stakeholder-map
The stakeholder-map Claude Code skill creates a power/interest grid analysis that systematically identifies stakeholders for a product launch or initiative, classifies them by their ability to influence outcomes and personal investment level, and generates tailored communication strategies for each quadrant. Use this when managing complex cross-functional projects, preparing organizational launches, aligning teams with competing priorities, or developing stakeholder engagement plans that require differentiated outreach by stakeholder type.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/stakeholder-map && cp -r /tmp/stakeholder-map/pm-execution/skills/stakeholder-map ~/.claude/skills/stakeholder-mapSKILL.md
## Stakeholder Mapping & Communication Plan Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group. ### Context 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. ### Instructions 1. **Identify stakeholders**: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users. 2. **Classify each stakeholder** on two dimensions: - **Power** (High/Low): Their ability to influence decisions, resources, or outcomes - **Interest** (High/Low): How much the project directly affects them or how engaged they are 3. **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 | 4. **For each quadrant**, recommend: - Communication frequency (daily, weekly, bi-weekly, monthly) - Communication format (1:1, email, Slack, meeting, dashboard) - Key messages and framing - Potential risks if this stakeholder is neglected 5. **Create a communication plan table**: | Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message | |---|---|---|---|---|---|---|---| 6. **Flag potential conflicts**: Identify stakeholders with competing interests and suggest alignment strategies. Think step by step. Save the stakeholder map as a markdown document. --- ### Further Reading - [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium) - [Team Topologies: A Handbook to Set and Scale Product Teams](https://www.productcompass.pm/p/team-topologies-a-handbook-to-set)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.