ralphinho-rfc-pipeline

Decomposes large features into RFC-driven work units executed through a multi-agent DAG pipeline.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill ralphinho-rfc-pipeline-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralphinho-rfc-pipeline
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/ralphinho-rfc-pipeline
Command: npx skills add https://github.com/ibytechaos/claude --skill ralphinho-rfc-pipeline-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large features often exceed what a single agent pass can implement reliably, leading to incomplete changes, broken dependencies, and risky merges. This Skill structures the work as an RFC-driven pipeline so big changes are split into independently verifiable units with quality gates. ## Core Features & Use Cases - DAG Decomposition: Breaks an RFC into work units with explicit depends_on relationships, scope, acceptance tests, risk levels, and rollback plans. - Quality Gates per Unit: Runs each unit through research, planning, implementation, tests, review, and a merge-ready report before integration. - Merge Queue & Recovery: Enforces rebase and integration-test rules on every queued merge, and recovers stalled units by snapshotting findings and regenerating narrowed scopes. - Use Case: When asked to add a new authentication subsystem touching schema, APIs, and UI, use this Skill to split the work into Tier 1-3 units, execute them against the dependency graph, and produce an integration risk summary. ## Quick Start Ask the agent to take this feature RFC and decompose it into dependency-ordered work units, then execute each unit through the quality pipeline with merge queue rules.

Frequently Asked Questions about ralphinho-rfc-pipeline

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

FAQPage Schema
How do I break a large feature into smaller work units for AI agents?

Define each unit with an id, depends_on list, scope, acceptance tests, risk level, and rollback plan, then order them in a dependency graph. This Skill executes units through research, planning, implementation, tests, and review stages before merging.

What is a multi-agent DAG execution pipeline?

It is a workflow where a feature RFC is decomposed into work units arranged as a directed acyclic graph, so independent units run in parallel while dependent units wait. Each unit passes quality gates before entering the merge queue.

When should I use RFC decomposition instead of a single implementation pass?

Use it when a feature is too large for one agent pass, such as multi-file behavior changes or schema, auth, performance, and security modifications. Tier 2 and Tier 3 changes benefit most from isolated, verifiable units.

How does the merge queue handle dependency failures?

Units with unresolved dependency failures are never merged. Each unit branch is rebased on the latest integration branch, and integration tests are re-run after every queued merge.

What happens when a work unit stalls during execution?

The stalled unit is evicted from the active queue, its findings are snapshotted, and a narrowed unit scope is regenerated. The unit is then retried with updated constraints.