agentleFS
FmarzochiFmarzochi/EGC/skills/general_part2/ralphinho-rfc-pipeline/SKILL.md

ralphinho-rfc-pipeline

Skill61 starsChanged 2 months agoApache-2.0View on GitHub

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

12 other projects use a version of this, 12 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use prediction-market-oracle-research.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • renepfSkill

    prediction-market-oracle-research

    Research prediction markets as data sources or oracle signals for products, agents, dashboards, and corporate decision intelligence. Use for source-grounded analysis of market-implied probabilities, caveats, and integration patterns without investment advice.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 4 are common, 0 are distinctive, and 0 are very specific to this project.

  • 4

    Common

    Most of the 11 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Common:

    Use this skill when a feature is too large for a single agent pass and must be split into independently verifiable work units.

    line 9
  2. Common:

    Never merge a unit with unresolved dependency failures.

    line 48
  3. Common:

    Always rebase unit branches on latest integration branch.

    line 49
  4. Common:

    If a unit stalls:

    line 54

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ralphinho RFC Pipeline

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.