ralphinho-rfc-pipeline

Decomposes large features into RFC-driven work units with DAG orchestration and merge queues.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Femad-6/my-skills --skill ralphinho-rfc-pipeline-femad-6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralphinho-rfc-pipeline
Source: https://github.com/Femad-6/my-skills/tree/main/.github/skills/ralphinho-rfc-pipeline
Command: npx skills add https://github.com/Femad-6/my-skills --skill ralphinho-rfc-pipeline-femad-6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large features often exceed what a single agent pass can implement reliably, leading to incomplete work, broken dependencies, and risky merges. This Skill provides a structured pipeline for splitting big features into independently verifiable work 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. - Tiered Complexity Handling: Classifies units into three tiers, from isolated file edits to schema, auth, performance, and security changes. - Merge Queue & Recovery: Enforces merge rules such as rebasing on the integration branch and re-running integration tests, plus a recovery loop that evicts stalled units, snapshots findings, and retries with narrowed scope. - Use Case: When asked to build a multi-module authentication overhaul, use this Skill to produce an RFC execution log, unit scorecards, a dependency graph snapshot, and an integration risk summary. ## Quick Start Ask the agent to decompose your large feature RFC into dependency-ordered work units and execute them through the pipeline with quality gates.

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 agent tasks?

Use RFC decomposition to split the feature into work units, each with an id, depends_on list, scope, acceptance tests, risk level, and rollback plan. Units are then executed through a per-unit pipeline of research, planning, implementation, tests, review, and a merge-ready report.

What is a DAG-based multi-agent workflow?

It is an orchestration pattern where work units are nodes in a directed acyclic graph and dependencies determine execution order. Units with unresolved dependency failures are never merged, and integration tests re-run after each queued merge.

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

Use it when a feature is too large for one pass, such as multi-file behavior changes or schema, auth, performance, and security work. Tier 1 isolated edits with deterministic tests usually do not need full pipeline orchestration.

What happens when a work unit stalls or fails?

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 rather than blocking the entire pipeline.

How does the merge queue prevent broken integrations?

The queue blocks any unit with unresolved dependency failures, requires rebasing unit branches on the latest integration branch, and re-runs integration tests after each queued merge to catch regressions early.