ralphinho-rfc-pipeline

Decompose large software features into verifiable work units via RFC-style decomposition.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lllooollpp/solopreneur- --skill ralphinho-rfc-pipeline-lllooollpp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralphinho-rfc-pipeline
Source: https://github.com/lllooollpp/solopreneur-/tree/main/solopreneur/data/skills/ralphinho-rfc-pipeline
Command: npx skills add https://github.com/lllooollpp/solopreneur- --skill ralphinho-rfc-pipeline-lllooollpp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposes large software features into independently verifiable work units using RFC-style decomposition, enabling clearer scope, traceability, and incremental delivery.

Core Features & Use Cases

  • RFC intake and DAG-based decomposition into verifiable work units.
  • Unit assignment, implementation, validation, and merge-ready reporting.
  • Quality gates, merge queue rules, and controlled integration across teams.
  • Recovery paths for stalled units and auditable execution logs.
  • Use Case: When delivering complex features that span multiple teams, apply this skill to structure work, validate each unit, and ensure end-to-end correctness.

Quick Start

Run the RFC pipeline on a feature to automatically decompose it into verifiable work units and kick off the 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 decompose large software features into verifiable work units?

You can decompose large software features into verifiable work units using RFC-style decomposition. This approach breaks down complex feature development into independent units that can be tracked and validated across teams.

How does DAG-based orchestration manage multi-agent feature development?

DAG-based orchestration manages multi-agent feature development by mapping RFC intakes into a directed acyclic graph. This structures the work units, applies quality gates, and coordinates merge queues to ensure controlled integration.

What is the best way to track and validate complex feature development across multiple teams?

The best way to validate complex features across teams is applying structured unit specification and quality gates. This ensures each decomposed work unit is independently implemented, validated, and tracked for end-to-end correctness.

Can I recover stalled work units during multi-agent orchestration?

Yes, you can recover stalled work units during multi-agent orchestration. The pipeline includes recovery paths for stalled units and maintains auditable execution logs to resume and track progress.

When do I need RFC-style decomposition for software engineering projects?

You need RFC-style decomposition when delivering complex software features that span multiple teams. It provides clearer scope, traceability, and incremental delivery by splitting work into independently verifiable units.

How do merge queue rules integrate with quality gates in multi-agent pipelines?

Merge queue rules integrate with quality gates to control multi-agent pipelines by enforcing validation checks before integration. This guarantees each work unit meets specified requirements before merging into the main branch.