Stakeholder alignment
Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/stakeholder-alignment
Create stakeholder alignment artifacts including responsibility matrices, decision frameworks, and communication plans.From its SKILL.md
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill stakeholder-alignmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.2 KB, 202 tokens by cl100k_base, as published. Nobody here has run it
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 ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most operations skills give in 202 tokens
Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07
- Collect monitoring data throughout the simulationin 14 of 483, across 6 files
- Set the random seed for reproducibilityin 14 of 483, across 6 files
- Validate simulations against analytical solutionsin 12 of 483, across 4 files
- Clarify goals, constraints, and inputsin 11 of 483, across 2 files
- Implement contract tests for integration pointsin 11 of 483, across 2 files
- Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
- Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
- Avoid Python blocking calls in processesin 10 of 483, across 3 files
- Use resource context managers for automatic cleanupin 9 of 483, across 2 files
- Maintain consistent time unitsin 9 of 483, across 2 files
- Validate outcomes against success criteriain 8 of 483, across 1 file
- Analyze the legacy codebase for technical debtin 8 of 483, across 1 file
Said here and by no other author read
- Map stakeholders at kickoff
- Establish decision rights before conflict
- Communicate proactively
- Revisit artifacts as projects evolve
- Identify all stakeholders and map influence vs interest
- Assign Responsible, Accountable, Consulted, and Informed roles
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.