trail
Skill0 starsChanged 3 months agoMITView on GitHub
The way in. Explains what a decision trail is and why git does not give you one, shows the state of this repository's trail, sets it up so every later session maintains it automatically, and routes to the right sub-skill. Use when someone asks what trail is, how to start, what to do next, or simply types the command with nothing after it. Also the setup step — one run per repository installs the convention so the trail is kept even by sessions that do not have this skill. Триггеры — "trail", "как это работает", "с чего начать", "настрой trail", "что такое trail", "trail status", "get started".
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Namann-14/trailtheir own version, first seen Nov 15, 2026
- ntholm86/principles-of-earned-autonomy-skills-suitetheir own version, first seen Nov 11, 2026
- 5throck/ai-workspace-standardstheir own version, first seen Nov 1, 2026
- simota/agent-skillstheir own version, first seen Oct 23, 2026
- selmakcby/claude-code-trailtheir own version, first seen May 26, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- simota/agent-skills★ 99same name
- 5throck/ai-workspace-standards★ 25same name
- ntholm86/principles-of-earned-autonomy-skills-suite★ 4same name
- selmakcby/claude-code-trail★ 1same name
- Namann-14/trail★ 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 repository3 other files it gives its agents.
- trail-distilSkill
- trail-recordSkill
- trail-whySkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
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 43
Every decision carries its source — [operator], [agent] or [project].
- Very specific: line 119
Run it once per repository — after that every session keeps the trail on its own.
- Distinctive: line 120
When you inherit unfamiliar code, ask it *why* before you change anything.
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
Trail
Git versions the code. This versions the reasoning.
One entry point. Say what you want in plain words, or say nothing and get the state of this repository plus the next sensible step.
Language
Answer in the language the person asked in. The files you write follow the repository's own language, detected from its commit history — those are read by the team, not by the asker.
What this is, in sixty seconds
Somebody asks an agent for a change. The agent proposes something. The person says "no, not like that". The agent adjusts, and the work ships.
Git keeps the last step and throws away the other three. The diff survives forever; the
reason it looks like that, the alternative that was rejected, and the correction that
produced it are gone when the session closes. Six months later git blame names a commit
and a date, and nobody can say why the obvious approach was not taken — so somebody takes
it, and rediscovers the reason at full price.
A trail is four things per session, and nothing else:
| DECIDED | a choice where a competent alternative existed — and whose choice it was |
| REJECTED | what was seriously considered and dropped, which leaves no other trace |
| CORRECTION | where the operator changed the direction, in their own words |
| ASSUMED | what was taken on faith, and what being wrong would cost |
Everything testable against one question: could git log -p tell the reader this? If
yes, it does not belong.
The part people underestimate
Every decision carries its source — [operator], [agent] or [project].
Work done with an AI is full of choices nobody consciously made: the model picked
something reasonable, nobody objected, and it became the design. Those are [agent]
decisions, and marking them is what lets a reviewer find them later.
Measured on the first real trail this tool produced, across two sessions: seven
[agent], three [project], two [operator]. In the commit messages for those sessions
all twelve look equally deliberate.
First: where is this repository
git rev-parse --show-toplevel 2>/dev/null || echo "NOT A GIT REPOSITORY"
[ -f .trail/config.yaml ] && echo "trail: set up" || echo "trail: not set up"
find .trail/entries -name '*.md' 2>/dev/null | wc -l
grep -rl 'Trail — decision record' CLAUDE.md AGENTS.md 2>/dev/null || echo "bootstrap: absent"Use find, not a glob. In zsh an unmatched *.md is an error raised by the shell
before the command runs, so 2>/dev/null does not suppress it — and the noise appears on
exactly the repositories where the answer is "nothing here yet", which is the first
impression a new user gets. Found by running this on a repository with no trail.
Report the four lines, then route:
| State | Say |
| Not a git repository | trail anchors entries to commits; without git it still works but the entries are worth much less — offer, do not insist |
| Not set up | offer setup in one line and do it on a yes — see below |
| Set up, no entries | explain what the first trail-record will produce, and offer to run it now against recent commits |
| Set up, entries exist | show the last two, the source ratio, and what is open |
Setup — one run per repository, and then it is automatic
Read references/bootstrap.md before setting anything up.
This is the step that matters most and is easiest to skip. Setup does two things:
- Creates
.trail/— config, index, an emptyentries/ - Writes a short block into the repository's agent-rules file —
CLAUDE.md,AGENTS.md, or whichever the repository already uses
The second is the whole point. That file is loaded by every future session automatically, so the trail gets maintained whether or not anyone remembers this skill exists, and whether or not it is installed. The block carries the entry format inline, so a teammate who clones the repository and has never heard of this tool still writes correct entries.
A tool that only works when you remember to invoke it is a tool that stops being used in about two weeks. This is the answer to that.
Show the block before writing it, and never write it without a yes — project rules change how every future session behaves.
Routing
| They want | Skill |
| To write down what just happened | trail-record |
| To know why some code is the way it is, or whether an idea was already rejected | trail-why |
| To turn repeated corrections into project rules | trail-distil |
| To understand the idea, or to start | this skill |
Route by reading the sub-skill, not by dispatching a subagent. The sub-skill needs the conversation you are in — what was asked, what was corrected, what you decided. A subagent gets none of that and produces a record of nothing.
Where the request is plainly one of the three, go straight there and say which you are using. Explaining the routing to someone who asked a direct question is overhead.
What to tell a person who has never used this
Three sentences, in this order, and then stop:
- Git tells you what changed; this tells you why, whose call it was, and what was rejected.
- Run it once per repository — after that every session keeps the trail on its own.
- When you inherit unfamiliar code, ask it why before you change anything.
Do not explain the file format unprompted. People adopt this because of the question it answers, not because of a markdown schema.
Non-goals
- Committing, pushing, or opening anything.
- Editing the agent-rules file without approval.
- Replacing commit messages, code review, or an architecture decision record. It records what those three all omit.
- Recording everything. Four kinds of thing qualify; the rest is narration.
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.

