Agent skill · product strategy · borghei
daci-framework
DACI decision facilitation framework (Driver, Approver, Contributor, Informed) for clarifying decision ownership, reducing decision thrash, role assignment, and governance design across product teams.
Why this skill is useful
Codifies a structured decision-making framework that the AI could infer but now has a clear standard to follow.
What it needs
About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
DACI Decision Framework Overview Clarify decision ownership and reduce decision thrash using the DACI framework (Driver, Approver, Contributor, Informed). Unlike RACI which focuses on task responsibility, DACI is purpose-built for product decisions -- who drives the decision to closure, who has veto power, who provides input, and who needs to know. The four roles in brief: Driver (exactly one, drives to closure), Approver (1-2 max, holds veto), Contributor (input without veto), Informed (notified, not consulted). Build a chart by mapping current state, finding pain points, designing target state, and rolling out a 30/60/90 transition. See the playbook reference for role rules, the 7-step build sequence, and health metrics. When to Use New team formation -- A new cross-functional group needs clear decision-making roles. Decision thrash -- Decisions stall because nobody knows who has authority. Scaling teams -- Growth creates ambiguity about who owns which decisions. Post-incident -- A failed launch or missed deadline reveals unclear ownership. Reorg transitions -- Role changes create governance gaps. When NOT to Use Task assignment or project execution (use RACI instead). Individual contributor work allocation (use sprint planning). Truly one-person decisions (no governance overhead needed). Clarify First Before building the DACI chart, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] The specific decisions to map — the 3-5 high-impact decisions, not "everything" (each becomes a chart row; mapping too much at once is the top failure mode) [ ] Candidate people and their real authority — who can actually approve or veto (drives the Driver and Approver assignments; without genuine authority the chart is fiction) [ ] Current pain points — where decisions stall or thrash today (drives the current→target-state gap and the 30/60/90 transition plan) Stop rule: ask only the 2-3 that most change the output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/daci-framework