baton-tasklisted
Install: claude install-skill StanimirTenev/baton
# Baton task — form it before you research it
Research answers a question. If the question was never stated, the research answers the
one the agent assumed, and the logbook records work on a task nobody defined. This skill
is the step before: four moves, in order, each one there because skipping it cost something.
Output in the human's language. The field names stay as they are.
---
## 1. Recognise — has this become a task?
A conversation turns into a task or a decision without announcing it. The signals:
a choice between options ("let's go with the first"), a priority ("give priority to 1 and 2"),
money or a deadline, "let's do it", "plan it", or a new name for a body of work.
When you see one, say so in one line and ask whether to record it — **do not record it on
your own, and do not plan it yet** unless asked.
> Paid for on 2026-09-28: a conversation opened with "we are only thinking aloud" and ended
> in a decision on which work comes first. Nobody said "this is a decision" until the agent
> did, three messages late.
## 2. Read back — what was already done and decided?
Before proposing anything:
- Is there a task folder? `ls -t` the task root; the UserPromptSubmit hook names folders a
message touches, but it matches words, not meaning — look yourself too.
- Read the logbook **on this topic**, not the top entry. Search it for the subject.
- Read the memory entries that point at it, and any open plan (`PLAN*.md`).
- Collect: decisions already taken, claims alrea