Ralphinho Rfc Pipeline

affaan-m/ECC/skills/ralphinho-rfc-pipeline

by affaan-mef648e01899ba3e8dc6371642deaaf64b4477775No license275K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 4 days ago

Split an RFC into a multi-agent execution DAG — decompose into work units with dependencies and acceptance tests, run research, plan, implement, test, and review per unit, then merge through a queue with re-based branches and final system verification. Use when a feature is too large for a single agent pass, orchestrating RFC-driven multi-agent execution, or managing merge queues across agent-built units.

AI-generated overview

Splits an RFC into a multi-agent execution DAG with work units, dependencies, acceptance tests and a merge queue.

What it does
Provides a staged pipeline for turning a large RFC into independently verifiable work units, covering intake, DAG decomposition, unit assignment, implementation, validation, merge queue integration and final system verification. It defines a unit spec template with fields such as id, depends_on, scope, acceptance_tests, risk_level and rollback_plan, plus complexity tiers and a per-unit quality pipeline. It also specifies merge queue rules and a recovery procedure for stalled units, and lists outputs such as an RFC execution log, unit scorecards, a dependency graph snapshot and an integration risk summary.
When to use it
Use when a feature is too large for a single agent pass and must be split into independently verifiable work units. Also suited to orchestrating RFC-driven multi-agent execution or managing merge queues across agent-built units.
Requirements
Instructions only; ships no scripts. It assumes an agent environment capable of running multiple work units, branches and integration tests.

Ralphinho RFC Pipeline

Inspired by humanplane style RFC decomposition patterns and multi-unit orchestration workflows.

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

Pipeline Stages

  1. RFC intake
  2. DAG decomposition
  3. Unit assignment
  4. Unit implementation
  5. Unit validation
  6. Merge queue and integration
  7. Final system verification

Unit Spec Template

Each work unit should include:

  • id
  • depends_on
  • scope
  • acceptance_tests
  • risk_level
  • rollback_plan

Complexity Tiers

  • Tier 1: isolated file edits, deterministic tests
  • Tier 2: multi-file behavior changes, moderate integration risk
  • Tier 3: schema/auth/perf/security changes

Quality Pipeline per Unit

  1. research
  2. implementation plan
  3. implementation
  4. tests
  5. review
  6. merge-ready report

Merge Queue Rules

  • Never merge a unit with unresolved dependency failures.
  • Always rebase unit branches on latest integration branch.
  • Re-run integration tests after each queued merge.

Recovery

If a unit stalls:

  • evict from active queue
  • snapshot findings
  • regenerate narrowed unit scope
  • retry with updated constraints

Outputs

  • RFC execution log
  • unit scorecards
  • dependency graph snapshot
  • integration risk summary

Source and attribution

Source:affaan-m/ECCinskills/ralphinho-rfc-pipelineat commitef648e0

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal