raci

Codify agent ownership and handoff artifacts across project lifecycle steps.

1|Updated Feb 22, 2026

Search Tags:#workflow #planning #agents #coordination #handoff #raci #responsibility

Ready to run

npx skills add https://github.com/gonz0w/bgsd-oc --skill raci

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: raci
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/raci
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill raci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines clear ownership boundaries across lifecycle steps, ensuring every task has a single Responsible agent and predictable handoffs of required artifacts.

Core Features & Use Cases

RACI Matrix: assigns exactly one Responsible agent per step to remove ambiguity.
Handoff Contracts: standardizes required artifacts and formats for each handoff between agents.
Coverage Summary: provides traceability of ownership and dependencies across the workflow.

Quick Start

Define the owner for each lifecycle step in your project and generate the required handoff artifacts.

Frequently Asked Questions about raci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I assign agent ownership and clarify handoff contracts in multi-agent workflows?▼

To clarify handoff contracts, you standardize the required artifacts and formats for each transition between agents. This ensures predictable task execution and removes ambiguity during phase handoffs across the project lifecycle.

What is the best way to enforce a single responsible agent per project lifecycle step?▼

The best way to enforce a single responsible agent is by codifying ownership rules within a RACI matrix. This governance approach guarantees exactly one Responsible agent per step, removing ambiguity across the workflow.

Does this approach support coverage traceability across multiple agent coordination phases?▼

Yes, this approach supports coverage traceability by providing a coverage summary across all workflow phases. It documents ownership rules and dependencies, ensuring full traceability across multi-agent coordination.

When do I need standardized handoff artifacts for agent workflow planning?▼

You need standardized handoff artifacts for agent workflow planning when managing multi-agent coordination. Standardized artifacts guarantee predictable transitions and ensure each agent receives required inputs in the correct format.

How do I generate required handoff artifacts after defining lifecycle step owners?▼

To generate required handoff artifacts, define the owner for each lifecycle step in your project. The governance system then automates the creation of standardized artifacts needed for each agent handoff.