agentleFS
Sign inStart free
ibahgatibahgat/oh-my-iflow/skills/ralph/SKILL.md

ralph

Skill2 starsChanged 8 months agoMITView on GitHub

Run strict quality-gated orchestration where every completion claim must pass verification gates.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for high-confidence delivery where quality gates are mandatory.

    line 8
  2. Very specific:

    If verification fails, run team-fix and return to team-verify.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 39 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

Purpose

Use this skill for high-confidence delivery where quality gates are mandatory.

Trigger

  • User prioritizes correctness/reliability over raw speed
  • Task has high regression risk
  • Release-readiness decision is required

Workflow

  1. Execute full pipeline: team-plan -> team-prd -> team-exec -> team-verify.
  2. If verification fails, run team-fix and return to team-verify.
  3. Repeat until acceptance criteria pass or blockers are explicit.
  4. Summarize gate evidence and final ship decision.

Rules

  • Never skip team-verify.
  • No "done" status without criterion-level pass evidence.
  • Separate blockers from unresolved nice-to-haves.

Output Template

## Mode
- ralph

## Gate Board
| Gate | Status | Evidence |
| --- | --- | --- |

## Risks
- ...

## Ship Decision
- ready / not ready

Download now (ZIP)

  • Other versions43 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 43

    1. Yeachan-Heo/oh-my-claudecode★ 40ksame name
    2. Yeachan-Heo/oh-my-claude-sisyphus★ 40ksame name
    3. Yeachan-Heo/oh-my-codex★ 34ksame name
    4. snarktank/ralph★ 22ksame name
    5. Q00/ouroboros★ 6.3ksame name
    6. zereight/gitlab-mcp★ 2.1ksame name
    7. srid/emanote★ 963same name
    8. opentabs-dev/opentabs★ 926same name
    9. first-fluke/fullstack-starter★ 223same name
    10. team-attention/hoyeon★ 173same name

    33 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use configure-notifications, ai-slop-cleaner and 6 more.

    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.
    • Jurel89Skill

      configure-notifications

      Wire Telegram / Discord / Slack notifications for copilot-omni run events (start, progress, completion, error)

      Also in 4 projects that use this

    • Jurel89Skill

      ai-slop-cleaner

      Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

      Also in 5 projects that use this

    • JokerRunSkill

      compound-engineering

      Compound Engineering workflow for AI-assisted development. Use when planning features, executing work, reviewing code, or codifying learnings. Follows the Plan → Work → Review → Compound loop where each unit of engineering makes subsequent work easier. Triggers on: plan this feature, implement this, review this code, compound learnings, create implementation plan, systematic development.

      Also in 3 projects that use this

    • klauswgSkill

      deep-interview

      在明确批准执行之前，通过数学化歧义门控进行苏格拉底式深度访谈

      Also in 6 projects that use this

    • Yeachan-HeoSkill

      ultragoal

      Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

      Also in 3 projects that use this

    • +3 more from Jurel89
  • In this repository24 other files it gives its agents.

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.

Check your setup, free