Handoff contract
Skill lightarktech/founder-coding-skills/skills/handoff-contract
Claude Code skills for non-technical founders, solopreneurs & one-person companies running an AI engineering team — no coding experience required. Six battle-tested skills + a real token-burn postmortem.
npx -y skills add lightarktech/founder-coding-skills --skill handoff-contractAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Write a self-contained handoff when work moves to a new session, a different AI tool, or another person. Use when context is about to be lost — quota exhausted, switching tools, ending a session mid-project.
SKILL.md
1.6 KB, 305 tokens by cl100k_base, as published. Nobody here has run it
The receiver knows nothing. Not your conversation, not your decisions, not your file layout. A handoff that assumes shared memory silently loses work — we watched a receiving tool merge a pull request into a dead branch because the handoff skipped one re-review rule, and the work vanished for days before anyone noticed.
A handoff must contain
- Status snapshot — what is done, and how it was verified (test counts, CI links). Not "mostly finished".
- Rules of the road — the 5–8 constraints that actually bind (what never to touch, what needs approval, what "tests may not be weakened" means here). Not your whole culture doc.
- Environment recipe — exact commands to reach a working state, copy-pasteable.
- Task list with per-task exit conditions — each task states its own observable "done".
- Overall exit — when the whole handoff is complete, in checkable terms.
- Not-yours list — parked items and escalation paths, so the receiver doesn't "helpfully" wander into them.
- File map — where the five things they'll look for actually live.
Write facts, not vibes. Every claim verifiable, every exit observable.
Success criteria
The stranger test: someone with zero context could execute the handoff end to end. If any step requires "ask the previous session", the handoff failed.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.