approve
Skill6 starsChanged 27 days agoMITView on GitHub
Owner-only. Approve (or reject) a project document — intent, spec, plan or ADR —, mark a finished plan live, set the byte budget of the always-loaded text, or lower the drill's floor. Usage /approve [intent | spec N | plan N | live N | adr N | reject adr N reason | budget N | floor N]; no arguments lists what waits for the owner.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- iadr-dev/greenlighttheir own version, first seen Oct 20, 2026
- drobins25/crafttheir own version, first seen Oct 11, 2026
- synaptiai/bdsktheir own version, first seen Apr 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- drobins25/craft★ 73same name
- iadr-dev/greenlight★ 2same name
- synaptiai/bdsk★ 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adrSkill
- feature-planSkill
- intentSkill
- observatorySkill
- orchestrateSkill
- reflectSkill
- session-closeSkill
- specSkill
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 3 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
- Distinctive: line 25
If the result starts with ✅ — save it at once, without asking: git add -u plus the approved document's own path (a new document may still …
- Very specific: line 30
If it starts with ❌ — explain in plain Georgian what is missing and offer to fix it (for example a broken link or a missing spec: link).
- Very specific: line 33
Never run tools/approve.py yourself, never edit memory/approvals.md, never set an approval status by hand — the guard refuses it and the …
“Common” is measured: kept by at least 6 in 10 of the 3 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
/approve — the owner's decision
The owner has just run this command. The result below comes from tools/approve.py; it has ALREADY
been applied (or refused). Nothing is waiting for you to approve. live N marks a finished (done) plan
live — the person saw it working, published it and the pilot is over — and moves the project to stage 6,
run and observe (ADR-0013). floor N lowers the drill's floor — the number of cases the drill must hold —
after the person heard why cases left the drill (ADR-0015).
Result:
!bash .claude/hooks/py.sh tools/approve.py '$ARGUMENTS'
Your job now:
- Tell the owner the result in 1–3 Georgian sentences: what was approved, rejected or refused, and the next step the result names. Plain words; gloss a technical term the first time.
- If the result starts with ✅ — save it at once, without asking:
git add -uplus the approved document's own path (a new document may still be untracked), then a CHECKPOINT commit whose command and message do not name the ledger file (the guard refuses a command that does). Do not edit the approved document. Then go straight on to the next step the result names — the approval is the person's go-ahead, so never ask "shall I save?" or "shall I continue?". - If it starts with ❌ — explain in plain Georgian what is missing and offer to fix it (for example a
broken link or a missing
spec:link); the owner then runs /approve again.
Never run tools/approve.py yourself, never edit memory/approvals.md, never set an approval status
by hand — the guard refuses it and the LEDGER gate flags it. (Owner's note: avoid the ' character
inside the note text — it breaks the shell quoting.)
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.

