write-handoff
Skill1 starsChanged 4 days agoMITView on GitHub
Build features/<slug>/handoff.md for a coding agent from approved steps and approved brain entries only. Use when someone says "write the handoff" or "hand this to the coding agent".
7 other projects use a version of this.
Adopted by
Most recently taken up by
- adhamhaithameid/write-skillstheir own version, first seen Nov 8, 2026
- orkeren21/shipshapetheir own version, first seen Nov 3, 2026
- koruworks/skillstheir own version, first seen Oct 15, 2026
- kitloomlk-stack/research-knowledge-kittheir own version, first seen Oct 15, 2026
- uzampogn/dual-loop-harnesstheir own version, first seen Oct 15, 2026
- akimisri17/idea-to-app-kittheir own version, first seen Oct 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- adhamhaithameid/write-skills★ 1same name
- jayden-dang/skills★ 1same name
- orkeren21/shipshape★ 1same name
- uzampogn/dual-loop-harness★ 1same name
- akimisri17/idea-to-app-kit★ 0same name
- kitloomlk-stack/research-knowledge-kit★ 0same name
- koruworks/skills★ 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brain-healthSkill
- captureSkill
- plan-in-nine-stepsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
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 12
Ask which feature (features/<slug>/).
- Distinctive: line 14
Read only the approved steps.
- Very specific: line 16
Write features/<slug>/handoff.md using features/_template/handoff.md:
- Distinctive: line 24
Add the date and the list of approved steps used at the top.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Write handoff
Builds a frozen bundle from approved work. Drafts are left out.
How to run it
- Ask which feature (
features/<slug>/). Readbrief.mdand its steps table. - List the steps marked
approvedand the steps markednot needed(with reasons). If the implementation plan (08) is not approved, stop and say so. - Read only the approved steps. Ignore any step marked draft or not started.
- Collect the entry IDs those steps cite. Open each one in
brain/and keep only entries withstatus: approved. If a cited entry is nowreplacedorstopped, stop and tell the person. - Write
features/<slug>/handoff.mdusingfeatures/_template/handoff.md:- Objective: two sentences, from the approved executive summary (01).
- Plan: from the approved plan, in order, with where to look first.
- Rules that apply: each approved rule in full, with ID and severity.
- Decisions that apply: ID plus one line each.
- Open questions: id, question, blocking level and owner. Blocking ones go first.
- Steps not needed, with reasons.
- End with "Stop and ask if unsure".
- Add the date and the list of approved steps used at the top.
- Tell the person where the file is, and which steps and entries went in. Remind them the PR template asks which entries the change touched.
Do not
- Include draft steps, proposed entries or anything in
brain/inbox/. - Summarise a rule. Rules go in full.
- Send stories to a tracker. That needs a person's OK.
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.

