Handoff note
Write down the state of a piece of work so another agent or person can pick it up cold: goal, done, in progress, decisions and why, next step, and traps.
In Lobstack: Skills › Library › Add
What your agent will do.
Work is moving to another agent, a teammate or a later session, or a thread has grown so long that where things stand needs writing down before it is lost.
- 01
Write for someone who has read nothing. Link the repository, document, ticket or thread; never "the file we discussed".
- 02
Use these sections:
- Goal: what finished looks like, in one or two sentences.
- Done: what is complete, and how it was checked.
- In progress: what is half-done, and exactly where it stopped.
- Decisions: each choice made and why, so nobody reopens it by accident.
- Next step: the one next action, specific enough to start at once.
- Traps: what was tried and failed, and anything that looks wrong but is right.
- 03
Check each claim before writing it. "Tests pass" needs a run you watched, not one you remember.
- 04
Name anything still waiting on a person, and who.
- 05
Cut the story of how you got here. Keep only what changes what the next person does.
- 06
Post it as a document. When the work is going to another agent, ask before handing it over.
A good note fits on one page. If it runs longer, the goal is probably two goals.
The whole SKILL.md: 35 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: handoff-notedescription: "Write down the state of a piece of work so another agent or person can pick it up cold: goal, done, in progress, decisions and why, next step, and traps."metadata: title: "Handoff note" category: communication tags: [handoff, context]--- ## When to use this Work is moving to another agent, a teammate or a later session, or a thread hasgrown so long that where things stand needs writing down before it is lost. ## How 1. Write for someone who has read nothing. Link the repository, document, ticket or thread; never "the file we discussed".2. Use these sections: - Goal: what finished looks like, in one or two sentences. - Done: what is complete, and how it was checked. - In progress: what is half-done, and exactly where it stopped. - Decisions: each choice made and why, so nobody reopens it by accident. - Next step: the one next action, specific enough to start at once. - Traps: what was tried and failed, and anything that looks wrong but is right.3. Check each claim before writing it. "Tests pass" needs a run you watched, not one you remember.4. Name anything still waiting on a person, and who.5. Cut the story of how you got here. Keep only what changes what the next person does.6. Post it as a document. When the work is going to another agent, ask before handing it over. A good note fits on one page. If it runs longer, the goal is probably two goals.
- Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Writing
Release notes from merged work
Turn merged work, or a thread about it, into release notes written for the person installing the version rather than the person who built it.
SKILL.md · App - OperationsFeatured
Weekly status report
Write the weekly update from what actually happened (merged work, moved tickets, tracked figures) in the same shape as last week.
SKILL.md · App - Personal
Meeting notes to action items
Turn a meeting transcript or rough notes into decisions, owned actions with dates, and open questions, and nothing else.
SKILL.md · App