Skip to content
cccskills
FreePublished on GitHubEnglish overview

ralphinho-rfc-pipeline

Break an RFC, a written design proposal, into work units with dependencies and acceptance tests for multiple agents. Organize research, implementation, testing, review, queued merges, and final system verification for features too large for one pass.

OriginalShow the original description

Split an RFC into a multi-agent execution DAG — decompose into work units with dependencies and acceptance tests, run research, plan, implement, test, and review per unit, then merge through a queue with re-based branches and final system verification. Use when a feature is too large for a single agent pass, orchestrating RFC-driven multi-agent execution, or managing merge queues across agent-built units.

AI rating80/ 100See how to install

Good for

  • Splitting a large design proposal into verifiable work units
  • Assigning dependent tasks to multiple agents
  • Managing review and queued merges of agent-built branches
  • Narrowing and retrying stalled work units

Overview

What it does

This skill organizes a multi-agent workflow by splitting a large feature RFC, a written design proposal, into independently verifiable work units. Each unit receives an ID, dependencies, scope, acceptance tests, risks, and a rollback plan. Work proceeds through research, planning, implementation, testing, and review. Changes are then merged in sequence before the whole system is verified.

When it helps

Use it for features too large for one agent pass, or when several changes must be combined according to their dependencies. It groups change complexity into three tiers and produces an execution log, unit scorecards, a dependency diagram, and an integration risk summary. If work stalls, it preserves the findings and organizes a retry with a narrower scope.

Example requests

  • “Split this RFC into work units with dependencies and acceptance tests.”
  • “Organize the merge order and verification steps for each agent’s changes.”
  • “Save the findings from this stalled task and propose a narrower retry.”

Notes

Do not merge work with unresolved dependency failures. Each work branch must be rebased onto the latest integration branch, and integration tests must run after every merge. Final system verification is required in addition to unit-level tests.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodThe source explicitly covers splitting an oversized RFC and progressing from assignment through integration and final verification.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
AGoodSeven stages, six unit specification fields, merge rules, and recovery steps for stalled work are provided.
SafetyAre sending data, deleting files, and running commands disclosed?
BPartly lackingRebase and merge rules are given, but confirmation before history changes and conflict handling are not documented.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingMultiple agents, branches, and rebasing are assumed, but execution environment setup is not provided.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

accessibility

FreeSummaryAI rating 100

Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.

  • Adding descriptive labels to icon-only buttons
  • Reviewing keyboard navigation and modal focus
  • Checking contrast and control sizes
affaan-m/ECC286.1KUpdated Oct 21, 2026

agent-architecture-audit

FreeSummaryAI rating 80

Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.

  • Investigating failures that appear only inside an agent application
  • Tracing old conversation content leaking into new sessions
  • Checking skipped or falsely claimed tool execution
affaan-m/ECC286.1KUpdated Oct 21, 2026

agent-eval

FreeSummaryAI rating 80

Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.

  • Comparing coding agents on real development tasks
  • Evaluating a new tool or model before adoption
  • Checking performance after agent updates
affaan-m/ECC286.1KUpdated Oct 21, 2026

agent-harness-construction

FreeSummaryAI rating 100

Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.

  • Define an AI agent’s tool set and input formats
  • Make tool results and next steps easier to interpret
  • Specify safe retries and stopping conditions
affaan-m/ECC286.1KUpdated Oct 21, 2026

agent-introspection-debugging

FreeSummaryAI rating 100

Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.

  • Diagnosing repeated tool calls with no progress
  • Investigating quality loss as context grows
  • Checking file paths and environment mismatches
affaan-m/ECC286.1KUpdated Oct 21, 2026

agent-introspection-debugging

FreeSummaryAI rating 100

Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.

  • Diagnosing repeated failures in an agent run
  • Investigating loops through the same tool calls
  • Reviewing output degradation as context grows
affaan-m/ECC286.1KUpdated Oct 5, 2026

See all skills by affaan-m

Report a problem with this skill