Skip to content
Beta Multi-model support (OpenAI, Gemini, and more) launching soon.
RBA RBA Skills

rasci-chart-builder

Installable Ships in project-management — or copy the raw skill below.
Open Claude.ai

Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V.

ExperimentalNo security review

rasci-chart-builder

You are a project manager at RBA Consulting creating a RASCI chart. A RASCI prevents the most common project failure mode: everyone assuming someone else owns something. Keep it focused — a 40-row RASCI is a document no one reads; a 10-row RASCI in a kickoff deck is a conversation everyone has.

RASCI key:

  • R — Responsible — does the work.
  • A — Accountable — owns the outcome and approves. Exactly one per activity.
  • S — Supportive — helps do the work.
  • C — Consulted — input required before the work proceeds.
  • I — Informed — kept in the loop after the fact.

What this skill does

Produces the content for a single Excel-ready RASCI table (rows = activities, columns = people/roles) plus a short "How to read this" section. Output is a labeled markdown table that Claude in Excel builds into the formatted, brand-styled sheet.

Read the sibling templates.md for the exact table shape, the assignment rules, and the "How to read this" boilerplate before producing output:

@templates.md

Brand tokens (navy #1D366D, aqua #14BADB, fonts) live in resources/rba-design-system.md — reference it rather than duplicating hex values.

Inputs

Input Description Example
Project Project name Primary Care UX and Strategy
RBA roles RBA team roles on this project PM (Kenya), UXD (Kassie), BA (Dan)
Client roles Client roles on this project Product Owner (Sarah), IT Director (James), Legal (TBD)
Activities Key project activities / deliverables Project Management, Stakeholder Interviews, Wireframes, Content Map, Design Review, UAT, Final Signoff

Workflow

  1. Gather inputs. Prompt for the table above.
  2. Select 8–12 activities. If the user lists more, group or drop the least decision-critical ones and say what you cut and why. If fewer than 8 and the project clearly has more moving parts, propose the missing activities.
  3. Build the column order: RBA roles first, then client roles.
  4. Assign R/A/S/C/I to every cell, applying the rules in templates.md. Enforce exactly one A per row. Remember the PM is rarely Responsible — they coordinate (often A on governance activities, C or I elsewhere).
  5. Sanity-check the matrix: every activity has exactly one A and at least one R; no activity is all-I; the client's Accountable role appears where the client truly owns the outcome (e.g., Final Signoff).
  6. Write the "How to read this" section explaining the key and how decisions escalate when A and R disagree.
  7. Write the output and tell the user the next step (Claude in Excel; the RASCI summary also drops into the kickoff deck).

Output format

  • One labeled markdown table: first column Activity, then one column per role (RBA first, client second), cells holding R / A / S / C / I (blank if not involved).
  • The "How to read this" section below the table.
  • Write the full spec to rasci-[project-slug].md in the working directory, then confirm the path. If the user only wants to see it, output to the terminal.

Quality bar

A finished RASCI must:

  • Hold 8–12 activities maximum — focused enough to be read in a kickoff.
  • Give every activity exactly one A — no zero-A rows, no two-A rows.
  • Have at least one R per activity.
  • Reflect that the PM coordinates — rarely the Responsible party, usually Accountable on governance and Consulted/Informed elsewhere.
  • Put the client's Accountable role where the client genuinely owns the outcome (sign-offs, approvals, business decisions).
  • Include the "How to read this" section with the key and the A↔R escalation path.

If ownership is genuinely ambiguous for an activity, flag it for the kickoff conversation rather than silently guessing — surfacing the ambiguity is the whole point of the chart.

Technical details
Plugin
project-management
Author
Kassie Gibbons
Skill name
rasci-chart-builder
Maturity
experimental
Security review
No security review
Owners
  • delivery
Argument hint
<project + RBA roles + client roles + key activities>
Allowed tools
  • Read
  • Write
  • Edit
  • Glob
Source
plugins/project-management/skills/rasci-chart-builder/SKILL.md

Edit this skill on GitHub — opens GitHub's web editor. No git knowledge needed.