Communication
Meeting notes to action items
Turn a meeting transcript or rough notes into decisions, owned actions with dates, and open questions, and nothing else.
Add in the app
Communication · For your bots
Handoff note
Write down the state of a piece of work so another bot or person can pick it up cold: goal, done, in progress, decisions and why, next step, and traps.
In Lobstack: Skills › Library › Add
Download LobstackWhen to use it
Work is moving to another bot, a teammate or a later session, or a thread has grown so long that where things stand needs writing down before it is lost.
What your bot will do
- 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 bot, ask before handing it over.
A good note fits on one page. If it runs longer, the goal is probably two goals.
The file
---name: handoff-notedescription: "Write down the state of a piece of work so another bot 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 bot, 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 bot, ask before handing it over. A good note fits on one page. If it runs longer, the goal is probably two goals.