From product-superpowers
Use when you need to update stakeholders, write executive summaries, manage cross-functional relationships, or resolve conflicts with engineering and design.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-superpowers:stakeholder-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manage product stakeholder relationships effectively. Write clear status updates, prepare executive summaries, communicate across functions, and resolve conflicts constructively.
Manage product stakeholder relationships effectively. Write clear status updates, prepare executive summaries, communicate across functions, and resolve conflicts constructively.
Announce at start: "I'm using the stakeholder-management skill to [purpose]."
You MUST create a task for each of these items and complete them in order:
| Stakeholder Group | What They Care About | How to Communicate | Cadence |
|---|---|---|---|
| Executive/VP | Strategic alignment, ROI, key risks, resource decisions | Concise executive summary | Monthly or per milestone |
| Engineering Lead | Technical feasibility, dependencies, clarity of requirements | Detailed plan + trade-off discussions | Weekly or per sprint |
| Design Lead | User experience, consistency, design system alignment | Design reviews + user research findings | Weekly |
| Marketing | Launch timing, competitive positioning, messaging | Feature briefs + launch timelines | Per feature/launch |
| Sales | Customer commitments, competitive differentiators, availability | Enablement materials + roadmap highlights | Monthly |
| Customer Success | Feature changes, known issues, training needs | Release notes + support documentation | Per release |
| Legal/Compliance | Regulatory requirements, privacy, terms updates | Formal reviews of changes | Per significant change |
| Peer PMs | Dependencies, shared resources, learnings | Informal syncs + roadmap alignment | Bi-weekly |
Use this format for regular stakeholder updates. It scales from a Slack message to a full document.
One sentence. The most important thing to know.
Examples:
3-5 bullet points of what was accomplished since the last update.
This period:
• Shipped onboarding redesign to 25% of new users — early data shows +15% activation
• Completed 12 user interviews for the collaboration feature discovery
• Resolved the performance regression (P95 latency back to 1.8s)
• Signed off on design specs for the dashboard v2
What's at risk? What do you need help with? What decisions need to be made?
Risks & Blockers:
• [BLOCKER] API team timeline slipped by 1 week — need to re-plan sprint scope
• [RISK] Analytics contractor leaves end of month — need to prioritize knowledge transfer
• [NEEDS DECISION] Mobile-first or desktop-first for the dashboard? Need alignment by Friday
Asks:
• Engineering: Need 2 engineers for the API integration spike next sprint
• Leadership: Please review and approve the Q4 roadmap draft by EOW
# [Product/Feature] Status Update — [Date]
**Headline:** [One sentence — what's the most important thing to know?]
## Accomplishments
- [Accomplishment 1]
- [Accomplishment 2]
- [Accomplishment 3]
## Metrics
| Metric | Current | Target | Trend |
|--------|---------|--------|-------|
| ... | ... | ... | ↑/↓/→ |
## Risks & Blockers
- [Risk/blocker with impact and mitigation]
## Next Priorities
- [What's happening next]
## Asks
- [What do you need from the reader?]
When communicating to executives, use the SCRA framework:
Situation — Context. What's the landscape?
Complication — What changed? What's the problem or opportunity?
Resolution — What are we doing about it? (Present options, recommend one)
Ask — What do we need from you? (Decision, resources, air cover)
Situation:
Our user activation rate has been stuck at 40% for the past 3 quarters.
This is below our target of 65% and the primary reason retention is flat.
Complication:
Research with 20 users revealed that new users are overwhelmed by
the empty dashboard — they don't know what to do first. Competitors
all provide guided setup, which we lack.
Resolution:
I'm proposing a 6-week onboarding redesign sprint. We have 3 paths:
A) Full redesign (8 weeks, highest impact)
B) Quick-start templates only (3 weeks, medium impact) ← recommended
C) In-app tips only (1 week, lowest impact)
Ask:
Approve path B and allocate 1 designer and 2 engineers for 6 weeks
starting next sprint. I need your decision by Friday to hit Q3 targets.
Principles for communicating with executives and leadership:
| Conflict | Typical Positions | Resolution Approach |
|---|---|---|
| Refactor vs. new features | Engineering wants to refactor. PM wants new features. | Allocate % of capacity for tech debt. Connect refactors to user-visible outcomes. |
| Design perfection vs. shipping | Design wants pixel-perfect. Engineering wants to ship. | Define "good enough to ship" together. Use design QA checklist. Iterate post-launch. |
| Timeline pressure | PM pushes for aggressive timeline. Engineering says it'll take longer. | Scope the date, don't date the scope. What must ship by the date? What can follow? |
| MVP scope disagreement | Different opinions on what's "minimum" | Go back to user outcomes. What's the smallest thing that tests our riskiest assumption? |
npx claudepluginhub guhcostan/product-superpowers --plugin product-superpowersGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.