stakeholder-identification — Claude Code skill
Maps initiative stakeholders before outreach, helping teams spot affected groups and decision-makers that an initial list can miss.
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a claude-codeWhat stakeholder-identification does
This skill builds a broad stakeholder list before outreach begins. Use it when starting an initiative, scoping discovery work, or drafting the stakeholder section of a PRD.
It starts with an unfiltered brainstorm, then sorts people and groups as Allies, Audiences, or Influencers. Each entry can receive R/P/D labels for resources, permission, and final decision authority. It also prompts an equity and bias check, including people affected indirectly or left out of the usual team discussion.
The skill keeps identification separate from prioritisation. A missing stakeholder with P or D is a reason to review the map before work starts, because that gap can become a blocker later.
What it helps with
- build a stakeholder list for a new initiative
- classify people by their relationship to the work
- mark resource, permission, and decision holders
- find overlooked affected groups
- prepare stakeholders for a PRD
Example prompts for the agent
- Identify stakeholders for moving customers to a new billing system.
- Review our stakeholder map and identify missing groups.
- Prepare a stakeholder list for product discovery research.
How to install stakeholder-identification
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a claude-code2Manually: put the files in place
~/.claude/skills/stakeholder-identification/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/stakeholder-identification/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a codex2Manually: put the files in place
.agents/skills/stakeholder-identification/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a cursor2Manually: put the files in place
.cursor/skills/stakeholder-identification/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills stakeholder-identification2Manually: put the files in place
.github/skills/stakeholder-identification/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/stakeholder-identificationManually: put the files in place
.devin/skills/stakeholder-identification/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about stakeholder-identification
How do I install stakeholder-identification in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a claude-code. Then repeat npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -a claude-code; the skill file is at ~/.claude/skills/stakeholder-identification/SKILL.md.
What does stakeholder-identification do?
It creates a structured stakeholder set before engagement. The skill categorises participants, marks their authority, and checks the list for bias and omissions.
What do the R/P/D labels mean?
R marks providers of resources, P marks people who grant permission, and D marks final decision authority. A stakeholder can hold more than one label.
