recalllisted
Install: claude install-skill sheldor26/Blastdoor
# Recall before you plan
The logbook is deliberately *not* loaded into context automatically. Reading
`MISTAKES.md` in full costs thousands of tokens for history that is irrelevant
to the task at hand. Retrieve by tag instead.
## When to do this
**Before writing the plan**, not before the first edit. This is the part people
get wrong, including the first version of this skill.
A plan built without the history bakes the repeat mistake into the plan itself,
and then implementation carries it out faithfully. By the time the first edit
comes around, recalling the entry means either discarding the plan or quietly
routing around the guardrail — and routing around it is what actually happens.
Two minutes earlier, the same entry changes the design for free.
So: in plan mode, `recall` is the first move, before the plan is drafted. Then
again before the first edit in any area not touched this session. Always for
auth, payments, migrations, data writes, scrapers, deploy config, and anything
that touches money or user data.
## How
```bash
node .bitacora/cli.mjs recall <tag> # by area: recall pricing
node .bitacora/cli.mjs recall <path> # by file: recall scripts/import.ts
node .bitacora/cli.mjs recall <phrase> # full text: recall "race condition"
node .bitacora/cli.mjs stats # where friction concentrates
```
`recall` prints ids, titles and tags — a cheap index. Then open the file and
read the full text of the two or three entries