Ralphinho rfc pipeline

Skill loulanyue/awesome-claude-notes/skills/ralphinho-rfc-pipeline

RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.From its SKILL.md

Install

npx -y skills add loulanyue/awesome-claude-notes --skill ralphinho-rfc-pipeline

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.5 KB, 307 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most plan spec skills give in 307 tokens

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

Ask one question at a timein 73 of 1360
Write the spec using the templatein 22 of 1360
Ask clarifying questions if neededin 19 of 1360, across 18 files
Wait for user confirmation before proceedingin 19 of 1360
Save plans to the plans directoryin 17 of 1360, across 13 files
Check for product marketing context firstin 16 of 1360, across 5 files
Read the plan file completelyin 16 of 1360
Order tasks by dependencyin 16 of 1360
Gather context from the conversationin 15 of 1360, across 9 files
Explore the codebase instead of askingin 15 of 1360, across 13 files
Wait for explicit user approvalin 14 of 1360, across 13 files
Quiz the user on the breakdownin 13 of 1360, across 7 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.