ralphinho-rfc-pipeline

Orchestrates RFC decomposition into a dependency-aware DAG of work units.

Updated Sep 13, 2025

Search Tags:#multi-agent #quality gates #rfc #dependency graph #merge queue #dag orchestration #work unit orchestration

Ready to run

npx skills add https://github.com/llmh333/employee_management_spring --skill ralphinho-rfc-pipeline-llmh333

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ralphinho-rfc-pipeline
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/ralphinho-rfc-pipeline
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill ralphinho-rfc-pipeline-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of delivering large, cross-cutting changes by breaking RFC-driven work into independent units that can be validated and merged without destabilizing the main integration branch.

Core Features & Use Cases

RFC-driven decomposition: Turns an incoming RFC into a DAG of smaller, independently verifiable work units.
Quality-gated unit execution: Assigns units, runs research and implementation planning per unit, and enforces validation and review before anything merges.
Merge queue safety rules: Prevents integration of units with unresolved dependency failures and requires rebasing and re-running integration tests after queued merges.

Quick Start

Use ralphinho-rfc-pipeline to split a large RFC into a dependency-aware set of work units, execute each with quality gates, then merge via a guarded queue with integration verification.

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 merge-ready work units?▼

To decompose a large RFC, this Skill orchestrates the document into a dependency-aware DAG of smaller work units, each independently verifiable with acceptance tests before merging. Units are executed through quality gates and a guarded merge queue.

What is dependency-aware DAG orchestration for RFC delivery?▼

Dependency-aware DAG orchestration maps RFC work units into a directed acyclic graph, tracking dependencies so units are implemented, tested, and merged safely without destabilizing the main integration branch.

How do merge queue rules handle rebasing and integration tests for staged work units?▼

Merge queue rules require rebasing and re-running integration tests after queued merges, preventing the integration of work units with unresolved dependency failures to maintain branch stability.

Can I use multi-agent workflows with quality gates for cross-cutting feature changes?▼

Yes, multi-agent workflows are supported by assigning work units, running research and implementation planning per unit, and enforcing validation and review through quality gates before any unit merges.

What is the recovery process for stalled work units in a dependency graph?▼

The recovery process for stalled units requires per-unit scope specification with acceptance tests and dependency tracking, allowing blocked units to be addressed without disrupting the broader DAG orchestration.

When should I not use RFC-driven decomposition for feature delivery?▼

RFC-driven decomposition is not suited for small, isolated changes that lack cross-cutting dependencies, as the overhead of DAG orchestration, per-unit scope specification, and merge queue rules outweighs the benefits of independent verification.