stakeholder-alignment
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).
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- 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).
- disable-model-invocation
- true
02 资源文件 3
- 参考文档agents/openai.yaml43 B
- 参考文档CREDITS.md351 B
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
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
04 同仓库更多 Skills
explainroo
Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.
unslop
Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or "sounds like AI".
technical-writing
Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.
no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
ponytail
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.
ponytail-review
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.