agent-workflows
AGENTS.md3 starsChanged 25 days agoMITView on GitHub
2. When several routes match, reduce them to one by asking with templates/select-option.md: Then continue handling the original request.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 21
When several routes match, reduce them to one by asking with templates/select-option.md:
- Distinctive: line 31
When one route remains, read its workflow file completely and follow it.
- Very specific: line 32
When no route matches, follow workflows/specialist.md with:
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md
Request Routing
For every user request, identify every matching route using this table:
Situation Workflow Select the next eligible item ( /nextor$next)workflows/next.mdResolve a local project directory ( /projector$project)workflows/project.mdCreate or reformulate one item ( /writeor$write)workflows/write.mdFrame an urgent bug report and start delivery ( /hotfixor$hotfix)workflows/hotfix.mdSelect an item, plan it, and start its implementation ( /pickor$pick)workflows/pick.mdCreate an implementation plan ( /planor$plan)workflows/plan.mdDecompose one oversized item into child items ( /refineor$refine)workflows/refine.mdExecute a plan ( /workor$work)workflows/work.mdPrepare work for review ( /readyor$ready)workflows/ready.mdReview a pull or merge request ( /inspector$inspect)workflows/inspect.mdComplete a pull or merge request ( /doneor$done)workflows/done.mdWhen several routes match, reduce them to one by asking with
templates/select-option.md:question: Which workflow do you want to use? options: - label: <matching situation> value: <workflow file>- When one route remains, read its workflow file completely and follow it.
When no route matches, follow
workflows/specialist.mdwith:task_context: available request contextThen continue handling the original request.
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.

