affaan-m/ECC

ralphinho-rfc-pipeline

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

68Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "skills/ralphinho-rfc-pipeline"
Automated source guideGeneral workflowStandard source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded usage guide: ralphinho-rfc-pipeline

Inspired by humanplane style RFC decomposition patterns and multi-unit orchestration workflows.

npx skills add https://github.com/affaan-m/ECC --skill "skills/ralphinho-rfc-pipeline"
Check the pinned source

The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.

180 source words · 7 usable sections

Source-declared outputs

  • RFC execution log
  • unit scorecards
  • dependency graph snapshot

Source workflow

Read ralphinho-rfc-pipeline through these 4 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

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

SKILL.md · Pipeline Stages
RFC intakeDAG decompositionUnit assignment
02

Unit Spec Template

Each work unit should include: - id - dependson - scope - acceptancetests - risklevel - rollbackplan

SKILL.md · Unit Spec Template
iddependsonscope
03

Complexity Tiers

Tier 1: isolated file edits, deterministic tests

SKILL.md · Complexity Tiers
Tier 1: isolated file edits, deterministic testsTier 2: multi-file behavior changes, moderate integration riskTier 3: schema/auth/perf/security changes
04

Quality Pipeline per Unit

1. research 2. implementation plan 3. implementation 4. tests 5. review 6. merge-ready report

SKILL.md · Quality Pipeline per Unit
researchimplementation planimplementation

Source checklist

Verify each item before delivery

The source section “Pipeline Stages” has been checked.

The source section “Unit Spec Template” has been checked.

The source section “Complexity Tiers” has been checked.

The source section “Quality Pipeline per Unit” has been checked.

Source output checked: RFC execution log

Source output checked: unit scorecards

Choose a different workflow

When another Skill is the better fit

FAQ

What does the ralphinho-rfc-pipeline source document cover?

Inspired by humanplane style RFC decomposition patterns and multi-unit orchestration workflows.

How do I install ralphinho-rfc-pipeline?

The source record exposes this install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/ralphinho-rfc-pipeline". Inspect the command and pinned source before running it.

Repository stars
234,327
Repository forks
35,711
Quality
68/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

68/100
Documentation14/30
Specificity14/25
Maintenance20/20
Trust signals20/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

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

  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
Source repo
affaan-m/ECC
Skill path
skills/ralphinho-rfc-pipeline/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected