write-handoff
/write-handoff
Updates a work item's handoff.md and moves its status so a fresh session or another role can continue. Use before stopping work, when switching roles, or whenever a work item changes state.
- Author
- The-Urcydo ↗
- Repository
- Repo-Template ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Updates a work item's handoff.md and moves its status so a fresh session or another role can continue. Use before stopping work, when switching roles, or whenever a work item changes state.
Original author description
Updates a work item's handoff.md and moves its status so a fresh session or another role can continue. Use before stopping work, when switching roles, or whenever a work item changes state.
How it works
SKILL.md has no level-two headings · 22 lines, 204 words
SKILL.md preview
--- name: write-handoff description: Updates a work item's handoff.md and moves its status so a fresh session or another role can continue. Use before stopping work, when switching roles, or whenever a work item changes state. --- # Write a handoff **Role:** any role holding the item. `handoff.md` is the one item file every role edits. The next session has no memory. Make `handoff.md` the only thing it needs. 1. Open `work/items/<id>/handoff.md` (or the single-file item). 2. Update the body, keeping it under about 60 lines: - **Current state**: one paragraph on where things stand right now. - **Decisions made**: choices that must not be re-litigated, with a pointer to the ADR if there is one. - **Dead ends already tried**: so nobody repeats them. 3. Set the `do_not` list in the front matter for anything the next role must avoid. 4. Move the status with the tool; do not edit `status` by hand: ``` python3 tools/transition.py <id> <status> --by <role> --next "<one sentence for the next role>" [--owner <role>] [--evidence "<command or link>"] ``` `in-review`, `verified` and `done` need `--evidence`. `blocked` needs `--next` saying what unblocks it. To change only the next step, owner or evidence, leave the status out: `python3 tools/transition.py <id> --next "..."`. 5. Run `python3 tools/check.py`. It must pass before you stop. Evidence is what you ran or a link, not "tests pass". If the tool refuses a move, read its message: it names the missing rule.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · The-Urcydo/Repo-Template | 96 | MIT |
| kailot-harris/claude-handoff-skills | 100 | MIT |
| anurag-rivora/product-brain-starter | 90 | MIT |
Database snapshot: 13.11.2026 · package version d48f4675eeeb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90handoff
Write a handoff document so another agent or a fresh session can continue this work. Use for "handoff", "hand this off", "write a handoff", "continue this in a new session" or "pass this to another agent". For deciding whether to compact or clear, use session-budget. - 82handoff
Write a short handoff note so a fresh session can continue this work with a small context, then tell the user to start a fresh session. Use when the conversation has grown long, before switching phase (design to implementation, one task to the next), or before stopping. - 82handoff
Write a short handoff note so a fresh session can continue this work with a small context, then tell the user to start a fresh session. Use when the conversation has grown long, before switching phase (design to implementation, one task to the next), or before stopping. - 100handoff
Save the current work as a short handoff note so a fresh session can continue without the old conversation, or pick up from one. Use on /handoff, before /clear or switching accounts, at milestones of long work, when a session has grown large and the next task is unrelated, and… - 90handoff
Write a handoff document so a fresh session can pick up this work. Use when a session is about to end or go cold, before switching tasks, or when the user asks for a handoff. - 100handoff-doc
Write a hand-off document so a fresh session or another person can continue the current task without the chat history. Use when switching tasks, after several compactions, before clearing a session, or when asked to write a handoff, brief, or progress doc.