Documents stakeholder needs, concerns, influence, and relationships for projects or initiatives. Use when starting projects, handing off, or resolving misalignments.
From pm-skillsnpx claudepluginhub product-on-purpose/pm-skillsThis skill uses the workspace's default tool permissions.
references/EXAMPLE.mdreferences/TEMPLATE.mdDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
A stakeholder summary documents the people and groups who have interest in or influence over a project, capturing their needs, concerns, and relationships. Effective stakeholder management often determines project success more than technical execution, making this document essential for navigating organizational complexity.
When asked to create a stakeholder summary, follow these steps:
Identify All Stakeholders List everyone with a stake in the project: sponsors, approvers, contributors, consumers of the output, and those affected by changes. Cast a wide net initially—you can prioritize later. Include both individuals and groups.
Assess Influence and Interest For each stakeholder, evaluate their influence (power to affect the project) and interest (how much they care about outcomes). This determines how much attention each requires.
Understand Their Perspective Document what each stakeholder needs from the project, what concerns or risks they perceive, and what a successful outcome looks like to them. When possible, validate these directly through conversation.
Map Relationships Identify key dependencies, alliances, and potential conflicts between stakeholders. Understanding who influences whom helps you navigate organizational dynamics.
Categorize by Engagement Level Based on influence and interest, determine the appropriate engagement approach: actively manage, keep satisfied, keep informed, or monitor. Different stakeholders need different levels of attention.
Plan Communication For high-priority stakeholders, define communication cadence, preferred channels, and key messages. Good stakeholder management is proactive, not reactive.
Identify Risks and Mitigations Note where stakeholder concerns could derail the project and plan how to address them. Early attention to resistant stakeholders prevents surprises.
Use the template in references/TEMPLATE.md to structure the output.
Before finalizing, verify:
See references/EXAMPLE.md for a completed example.