ralphinho-rfc-pipeline

Decompose large features into verifiable work units with a quality-gated pipeline.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill ralphinho-rfc-pipeline-jamkris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralphinho-rfc-pipeline
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/ralphinho-rfc-pipeline
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill ralphinho-rfc-pipeline-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill when a feature is too large for a single agent pass and must be split into independently verifiable work units.

Core Features & Use Cases

  • RFC intake and DAG decomposition to break complex features into manageable work units.
  • Unit assignment, implementation, and validation to ensure traceable progress.
  • Merge queue rules and recovery strategies to maintain integration quality and guardrails.
  • Final system verification and production-ready reporting to close the loop.

Quick Start

Describe your feature as RFC units and let the system decompose it into verifiable work units.

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 feature into verifiable work units for multi-agent workflows?

Feature decomposition uses RFC intake and DAG decomposition to break large features into independently verifiable work units for multi-agent environments. This ensures traceable progress and integration-ready reporting.

What is an RFC-driven pipeline for multi-agent orchestration?

An RFC-driven pipeline orchestrates multi-agent workflows by covering RFC intake, unit assignment, implementation, and validation. It applies quality-gated merge rules and recovery strategies to produce integration-ready reports.

How do I manage merge integration and recovery strategies across multiple agents?

Manage merge integration across multiple agents using merge queue rules and recovery strategies within a quality-gated pipeline. This maintains integration quality and guardrails during feature implementation and final system verification.

When do I need DAG decomposition for complex feature implementation?

DAG decomposition is needed when a feature is too large for a single agent pass and must be split into manageable, independently verifiable work units. It enables traceable unit assignment and validation.

Does the pipeline support unit specs and quality gates for integration validation?

The pipeline implements quality-gated validation with unit specs to ensure traceable progress. It verifies work units before merge integration, closing the loop with final system verification and production-ready reporting.

What are the limitations of using a quality-gated pipeline for multi-agent feature decomposition?

The pipeline requires features to be described as RFC units before decomposition begins. It is designed for large features needing independent work units, so smaller single-agent tasks may not benefit from its overhead.