Resume from binnacle
You were invoked at the start of a cold session to pick up a multi-session run. This skill adds
nothing to the resume contract — it is the deterministic entry point that saves the user from
retyping the same prompt. The procedure itself belongs to the binnacle skill; never reimplement
it here.
Steps
- Locate. Check for
.claude/binnacle.mdat the root of the current worktree. If it does not exist, stop with a clear message: this session is not inside a run's worktree. Do not search other worktrees, and do not create a binnacle — opening is task-planning's job. - Delegate. Invoke the
binnacleskill and execute every numbered step of its Resuming section in order, without summarizing, reordering, or skipping any. Do not restate those steps here — that section is their single source of truth. - Warm context, only if needed. After the binnacle skill's plan read, check the latest entry's Siguiente and Referencias: if they point at code this session must understand and neither the entry nor the plan explains it, launch read-only Explore agents in parallel — one per distinct area — and fold their conclusions into your working context. The decision comes after the plan read on purpose: the plan often documents exactly what an explorer would go find. A well-written entry needs zero explorers; the default is none, and launching them for code already explained wastes the budget the binnacle exists to protect.
- Continue. Start working the first pending task of the session in the main context, under the binnacle's Convenciones de ejecución.