ralphinho-rfc-pipeline

Decompose large features into RFC-driven work units with staged quality gates.

16|3|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/sehoon787/my-claude --skill ralphinho-rfc-pipeline-sehoon787
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralphinho-rfc-pipeline
Source: https://github.com/sehoon787/my-claude/tree/main/skills/ecc/ralphinho-rfc-pipeline
Command: npx skills add https://github.com/sehoon787/my-claude --skill ralphinho-rfc-pipeline-sehoon787

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RFC-driven approach to breaking large features into independent, verifiable work units, enabling safer collaboration across multiple agents and clearer ownership.

Core Features & Use Cases

  • RFC intake and DAG decomposition for scalable planning
  • Unit assignment, implementation, and deterministic execution
  • Quality gates, merge queue, and comprehensive verification
  • Recovery, audit reports, and transparency of outcomes

Quick Start

Define an RFC, decompose it into verifiable work units, and run them through the quality pipeline to merge safely.

Frequently Asked Questions about ralphinho-rfc-pipeline

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

FAQPage Schema
How do I decompose large software features into verifiable work units for multi-agent orchestration?

Decomposing large features into verifiable work units requires an RFC-driven approach, breaking tasks into independent units with a staged quality pipeline. This enables safer collaboration across multiple agents and clearer ownership through deterministic execution and dependency management.

What is RFC-driven DAG decomposition and when do I need it for complex task workflows?

RFC-driven DAG decomposition is a planning method that structures complex tasks into directed acyclic graphs for scalable execution. You need it when multi-agent workflows require independent validation, dependency management, and merge queuing to enforce controlled delivery and verification.

How do I set up a multi-agent quality pipeline with merge queues and verification gates?

Setting up a multi-agent quality pipeline involves defining an RFC, decomposing it into work units, and running them through staged quality gates. The pipeline applies merge rules and comprehensive verification to ensure controlled delivery and transparent audit reports.

Can I use RFC-driven orchestration to manage dependencies across multiple agents?

Yes, RFC-driven orchestration manages dependencies across multiple agents by assigning work units based on a unit spec schema and complexity tiers. It ensures deterministic execution and independent validation before tasks enter the merge queue.

What's the best way to enforce controlled delivery and verification in multi-agent workflows?

The best way to enforce controlled delivery in multi-agent workflows is implementing staged quality gates and merge rules. This approach specifies complexity tiers and uses a merge queue to ensure comprehensive verification before any work unit is safely merged.

Why does multi-agent task execution fail without independent validation and recovery mechanisms?

Multi-agent task execution fails without independent validation because complex tasks lack controlled delivery and verifiable outcomes. Implementing recovery mechanisms, audit reports, and transparency of outcomes ensures safer collaboration and clearer ownership across agents.