raci-matrix
Skill6 starsChanged 4 months agoApache-2.0View on GitHub
Use when ownership, approval rights, handoffs, or decision authority are unclear. Use when applying the RACI Matrix consulting method and when a user asks for RACI Matrix, method execution, structured diagnosis, or action planning.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- CAPP-Financials/Consulting_Braintheir own version, first seen Apr 24, 2026
- kenmulford/PMSkillstheir own version, first seen Apr 19, 2026
- 45ck/business-analysis-skillstheir own version, first seen Mar 28, 2026
- nandanosql/all_in_one_pm_skillstheir own version, first seen Feb 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- 45ck/business-analysis-skills★ 28same name
- nandanosql/all_in_one_pm_skills★ 1same name
- CAPP-Financials/Consulting_Brain★ 0same name
- kenmulford/PMSkills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- 5w1h-analysisSkill
- abductive-reasoningSkill
- account-planSkill
- affinity-diagramSkill
- assumption-inventorySkill
- balanced-scorecardSkill
- break-even-analysisSkill
- business-model-canvasSkill
- change-event-timelineSkill
- change-impact-analysisSkill
- communications-planSkill
- competitive-positioningSkill
- constraint-analysisSkill
- cost-benefit-analysisSkill
- critical-uncertaintiesSkill
- customer-segmentationSkill
- customer-success-health-scoreSkill
- deal-strategy-mapSkill
- decision-matrixSkill
- deductive-reasoningSkill
- effort-impact-matrixSkill
- empathy-mapSkill
- evidence-mapSkill
- fifteen-percent-solutionsSkill
- first-principles-thinkingSkill
- fishbone-diagramSkill
- five-whys-root-causeSkill
- force-field-analysisSkill
- go-to-market-diagnosisSkill
- hypothesis-treeSkill
- inductive-reasoningSkill
- issue-treeSkill
- jobs-to-be-doneSkill
- kano-modelSkill
- mece-frameworkSkill
- metrics-treeSkill
- mind-map-analysisSkill
- min-specsSkill
- north-star-metricSkill
- pestel-analysisSkill
- porter-five-forcesSkill
- power-interest-gridSkill
- pre-mortemSkill
- pricing-strategy-checkSkill
- rice-scoringSkill
- risk-matrixSkill
- scenario-planningSkill
- service-blueprintSkill
- signal-vs-noise-filterSkill
- stakeholder-power-mapSkill
- swot-analysisSkill
- systems-thinkingSkill
- user-journey-mappingSkill
- validation-planSkill
- weighted-scorecardSkill
- win-loss-reviewSkill
- wsjf-prioritizationSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use this skill to run RACI Matrix as a practical consulting method, not as a generic framework explanation.
- Distinctive: line 13
Use exactly one Accountable owner per decision or deliverable whenever possible.
- Very specific: line 25
If an input is missing, do not block automatically.
- Distinctive: line 29
Do not use before the work products, decisions, and role boundaries are defined.
- Distinctive: line 85
Keep wording professional and plain enough that a smart non-specialist can use the output directly.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
RACI Matrix
Use this skill to run RACI Matrix as a practical consulting method, not as a generic framework explanation.
Method Notes
- Use exactly one Accountable owner per decision or deliverable whenever possible.
- Responsible does the work; Accountable owns the result; Consulted gives two-way input; Informed receives one-way updates.
Required Inputs
Collect or infer these inputs before execution:
- work items or decisions
- roles or named owners
- current responsibility ambiguity
- decision cadence
If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.
When Not To Use
Do not use before the work products, decisions, and role boundaries are defined. RACI clarifies accountability for work; it does not resolve stakeholder resistance, authority gaps, or capacity shortages.
Adjacent Methods
change-impact-analysis: diagnose affected groups and adoption needs.communications-plan: define messages, channels, cadence, and feedback.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
| Define rows | Decisions, deliverables, process steps, or recurring tasks. | Write each row as one accountable work item with a clear completion point. | RACI row list. |
| Define columns | Roles, named owners, teams, approvers, contributors. | Use roles when many people rotate; use names when accountability is personal. | Role/owner column list. |
| Assign R/A/C/I | Rows, columns, known authority, handoff rules. | Assign Responsible, Accountable, Consulted, and Informed; keep one Accountable when possible. | Draft RACI matrix. |
| Find role defects | Draft matrix. | Flag no Accountable, multiple Accountables, no Responsible, over-consulting, or missing informed parties. | Ownership gap list. |
| Confirm operating rules | Gap list, governance cadence, escalation path. | Define sign-off, handoff, update cadence, and unresolved-role decision owner. | Final RACI and role clarification actions. |
Output Template
### 1. Scope And Decision Rights
Process / project:
Decision rows:
Roles:
Escalation owner:
### 2. RACI Matrix
| Work / decision | R | A | C | I | Timing |
|---|---|---|---|---|---|
| | | | | | |
### 3. Defects
| Row | Missing / duplicate accountability | Conflict | Fix |
|---|---|---|---|
| | | | |
### 4. Operating Rules
| Rule | Owner | Trigger | Escalation path |
|---|---|---|---|
| | | | |
### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:Quality Gate
- Produce the method-specific outputs for Scope And Decision Rights, RACI Matrix, Defects; do not substitute a generic framework summary.
- Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
- Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
- Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
- State missing inputs and the smallest validation action instead of inventing precision.
- Keep wording professional and plain enough that a smart non-specialist can use the output directly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

