Skip to main content
affpapa.org
RU EN
skill CX Codex

stakeholder-alignment · owl-listener — Claude Code skill: RACI matrix and decision

Builds alignment artifacts: a stakeholder map, RACI matrix, decision rights and a communication plan. Useful when unclear ownership stalls decisions.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add Owl-Listener/designer-skills --skill stakeholder-alignment -a claude-code
Open on GitHub

What stakeholder-alignment does

The skill produces a set of artifacts that pin down roles and agreements before an argument starts. A stakeholder map sorts participants by influence and interest, and the RACI matrix spells out who is responsible, accountable, consulted and informed for each decision. A decision framework sits alongside: what needs input, who decides, how disagreements get resolved.

The second half covers communication. A plan states who hears what, on which channel and how often, while a feedback protocol sets the format, timing and conflict handling. It targets familiar failures: stakeholders designing the solution themselves, conflicting priorities, scope changes late in the project, people missing from the list entirely.

The skill advises mapping stakeholders at kickoff and settling decision rights before conflict appears. Document decisions and the reasoning behind them, then revisit the artifacts as the project moves. If the problem is persuading someone in the moment rather than building structure, the author points to the design-negotiation skill in designer-toolkit — a different tool for a different job.

What it helps with

  • map stakeholders by influence and interest
  • settle who decides and who only gets informed
  • define channels and cadence for communication
  • agree on feedback format and turnaround
  • work through conflicting priorities before they block

Example prompts for the agent

  • build a stakeholder map for the account dashboard redesign
  • draft a RACI matrix for navigation structure decisions
  • write a stakeholder communication plan and feedback protocol

How to install stakeholder-alignment

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill stakeholder-alignment -a claude-code

2Manually: put the files in place

~/.claude/skills/stakeholder-alignment/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/stakeholder-alignment/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about stakeholder-alignment

How do I install stakeholder-alignment in Claude?

Run npx skills add Owl-Listener/designer-skills --skill stakeholder-alignment -a claude-code. The skill lands in ~/.claude/skills/stakeholder-alignment/SKILL.md.

What does stakeholder-alignment do?

It builds alignment artifacts: a stakeholder map, RACI matrix, decision framework, communication plan and feedback protocol. It helps when nobody is sure who owns a decision.

How is it different from design-negotiation?

stakeholder-alignment sets up roles and agreements for the long run. For persuading someone in the moment, the author points to design-negotiation in designer-toolkit.

Source text

SKILL.md · MIT 
---
name: stakeholder-alignment
description: Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use `design-negotiation` (designer-toolkit).
---
# 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

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →

stakeholder-alignment by other authors comes first.

stakeholder-alignment RefoundAI Guides cross-functional alignment without formal authority. Uses frameworks and interview tactics from Lenny's Podcast to map incentives and handle pushback. CX Codex +1 2,100installs stakeholder-communication aj-geddes A skill for planning stakeholder communication: status updates, engagement plans and conversations about slipping deadlines. CX Codex +1 500installs foundation-stakeholder-briefings product-on-purpose Turns any source spec or note into a neutral master document with numbered claims, then projects tailored briefing blocks for engineering and leadership. CX Codex +1 428installs repeated-component-alignment dembrandt A coding-agent skill that keeps cards, list rows and tiles aligned when text lengths differ. Useful whenever you build or review a repeated component. CX Codex +1 678installs strategic-alignment Alireza Rezvani This skill connects company strategy to team and individual OKRs. Use it when departments pull in different directions or goals lose their link to company priorities. 563installs foundation-stakeholder-update product-on-purpose Turns meeting outcomes into an async update for people who missed the room, with the CTA up front and jargon translated for the audience. CX Codex +1 693installs spark-recipe-stakeholder-brief readdle Pulls a person's meetings and email threads into one relationship brief. Handy before a 1:1 or when reconnecting after a gap. CX Codex +1 343installs

From the same set111

opportunity-framework Turns a pile of possible improvements into a ranked roadmap using impact-effort and RICE. Handy when ideas outnumber capacity. CX Codex +1 2,000installs design-review-process A skill that sets four review gates for design work, from concept to implementation QA. Useful when things ship without a consistent review step. CX Codex +1 2,000installs north-star-vision Articulates a long-horizon product vision across 1-year, 2-3 year, and 5+ year horizons. Useful when a team lacks a clear strategic direction. CX Codex +1 2,000installs test-scenario Writes usability test scenarios with realistic context, success criteria and facilitation notes. Useful once the study is planned and the tasks are still missing. CX Codex +1 2,000installs metrics-definition Defines UX metrics and KPIs that connect design decisions to measurable outcomes. Useful when deciding what to measure before tracking changes. CX Codex +1 2,100installs diary-study-plan Walks you through designing a diary study: prompts, cadence, duration, participant criteria and an analysis frame. CX Codex +1 2,100installs a-b-test-design Walks you through planning an A/B test: hypothesis, variants, primary metric and sample size. Useful when a change can be measured quantitatively. CX Codex +1 2,100installs form-design Designs forms end to end, covering field order, grouping, validation, and accessibility. Useful when building anything from single inputs to multi-step flows. CX Codex +1 1,900installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor