ralphinho-rfc-pipeline

Decompose RFCs into a dependency DAG of verifiable work units.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a feature is too large for one agent to handle correctly, it causes slow iterations, unclear ownership, and brittle integrations that are hard to validate before merge.

Core Features & Use Cases

  • RFC-driven decomposition into a DAG: Breaks a proposal into independently verifiable work units with explicit dependencies.
  • Quality gates per unit: Enforces a consistent sequence of research, plans, implementation, tests, review, and a merge-ready report.
  • Merge queue and integration safety: Prevents merges when dependency failures exist, rebases on the latest integration branch, and re-runs integration tests after queued merges.

Quick Start

Ask the AI to execute the ralphinho RFC pipeline by decomposing your RFC into DAG-structured work units, running unit validation with quality gates, and producing an RFC execution log plus dependency graph snapshot ready for merge queue integration.

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 a large RFC into independently verifiable work units?

Decomposing an RFC involves breaking a proposal into a dependency DAG of tasks with explicit templates for scope, acceptance tests, risk level, and rollback plans to ensure safe integration.

What is a dependency DAG in multi-agent feature development?

A dependency DAG structures large engineering initiatives into a directed acyclic graph of work units, allowing orchestrated research, implementation, and tests across agents while preventing merges when dependency failures exist.

How do I enforce quality gates for staged pipeline execution in feature development?

Quality gates enforce a consistent sequence of research, plans, implementation, tests, review, and merge-ready reports per work unit, ensuring each independently verifiable unit meets staged pipeline execution requirements.

Can merge queue safety rules prevent integration failures in a multi-agent workflow?

Yes, merge queue safety rules prevent merges when dependency failures exist, rebase on the latest integration branch, and re-run integration tests after queued merges to maintain integration safety.

What do I need to define before automating RFC-driven feature decomposition?

You need to define explicit unit templates containing an id, depends_on, scope, acceptance_tests, risk_level, and rollback_plan to automate RFC-driven feature decomposition and DAG orchestration correctly.