stakeholder-alignmentlisted

Align stakeholders in writing using RFCs, design docs, proposals, pre-reads, and decision docs with explicit role assignments (DACI, RAPID). Use when the user asks to write an RFC, design doc, proposal, pre-read, or decision doc, wants to align async stakeholders on a decision, needs to assign deciders vs consulted vs informed, wants to structure a cross-team proposal, or is preparing a pre-read for a decision meeting. NOT for structuring a generic memo (use structured-writing). NOT for stakeholder power maps (use persona-mapping). NOT for storytelling pitches or investor decks (use storytelling-for-stakeholders).
viktorbezdek/skillstack · ★ 9 · AI & Automation · score 76

Install: claude install-skill viktorbezdek/skillstack

# Stakeholder Alignment Decisions fail more often in the alignment than in the logic. A good RFC or decision doc does two things: makes the best argument for the chosen path, and makes the roles of everyone affected explicit so no one is surprised. ## Pick the right artifact | Artifact | When to use | Length | |---|---|---| | **RFC** / design doc | Technical decision affecting multiple teams; invites comment | 3-10 pages | | **Proposal** | Bet on a direction that requires budget/headcount/scope | 1-3 pages | | **Pre-read** | Input for a scheduled decision meeting | 1-2 pages | | **Decision doc** | Record a decision that has been made (or is being made now) | 1 page | | **One-pager** | Early alignment on an idea before full RFC | 1 page | Use the smallest artifact that produces alignment. A 10-page RFC for a two-team change is over-investment; a Slack thread for a 10-team change is under-investment. ## RFC / design doc structure ```markdown # [Title] — [state: Draft / Reviewing / Accepted / Rejected / Superseded] ## BLUF [One-paragraph summary: the problem, the proposed direction, the ask.] ## Roles (DACI) - **Driver:** [who writes + shepherds] - **Approver:** [who makes the final call — name, not group] - **Contributors:** [who provides input] - **Informed:** [who needs to know] ## Context [Shared understanding. What led here. Keep controversial claims for later sections.] ## Problem [What we are trying to solve. Why now.] ## Options considered - Option A: [name] —