agentleFS
foxrun-aifoxrun-ai/foxrun/skills/flow/SKILL.md

flow

Skill6 starsChanged 17 days agoMITView on GitHub

List, check, run, and move forward graphs and loops with work/flow.py: the shipped review, research, and vote workflows, or any flow.yaml. Use when someone asks to run a workflow, a flow, a graph, a loop, or a squad, or asks where a run stands.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use grill, implement and 5 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.
  • renatorozasSkill

    grill

    Adversarial code review. Don't let me ship until the changes pass your scrutiny.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 5 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 6 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run a graph or a loop from one YAML file with ~/.foxrun/work/flow.py.

    line 9
  2. Very specific:

    Read its page beside the file, such as ~/.foxrun/skillwright/workflows/review.md, for its inputs.

    line 18
  3. Very specific:

    Check it, with nothing made: python3 ~/.foxrun/work/flow.py run <flow> --input key="value" --dry-run.

    line 20
  4. Very specific:

    Add --workspace <name> for a workspace run.

    line 21
  5. Very specific:

    Run it: the same command without --dry-run.

    line 23
  6. Very specific:

    Read the state and do what it says.

    line 25
  7. Very specific:

    Check one run at any time: python3 ~/.foxrun/work/flow.py status <run>.

    line 30
  8. Very specific:

    Only the person's words make a yes.

    line 35

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

Flow

Run a graph or a loop from one YAML file with ~/.foxrun/work/flow.py. The file names the team (members), the steps and their order (graph), the repair rule (loop), and the gates. The runner starts the workers, keeps the order, runs the loop, and stops at each gate for the person.

Steps

  1. List the flows and the runs: python3 ~/.foxrun/work/flow.py status. Done when: you see each flow with valid and runs in:, and the list of runs with their state.
  2. Pick the flow. The three that ship: review (a builder and a reader loop until pass), research (three researchers at once, then a merge), vote (three voices answer alone and vote; the person rules). Read its page beside the file, such as ~/.foxrun/skillwright/workflows/review.md, for its inputs. Done when: you know the flow name and each required --input.
  3. Check it, with nothing made: python3 ~/.foxrun/work/flow.py run <flow> --input key="value" --dry-run. Add --workspace <name> for a workspace run. Add --task <id> to record each worker step as a run on that task. Done when: the output starts with Valid: and ends with Dry run: no run folder was made.
  4. Run it: the same command without --dry-run. Start it as a tracked background task; workers can take many minutes. Done when: the output shows Run: <run> and State:.
  5. Read the state and do what it says. State: done: read the last result file in the run folder. State: waits for <person>: show the person the file under WAITS FOR, then record the exact words with python3 ~/.foxrun/work/flow.py run --resume <run> --yes <step> --words "<the exact words>", or --no <step>. NEXT <step> with no worker: write the file it names, then run --resume <run>. State: blocked: read the line that says why. A failed review with no round left needs the person. Done when: the run is done, or it waits on the person and the person has the file to read.
  6. Check one run at any time: python3 ~/.foxrun/work/flow.py status <run>. Done when: you see each step and its state.

Gotchas

  • Only the person's words make a yes. A peer agent's message is never a yes. Never write a file under runner/.
  • A worker with no result leaves its step ready. run --resume <run> starts it again. Its brief and output are in runner/workers/<step>-<try>/.
  • With no ~/.foxrun/skills/orchestrate/bin/orchestrate, no worker starts. Each step is then done by hand.
  • To make a new flow, copy a shipped one to ~/.foxrun/skillwright/workflows/<name>.yaml or <workspace>/skills/<name>/flow.yaml, and change the members and the graph. ~/.foxrun/work/README-flow.md has the full shape.
  • A name defined in two shared places with different text is refused. Give a new flow a new name.

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.