loop-dog-food
Skill0 starsChanged 5 months agoMITView on GitHub
Turn a spec, plan, orchestration pattern, or other work object into a bounded loop with visible state, a turn budget, review gates, and proof commands.
In this repository11 other files it gives its agents.
- loop-anythingSkill
- loop-dog-foodSkill
- loop-proveSkill
- loop-recordSkill
- loop-reviewSkill
- loop-triageSkill
- loop-anythingSkill
- loop-proveSkill
- loop-recordSkill
- loop-reviewSkill
- loop-triageSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when the operator wants the repo, spec, plan, or orchestration pattern to improve itself through the loop.
- Distinctive: line 23
Treat the work object as the current goal surface.
- Very specific: line 28
Keep permission boundaries visible in loop-state.md.
- Distinctive: line 29
Stop if the loop needs destructive action, hidden credentials, broader permissions, or proof that cannot be run.
- Very specific: line 42
Update loop-state.md with the chosen task, proof command, stop condition, and next action.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Loop Dog Food
Use this skill when the operator wants the repo, spec, plan, or orchestration pattern to improve itself through the loop.
Inputs
loop-state.mdloop-contract.mdloop-decisions.mdloop-prompts.md- A named work object, such as a spec, plan, branch, issue, repo area, or orchestration pattern
- A turn budget:
single,multi, orinfinite
Process
- Treat the work object as the current goal surface.
- Zoom out enough to identify the highest-leverage next loop task.
- Choose exactly one bounded task unless the turn budget explicitly permits additional iterations.
- Name the proof command before implementation starts.
- Keep permission boundaries visible in
loop-state.md. - Stop if the loop needs destructive action, hidden credentials, broader permissions, or proof that cannot be run.
Turn Budgets
single: complete one bounded iteration, record it, then stop.multi: continue while proof stays green and the state board names a next action.infinite: continue while compute and permission boundaries allow, but never bypass review, proof, or stop conditions.
Output
Update loop-state.md with the chosen task, proof command, stop condition, and
next action. Record durable decisions in loop-decisions.md.
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
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.

