Install Discover Stakeholder Summary
Pick your agent. Every command is ready to paste.
npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summaryThe open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.
01
Install it
Run the command above, or upload the folder in Claude.
02
Ask naturally
Describe the task. Your agent loads discover-stakeholder-summary when the request matches its description.
03
Name it if needed
If it does not trigger, say “use the discover-stakeholder-summary skill”. In Codex, type $discover-stakeholder-summary.
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 persona to design or market against -> use
foundation-persona
Instructions
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.
Output Format
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.
Quality Checklist
Before finalizing, verify:
- All significant stakeholders are identified (not just obvious ones)
- Influence and interest assessments are realistic, not wishful
- Concerns are documented from stakeholder's perspective, not dismissed
- Relationships and dependencies are mapped
- Communication plan is specific and actionable
- Resistant stakeholders have mitigation strategies
Examples
See references/EXAMPLE.md for a completed example.
Tips for Discover Stakeholder Summary
- • Start a fresh session after installing so your agent picks up the new skill.
- • It bundles reference files. The agent reads them only when needed, so they cost no context until then.
- • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
- • If two skills overlap, mention the one you want by name.
Questions about Discover Stakeholder Summary
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 Discover Stakeholder Summary?
Run "npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.
Does Discover Stakeholder Summary work in Cursor and Codex?
Yes. Discover Stakeholder Summary uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.
Is Discover Stakeholder Summary free?
Discover Stakeholder Summary is open source on GitHub under the Apache-2.0 license. It is free to install; check the license before commercial use.
Who made Discover Stakeholder Summary?
Discover Stakeholder Summary is published by product-on-purpose in the product-on-purpose/pm-skills repository, together with 29 other skills.


