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 everything-claude-code

Install

Run in your terminal

npx claudepluginhub binzetss/mobile-hvgllocal

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

frontend-patterns

Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.

everything-claude-code

139.2k

foundation-models-on-device

Integrates Apple's FoundationModels for on-device LLM in iOS 26+ apps: text generation, @Generable structured output, tool calling, snapshot streaming.

everything-claude-code

139.2k

flutter-dart-code-review

Reviews Flutter/Dart code with library-agnostic checklist for widget best practices, state management patterns, Dart idioms, performance, accessibility, security, and clean architecture.

everything-claude-code

139.2k

Stats

Stars1

Forks0

Last CommitApr 4, 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