discover-stakeholder-summary
Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach. Use at project kickoff, when taking over from another PM, or when resistance signals misalignment. For the update you send to those stakeholders, use foundation-stakeholder-update instead; this skill maps them, that one talks to them.
npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Stakeholder Summary 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 to Use - At the start of a new project or initiative to map the landscape - When taking over an existing project from another PM - Before major decision points that require cross-functional buy-in - When experiencing resistance or misalignment mid-project - During organizational changes that shift stakeholder dynamics - When preparing communication strategies for launches or changes ## When NOT to Use - You need the async update you will SEND to stakeholders -> use `foundation-stakeholder-update`; this skill maps them, that one talks to them - You are preparing for one specific high-stakes meeting -> use `foundation-meeting-brief` - You need customer research synthesis rather than an influence map -> use `discover-interview-synthesis` - You want a pers
- When to Use
- When NOT to Use
- Instructions
- Output Format
- Quality Checklist
- Examples
What does the discover-stakeholder-summary skill do?
Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach. Use at project kickoff, when taking over from another PM, or when resistance signals misalignment. For the update you send to those stakeholders, use foundation-stakeholder-update instead; this skill maps them, that one talks to them.
How do I install it?
Run `npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.