Ralphinho Rfc Pipeline

by affaan-mef648e01899bNo license275K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 days ago

RFC駆動の複数エージェントDAG実行パターン、品質ゲート、マージキュー、ワークユニットオーケストレーション。

AI-generated overview

Orchestrates large features as RFC-driven multi-agent work units with DAG dependencies, quality gates and a merge queue.

What it does
This skill defines a pipeline for breaking a feature that is too large for a single agent pass into independently verifiable work units. It covers RFC intake, DAG decomposition, unit assignment, implementation, validation, merge queue integration and final system verification. It supplies a unit spec template, complexity tiers, a per-unit quality pipeline, merge queue rules and recovery steps, and it produces an RFC execution log, unit scorecards, a dependency graph snapshot and an integration risk summary.
When to use it
Use it when a feature must be split into independently verifiable work units because a single agent path is too large. It suits multi-unit orchestration where dependency ordering, per-unit quality gates and controlled merging matter.
Requirements
Instructions only; no scripts are shipped. It assumes a multi-agent or multi-unit execution environment with version control branches and integration tests.

Ralphinho RFC Pipeline

humanplane スタイルのRFC分解パターンと複数ユニットオーケストレーションワークフローにインスパイア。

単一エージェントパスでは大きすぎる機能を独立して検証可能なワークユニットに分割する必要がある場合、このスキルを使用します。

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

各ワークユニットに含める:

  • 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

ユニットが stall した場合:

  • 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

Source and attribution

Source:affaan-m/eccindocs/ja-JP/skills/ralphinho-rfc-pipelineat commitef648e0

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal