From pm-skills
Documents stakeholder needs, concerns, and influence for projects. Use when starting initiatives, managing relationships, or ensuring cross-boundary alignment.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-skills:discover-stakeholder-summaryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
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.
foundation-stakeholder-update; this skill maps them, that one talks to themfoundation-meeting-briefdiscover-interview-synthesisfoundation-personaWhen 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. A complete summary fills every template section: Overview; Stakeholder Map; Stakeholder Profiles; Detailed Stakeholder Analysis; Key Relationships; Communication Plan; Risk Mitigation; Action Items; and Document History.
Before finalizing, verify:
See references/EXAMPLE.md for a completed example.
npx claudepluginhub product-on-purpose/pm-skills --plugin pm-skillsIdentifies project stakeholders by category, assesses power/interest/attitude, generates registers, power/interest matrices, RACI charts, and communication plans using BABOK techniques.
Builds power/interest stakeholder maps, classifies by influence/engagement, recommends quadrant strategies, and generates communication plans/tables. For launches, team alignment, stakeholder management.