What is an 'accountability gap' in this context?

An accountability gap occurs when an activity has no assigned 'Accountable' role, multiple roles claiming accountability, or a required artefact with no 'Responsible' worker.

What is the primary purpose of the Responsibility Flows skill?

It ensures project clarity by mapping who is Responsible, Accountable, Consulted, and Informed for every activity, preventing 'orphaned' artefacts and decision delays.

How does it handle team changes?

The skill separates roles from individuals, allowing you to update the person-to-role assignment without breaking the underlying accountability structure of the project.

When should I trigger this skill in my workflow?

It is best used when entering the Architecture or Discovery phases, when team members join or leave, or during gate reviews if ownership is unclear.

Agile Responsibility Flows

Name: Agile Responsibility Flows
Author: nsalvacao

bynsalvacao

0•

Collaboration Tools

Generates professional RACI charts and accountability maps to eliminate project ambiguity and streamline decision-making.

Responsibility Flows is a specialized skill for Claude Code designed to institutionalize clarity within the software development lifecycle. By systematically mapping project activities to specific roles using the RACI framework (Responsible, Accountable, Consulted, Informed), this skill helps teams produce mandatory Role-Responsibility Maps, identify dangerous accountability gaps, and define clear escalation paths. It is essential during architecture and discovery phases or whenever team structures change, ensuring that every artefact has an owner and no decision becomes a bottleneck.

Key Features

01Formal escalation path mapping for governance and gate reviews

02Automated RACI chart generation for all project lifecycle phases

03Production of standardized Role-Responsibility Map artefacts

04Detection and resolution of accountability gaps and dual-ownership conflicts

05Dynamic role-roster management for evolving team structures

060 GitHub stars

Use Cases

01Onboarding new team members by visualizing their accountability boundaries and dependencies

02Resolving project stalls by identifying the single 'Accountable' individual for blocked decisions

03Defining clear ownership of backlog items and architecture artefacts during Phase 2 and 3

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nsalvacao/nsalvacao-claude-code-plugins responsibility-flows

For use in Claude.ai and ChatGPT

Key Features

01Formal escalation path mapping for governance and gate reviews

02Automated RACI chart generation for all project lifecycle phases

03Production of standardized Role-Responsibility Map artefacts

04Detection and resolution of accountability gaps and dual-ownership conflicts

05Dynamic role-roster management for evolving team structures

060 GitHub stars

Use Cases

01Onboarding new team members by visualizing their accountability boundaries and dependencies

02Resolving project stalls by identifying the single 'Accountable' individual for blocked decisions

03Defining clear ownership of backlog items and architecture artefacts during Phase 2 and 3

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nsalvacao/nsalvacao-claude-code-plugins responsibility-flows

For use in Claude.ai and ChatGPT