Skip to content
Back to skills

Ralphinho Rfc Pipeline

ASecurity

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

  • 272 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 11, 2026
testinggitsecurity

Security analysis

A100/100

Scanned June 11, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Ralphinho Rfc Pipeline?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ralphinho Rfc Pipeline
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/loulanyue-ralphinho-rfc-pipeline/badge)](https://www.skillsdirectory.com/skills/loulanyue-ralphinho-rfc-pipeline)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ralphinho-rfc-pipeline
description: RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
source_path: skills/ralphinho-rfc-pipeline/SKILL.md
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

## 원문
- [영문 원문](../../../../skills/ralphinho-rfc-pipeline/SKILL.md)

## 탐색
- [한국어 문서 안내](../../README.md)
- [기여 가이드](../../../../CONTRIBUTING.md)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…