agentleFS
Sign inStart free
Jason-hub-starJason-hub-star/model-orchestrator/skills/phase-loop/SKILL.md

phase-loop

Skill0 starsChanged 2 months agoMITView on GitHub

Execute an approved implementation plan with three or more phases, running a project-specific gate after every phase, advancing automatically on pass, and stopping on failure. Use for “run the phases”, “phase loop”, or “페이즈루프”; avoid for one small change or a pure test-fix loop.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. awjackson2/phase-skills★ 0same name

    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.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Read the relevant code path and current project rules.

    line 14
  2. Distinctive:

    Run the declared focused check plus applicable type, build, or security gates.

    line 16
  3. Distinctive:

    Check documentation drift and whether any fact blocks the next phase.

    line 17
  4. Distinctive:

    Use one writer by default.

    line 21
  5. Very specific:

    After all phases pass, use evidence-audit.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Phase Loop

Before starting

Each phase must name its outcome, owned paths, verification, and any domain-specific invariant. If those are missing, stop and repair the plan.

For each phase

  1. Read the relevant code path and current project rules.
  2. Make the smallest complete change within the phase boundary.
  3. Run the declared focused check plus applicable type, build, or security gates.
  4. Check documentation drift and whether any fact blocks the next phase.
  5. Record PASS, CONDITIONAL_PASS, or FAIL with direct evidence.
  6. Advance automatically only on pass. Fix a bounded failure inside the phase; otherwise stop and report.

Use one writer by default. Parallelize read-only checks or explicitly disjoint paths, never competing edits to a shared hub file.

Stop conditions

  • The plan’s ordering or assumptions are wrong.
  • Required authorization, data, or external state is missing.
  • The same serious failure repeats without a new hypothesis.
  • A phase would cross its declared boundary.

Next

After all phases pass, use evidence-audit. If the plan itself failed, return to converge-plan.

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.

Check your setup, free