User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach.
Install Discover Stakeholder Summary
$ npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills discover-stakeholder-summary --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/discover-stakeholder-summary .claude/skills/discover-stakeholder-summary && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "discover-stakeholder-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/discover-stakeholder-summary into .claude/skills/discover-stakeholder-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-stakeholder-summary", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/product-on-purpose/pm-skills/tree/main/skills/discover-stakeholder-summaryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills discover-stakeholder-summary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/discover-stakeholder-summary .agents/skills/discover-stakeholder-summary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "discover-stakeholder-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/discover-stakeholder-summary into .agents/skills/discover-stakeholder-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-stakeholder-summary", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills discover-stakeholder-summary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/discover-stakeholder-summary .cursor/skills/discover-stakeholder-summary && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "discover-stakeholder-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/discover-stakeholder-summary into .cursor/skills/discover-stakeholder-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-stakeholder-summary", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/product-on-purpose/pm-skills.git --path skills/discover-stakeholder-summary--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills discover-stakeholder-summary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/discover-stakeholder-summary .gemini/skills/discover-stakeholder-summary && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "discover-stakeholder-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/discover-stakeholder-summary into .gemini/skills/discover-stakeholder-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-stakeholder-summary", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install product-on-purpose/pm-skills discover-stakeholder-summaryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/discover-stakeholder-summary .github/skills/discover-stakeholder-summary && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "discover-stakeholder-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/discover-stakeholder-summary into .github/skills/discover-stakeholder-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-stakeholder-summary", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills discover-stakeholder-summary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/discover-stakeholder-summary .opencode/skills/discover-stakeholder-summary && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "discover-stakeholder-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/discover-stakeholder-summary into .opencode/skills/discover-stakeholder-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discover-stakeholder-summary", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
discover-stakeholder-summary- GitHub stars
- 716
- Token cost
- ~1.1k tokens
- SKILL.md length
- 457 words
- Files
- 5 (incl. references)
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach.
- Works in 7 steps: Identify All Stakeholders → Assess Influence and Interest → Understand Their Perspective → …
- Product & Project Management work in your project
- SKILL.md covers When to Use, When NOT to Use, Instructions and Output Format, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Discover Stakeholder Summary is an agent skill from product-on-purpose/pm-skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `HISTORY.md`, `evals/trigger-fixtures.json` and `references/EXAMPLE.md`).
It sits in Product & Project Management. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.
When your agent uses it
- Product & Project Management work in your project
Example prompts
- “/discover-stakeholder-summary”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Identify All Stakeholders
- Assess Influence and Interest
- Understand Their Perspective
- Map Relationships
- Categorize by Engagement Level
- Plan Communication
- Identify Risks and Mitigations
What it can do on your machine
Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Discover Stakeholder Summary loads about 1.1k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 457 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 457 words, ~1,075 tokens.
Download SKILL.mdSave it as
.claude/skills/discover-stakeholder-summary/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- discover-stakeholder-summary
- description
- 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.
- license
- Apache-2.0
- metadata.phase
- discover
- metadata.version
- 2.2.0
- metadata.updated
- 2026-07-04
- metadata.category
- research
- metadata.frameworks
- triple-diamond, lean-startup, design-thinking
- metadata.author
- product-on-purpose
<!-- 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 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.
Show full SKILL.md (90 more words)Show less
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.
© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/discover-stakeholder-summary of product-on-purpose/pm-skills.
- SKILL.md
- HISTORY.md
- evals/trigger-fixtures.json
- references/EXAMPLE.md
- references/TEMPLATE.md
Open the folder on GitHubat commit 1cef1a9
Compare with similar skills
Discover Stakeholder Summary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Discover Stakeholder Summary this skillproduct-on-purpose/pm-skills | 716 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Convex Create Componentspokvulcan/poker-planning | 115 | 8 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Self Improving Agentfarm-fe/farm | 5.6k | 2 repos | ~3.3k | Automated safety check: Notes | MIT |
Similar skills
Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Convex Create Component
spokvulcan/poker-planning
Builds reusable Convex components with isolated tables and app-facing APIs.
Self Improving Agent
farm-fe/farm
A universal self-improving agent that learns from ALL skill experiences.
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
More from product-on-purpose/pm-skills
All 68 skills in this repoDefine Hypothesis
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
Define Jtbd Canvas
product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
Define Problem Statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
Deliver Acceptance Criteria
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.
Deliver Launch Checklist
product-on-purpose/pm-skills
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Related
Categories
Questions about Discover Stakeholder Summary
What does Discover Stakeholder Summary do?
Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach. Discover Stakeholder Summary is an agent skill from product-on-purpose/pm-skills. Maps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach.
When should I use Discover Stakeholder Summary?
Discover Stakeholder Summary fits situations like: product & Project Management work in your project.
How do I install Discover Stakeholder Summary in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary -a claude-code`. Or copy the skill folder (skills/discover-stakeholder-summary in product-on-purpose/pm-skills) into .claude/skills/discover-stakeholder-summary in your project. Claude Code loads it when a task matches its description.
How do I install Discover Stakeholder Summary in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary -a codex`. Or copy the skill folder (skills/discover-stakeholder-summary in product-on-purpose/pm-skills) into .agents/skills/discover-stakeholder-summary in your project. Codex loads it when a task matches its description.
Can I use Discover Stakeholder Summary in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill discover-stakeholder-summary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/discover-stakeholder-summary, .gemini/skills/discover-stakeholder-summary, .github/skills/discover-stakeholder-summary and .opencode/skills/discover-stakeholder-summary in your project.
What does Discover Stakeholder Summary need to run?
SKILL.md names no scripts, command-line tools or credentials: Discover Stakeholder Summary is instructions for the agent only.
Does Discover Stakeholder Summary access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Discover Stakeholder Summary safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Discover Stakeholder Summary use?
Discover Stakeholder Summary is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Discover Stakeholder Summary use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.
What are the alternatives to Discover Stakeholder Summary?
Skills that share tags, products or a category with Discover Stakeholder Summary: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Discover Stakeholder Summary?
product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.
Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.