stakeholder-alignment

Generate RFCs, proposals, and decision docs with DACI or RAPID role assignments.

10|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/viktorbezdek/skillstack --skill stakeholder-alignment-viktorbezdek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stakeholder-alignment
Source: https://github.com/viktorbezdek/skillstack/tree/main/communication/skills/stakeholder-alignment
Command: npx skills add https://github.com/viktorbezdek/skillstack --skill stakeholder-alignment-viktorbezdek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often struggle to achieve consensus on cross‑team decisions, resulting in unclear responsibilities, wasted meetings, and stalled projects. This skill provides structured artifacts and role‑assignment frameworks to ensure transparent alignment and decisive outcomes.

Core Features & Use Cases

  • Artifact selection guidance: Choose the smallest appropriate document (RFC, proposal, pre‑read, decision doc, or one‑pager) based on scope and audience.
  • Role assignment frameworks: Apply DACI or RAPID consistently, with rules for naming individuals, avoiding vetoes, and defining informed stakeholders.
  • Templates and checklists: Ready‑to‑use RFC, pre‑read, decision doc, and escalation playbooks with tables, role sections, and open‑question tracking.
  • Workflow steps: From drafting the BLUF through comment deadlines, stakeholder pinging, escalation, and post‑decision follow‑up. Use cases include launching a new product feature across multiple engineering teams, budgeting proposals that require cross‑functional sign‑off, and any async alignment needing documented decisions.

Quick Start

Request the stakeholder‑alignment skill to generate an RFC with DACI roles for your cross‑team decision.

Frequently Asked Questions about stakeholder-alignment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an RFC for cross-team decision alignment?

An RFC for cross-team alignment includes a concise BLUF, assigned DACI or RAPID roles, open-question tracking, and defined comment deadlines to ensure documented stakeholder consensus.

What is the difference between DACI and RAPID frameworks for role assignment?

DACI assigns Driver, Approver, Contributor, and Informed roles, while RAPID adds Performer and omits Contributor, ensuring clear accountability without veto powers in stakeholder alignment documents.

When do I need a pre-read versus a full decision doc for stakeholder alignment?

Select a pre-read for async meeting context, or a full decision doc when requiring structured cross-functional sign-off, RAPID role assignment, and documented escalation paths.

Can I use stakeholder alignment templates for async team decisions?

Yes, apply RFC and one-pager templates for async team decisions by using role-assignment rules, pinging stakeholders, and enforcing comment deadlines to achieve documented consensus.

What's the best way to structure a cross-team proposal that requires sign-off?

Structure cross-team proposals by drafting a BLUF, applying DACI to name individual roles, tracking open questions, and defining escalation paths to resolve stalled approvals.

How do I handle stakeholder vetoes during cross-functional alignment?

Prevent stakeholder vetoes during cross-functional alignment by applying role-assignment rules that eliminate veto powers, defining informed stakeholders, and using the escalation playbook.