Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstakeholder-mapExecute the skills CLI command in your project's root directory to begin installation:
Fetches stakeholder-map from phuryn/pm-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate stakeholder-map. Access via /stakeholder-map in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
9.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
9.6K
stars
Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
You are helping build a stakeholder map for $ARGUMENTS.
If the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.
Identify stakeholders: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
Classify each stakeholder on two dimensions:
Place stakeholders in the Power × Interest grid:
| High Interest | Low Interest | |
|---|---|---|
| High Power | Manage Closely — Regular 1:1s, involve in decisions, seek their input early | Keep Satisfied — Periodic updates, escalate only critical issues |
| Low Power | Keep Informed — Regular status updates, invite to demos, gather feedback | Monitor — Light-touch updates, available on request |
For each quadrant, recommend:
Create a communication plan table:
| Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message |
|---|
Flag potential conflicts: Identify stakeholders with competing interests and suggest alignment strategies.
Think step by step. Save the stakeholder map as a markdown document.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
jezweb/claude-skills
stakeholder-map has been reliable in day-to-day use. Documentation quality is above average for community skills.
stakeholder-map has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in stakeholder-map — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added stakeholder-map from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
stakeholder-map reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend stakeholder-map for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: stakeholder-map is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: stakeholder-map is focused, and the summary matches what you get after install.
We added stakeholder-map from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend stakeholder-map for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 69