handoff-spec
Skill55 starsChanged 2 days agoApache-2.0View on GitHub
Hand a spec that is mid-implementation to another machine or another agent.
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Leave the spec so that session can carry on as if it had been here.
- Distinctive: line 26
Write it into the spec's own handoff, in place: the spec stays one current account, not a transcript with a new note on top.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Handoff Spec
I'm moving this spec's work to another machine or another agent. The next session starts cold: it has the repository and nothing else. It has none of this conversation, none of this machine's files and none of your memory. Leave the spec so that session can carry on as if it had been here.
Collect what this session knows and the spec doesn't yet say, from the discussion and from the work itself, and put it in the spec:
- what is done, what is half-done and exactly where it stopped, and what is next;
- what I decided or corrected along the way, and how I want the work done;
- calls you made where I was silent, and anything still waiting on me;
- what is known to be broken or unverified, with what you already found out about it;
- anything that lives only on this machine and the next session needs: unpushed branches, uncommitted work, scratch results worth keeping.
Write it into the spec's own handoff, in place: the spec stays one current account, not a transcript with a new note on top. Then push, so everything the spec points at exists on the remote.
Done when a fresh agent, given only the repository, would pick the same next step you would, and would not repeat a question I've already answered.
Trending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Other versions9 projects use a version of this.
Word for word · 3
- dzhng/jevgrep★ 3.1k100% same
- dzhng/skills★ 1.4k100% same
- dzhng/yap★ 112100% same
Edited · 0
None found.
Wrote their own version · 6
- launchapp-dev/animus-cli★ 39same name
- sidneyswift/skills★ 9same name
- cskwork/handoff-spec-kit★ 1same name
- miovrag/claude-skills★ 1same name
- aiuxmasters/agentic-design-tools★ 0same name
- tjrice42/design-judgment-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.
Used alongsideProjects with it also use marketing-pages.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dzhngSkillmarketing-pages
Best-practice rulebook for a marketing site's pages, organized by page class — campaign landers, product pages, programmatic SEO trees, editorial. Use when writing or updating a landing/marketing page, wiring a campaign lander to an attribution identifier, changing site-wide nav/footer links, touching sitemap/robots/agent-readable surfaces, or auditing a public site's indexing, reachability, and conversion setup.
Also in 3 projects that use this
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-agentsSkill
- audit-decisionsSkill
- audit-testsSkill
- claudeSkill
- close-specSkill
- code-reviewSkill
- codexSkill
- compare-screenshotsSkill
- debug-memorySkill
- design-with-imagesSkill
- eli5Skill
- eval-skillsSkill
- explore-unknownsSkill
- implement-specSkill
- implement-spec-with-codexSkill
- preview-shotsSkill
- ratchet-filesSkill
- refactor-cleanSkill
- releaseSkill
- reviewSkill
- screenshot-critiqueSkill
- write-docsSkill
- write-evalSkill
- write-skillsSkill
- write-specSkill
- write-testsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.