loulanyue 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:
iddepends_onscopeacceptance_testsrisk_levelrollback_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