agentleFS
fzfcleefzfclee/consulting-skills/skills/raci-matrix/SKILL.md

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

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
  1. Very specific:

    Use this skill to run RACI Matrix as a practical consulting method, not as a generic framework explanation.

    line 9
  2. Distinctive:

    Use exactly one Accountable owner per decision or deliverable whenever possible.

    line 13
  3. Very specific:

    If an input is missing, do not block automatically.

    line 25
  4. Distinctive:

    Do not use before the work products, decisions, and role boundaries are defined.

    line 29
  5. Distinctive:

    Keep wording professional and plain enough that a smart non-specialist can use the output directly.

    line 85

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

StepRequired inputHow to executeOutput
Define rowsDecisions, deliverables, process steps, or recurring tasks.Write each row as one accountable work item with a clear completion point.RACI row list.
Define columnsRoles, 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/IRows, columns, known authority, handoff rules.Assign Responsible, Accountable, Consulted, and Informed; keep one Accountable when possible.Draft RACI matrix.
Find role defectsDraft matrix.Flag no Accountable, multiple Accountables, no Responsible, over-consulting, or missing informed parties.Ownership gap list.
Confirm operating rulesGap 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.