Skill

ralphinho-rfc-pipeline

Orchestrates large features via RFC decomposition into verifiable work units in a multi-agent DAG, with quality gates, merge queues, complexity tiers, and recovery. Use for complex, multi-pass tasks.

code-quality

developer-tools

From atum-system

Install

Run in your terminal

npx claudepluginhub arnwaldn/atum-system --plugin atum-system

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.4k

paypal-integration

Integrates PayPal payments with express checkout, subscriptions, refunds, and IPN. Includes JS SDK for frontend buttons and Python REST API for backend capture.

payment-processing

33.0k

Stats

Stars0

Forks0

Last CommitMar 21, 2026

Actions

View Source View Plugin View on GitHub View README

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

RFC intake
DAG decomposition
Unit assignment
Unit implementation
Unit validation
Merge queue and integration
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

research
implementation plan
implementation
tests
review
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