Stakeholder Alignment
Produce RACI matrices, stakeholder maps, and decision frameworks so design choices do not stall on unclear roles or late feedback.
Overview
Stakeholder Alignment is an agent skill most often used in Validate (also Build) that creates RACI matrices, stakeholder maps, and communication plans around design decisions.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill stakeholder-alignmentWhat is this skill?
- Five alignment artifact types: Stakeholder Map, RACI Matrix, Decision Framework, Communication Plan, and Feedback Protoc
- Influence-vs-interest mapping and role categorization for missing or silent stakeholders
- Decision rights and disagreement resolution defined before conflicts escalate
- Handles anti-patterns: stakeholders designing solutions, conflicting priorities, late scope changes
- Best practices: document rationale, proactive cadence, revisit maps as the project evolves
- 5 alignment artifact types: Stakeholder Map, RACI Matrix, Decision Framework, Communication Plan, Feedback Protocol
Adoption & trust: 559 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are shipping UX or product changes but nobody agrees who decides, who must be consulted, or how feedback gets prioritized—so reviews reopen settled choices.
Who is it for?
Solo founders coordinating freelancers, co-founders, or early customers on design scope with lightweight RACI and decision frameworks instead of heavyweight enterprise PM tooling.
Skip if: Purely solo projects with no external reviewers where a one-page spec is enough and formal stakeholder governance adds no value.
When should I use this skill?
Starting or rescoping a design-led project where roles, decision rights, or feedback loops are unclear.
What do I get? / Deliverables
You get documented stakeholder maps, RACI coverage per decision, and a communication plus feedback protocol the team can follow before the next design milestone.
- Stakeholder map
- RACI matrix
- Decision framework
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Stakeholder alignment lands on Validate/scope as the first journey shelf where solo builders must lock who decides, who is consulted, and how feedback flows before heavy Build work. Scope is where kickoff artifacts—maps, RACI, communication cadence—prevent late scope churn that the skill explicitly calls out as a common challenge.
Where it fits
At MVP kickoff, map investors as Consulted and the founder as Accountable for navigation IA decisions.
Before a sprint with a contract designer, publish cadence and channels in a communication plan tied to the RACI.
Document decision rationale in a decision log referenced by the alignment artifacts when scope shifts.
Clarify who is Informed versus Consulted for launch-ready UI so marketing does not trigger last-minute visual rework.
How it compares
Use for alignment artifacts and decision rights, not as a wireframing or visual design generation skill.
Common Questions / FAQ
Who is Stakeholder Alignment for?
Indie builders and designer-founders who run kickoffs with multiple influencers—advisors, partners, or users—and need clear RACI and feedback rules without a dedicated PMO.
When should I use Stakeholder Alignment?
Use it in Validate when scoping an MVP and naming decision owners, in Build during PM checkpoints before major UX releases, and whenever late-stage scope changes suggest stakeholders were never mapped.
Is Stakeholder Alignment safe to install?
It generates planning documents only; check the Security Audits panel on this Prism page for the skill source before enabling it in your agent.
SKILL.md
READMESKILL.md - Stakeholder Alignment
# 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