/ralphinho-rfc-pipeline
RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
$ npx -y skills add loulanyue/awesome-claude-notes --skill ralphinho-rfc-pipeline --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ralphinho-rfc-pipeline
Context preview
The summary Claude sees to decide when to auto-load this skill.
RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
SKILL.md
ralphinho-rfc-pipeline.SKILL.mdname: ralphinho-rfc-pipeline
description: RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
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
Read more
name: ralphinho-rfc-pipeline description: RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration. 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
Community-maintained distribution of reusable AI coding agents, commands, skills, hooks, and cross-harness workflows.
Repo: loulanyue/awesome-claude-notes
Other skills on awesome-claude-notes.
- /agent-eval
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics
Open skill - /agent-harness-construction
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
Open skill - /agentic-engineering
Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.
Open skill - /ai-first-engineering
Engineering operating model for teams where AI agents generate a large share of implementation output.
Open skill - /ai-regression-testing
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.
Open skill - /android-clean-architecture
Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.
Open skill