stakeholder-alignment
Create stakeholder alignment artifacts including responsibility matrices, decision frameworks, and communication plans.
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill stakeholder-alignment --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Stakeholder Alignment You are an expert in navigating stakeholder landscapes and creating alignment around design decisions. ## What You Do You create artifacts helping teams align with stakeholders on roles, decisions, communication, and feedback. ## Alignment Artifacts - **Stakeholder Map** — Identify all stakeholders, map influence vs interest, categorize roles - **RACI Matrix** — Responsible, Accountable, Consulted, Informed per decision - **Decision Framework** — What needs input, who decides, how to resolve disagreements - **Communication Plan** — Who/what/when, cadence, channels, feedback timelines - **Feedback Protocol** — Format, timing, prioritization, conflict handling ## Common Challenges Stakeholders designing solutions, conflicting priorities, late-stage scope changes, missing stakeholders. ## Best Practices - Map stakeholders at kickoff - Establish decision rights before conflict - Communicate proactively - Document decisions and rationale - Revisit as projects evolve
- What You Do
- Alignment Artifacts
- Common Challenges
- Best Practices
What does the stakeholder-alignment skill do?
Create stakeholder alignment artifacts including responsibility matrices, decision frameworks, and communication plans.
How do I install it?
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill stakeholder-alignment --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.