RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration. Use when running RFC-driven multi-agent execution with quality gates and a merge queue.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add userInner/SKILLS --skill ralphinho-rfc-pipeline--affaan-m-ecc --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ralphinho Rfc Pipeline Affaan M Ecc?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/userinner-ralphinho-rfc-pipeline-affaan-m-ecc)More formats (shields.io, HTML) on the badges page.
---
name: ralphinho-rfc-pipeline
description: RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration. Use when running RFC-driven multi-agent execution with quality gates and a merge queue.
metadata:
origin: ECC
---
# Ralphinho RFC Pipeline
Inspired by [humanplane](https://github.com/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
Is this your skill, or is something wrong with this listing? . Author removals are honored within 72 hours.
No comments yet. Be the first to comment!