Skill

ralphinho-rfc-pipeline

From ecc

Orchestrates large features via RFC decomposition into verifiable work units in a multi-agent DAG, with quality gates, merge queues, complexity tiers, and recovery. Use for complex, multi-pass tasks.

code-quality

developer-tools

npx claudepluginhub jevonthompsonx/todo.tsx

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Inspired by [humanplane](https://github.com/humanplane) style RFC decomposition patterns and multi-unit orchestration workflows.

SKILL.md

Similar Skills

ralphinho-rfc-pipeline

149

Orchestrates large features via RFC decomposition into verifiable work units in a multi-agent DAG, with quality gates, merge queues, complexity tiers, and recovery. Use for complex, multi-pass tasks.

awesome-claude-notes

ralphinho-rfc-pipeline

173.8k

Orchestrates complex features via RFC-driven multi-agent DAGs, decomposing into verifiable work units with quality gates, merge queues, and integration verification. Use for large, multi-step tasks beyond single-agent scope.

everything-claude-code

orchestrated-execution

169

Orchestrates 4-phase execution loop (IMPLEMENT, VALIDATE, ADVERSARIAL REVIEW, COMMIT) for complex work units with specs. Verifies outputs adversarially in multi-agent setups.

2 files

metaswarm

Stats

Stars0

Forks0

Last CommitApr 11, 2026

Used By43 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

RFC intake

DAG decomposition

Unit assignment

Unit implementation

Unit validation

Merge queue and integration

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

research

implementation plan

implementation

tests

review

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