ralphinho-rfc-pipeline

Decomposes large features into RFC-driven work units with DAG orchestration and quality gates.

2|Updated Mar 29, 2015
One-click install
npx skills add https://github.com/ovisan/dotfiles --skill ralphinho-rfc-pipeline-ovisan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralphinho-rfc-pipeline
Source: https://github.com/ovisan/dotfiles/tree/main/.agents/skills/ralphinho-rfc-pipeline
Command: npx skills add https://github.com/ovisan/dotfiles --skill ralphinho-rfc-pipeline-ovisan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large features often exceed what a single agent pass can implement reliably, leading to incomplete or unverifiable changes. This Skill provides a structured pipeline that splits an RFC into independently verifiable work units with dependency tracking, quality gates, and merge queue rules. ## Core Features & Use Cases - DAG Decomposition: Breaks an RFC into work units with id, depends_on, scope, acceptance_tests, risk_level, and rollback_plan fields. - Quality Pipeline per Unit: Enforces research, implementation plan, implementation, tests, review, and merge-ready report stages for every unit. - Merge Queue and Recovery: Rebases unit branches on the integration branch, re-runs integration tests after each merge, and evicts stalled units with narrowed scope regeneration. - Use Case: When implementing a multi-service authentication overhaul, use this Skill to decompose the RFC into Tier 1-3 units, assign them to agents, validate each against acceptance tests, and merge them through a controlled queue. ## Quick Start Use the ralphinho-rfc-pipeline skill to decompose this feature RFC into dependency-ordered work units with acceptance tests and a merge queue plan.

Frequently Asked Questions about ralphinho-rfc-pipeline

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

FAQPage Schema
How do I split a large feature into agent-implementable work units?▼

Decompose the feature RFC into work units each defining id, depends_on, scope, acceptance_tests, risk_level, and rollback_plan. Order units by dependency in a DAG so each can be implemented and validated independently before merging.

What is a merge queue in multi-agent development?▼

A merge queue serializes integration of completed work units onto a shared integration branch. Each unit is rebased on the latest branch state and integration tests re-run after every merge, preventing broken combinations from landing.

How are work units classified by complexity?▼

Units fall into three tiers: Tier 1 covers isolated file edits with deterministic tests, Tier 2 covers multi-file behavior changes with moderate integration risk, and Tier 3 covers schema, auth, performance, or security changes.

What happens when a work unit stalls during implementation?▼

Stalled units are evicted from the active queue, their findings are snapshotted, and a narrowed unit scope is regenerated. The unit is then retried with updated constraints rather than blocking the pipeline.

When should I not use RFC decomposition for a feature?▼

Avoid it for small, single-file changes that one agent pass can complete and verify directly. The overhead of DAG decomposition, quality gates, and merge queues only pays off for features spanning multiple files or risk tiers.