handofflisted

# Handoff - Resume Intake An opener like `resume work`, `take over from the handoff`, or `follow up` is not a description of a task. It is a pointer to state you do not have. Load that state and check it before acting - never guess the task from the opener alone. **Output:** a short spoken summary - where things stand, what is stale, what to do next. No file, no edit. **Default command:** `$handoff` **Source edits:** none --- ## The rule that makes this skill worth running **A handoff note is a claim, not a fact.** It was written before the last things happened. Notes routinely say work is blocked when it landed, name a branch that merged, or point at a file that moved. Verify every checkable claim against the repo before you repeat it. Repeating a stale note as current state is the failure this skill exists to prevent. --- ## Phase 1: Find the state Work outward. Stop at the first layer that answers the question, but always do Phase 2 on whatever you find. 1. **An explicit path.** If the user named a file, read that first. 2. **The memory store.** The remember-style layout is `<store>/projects/<project-slug>/` holding `now.md` (live buffer), `today-*.md` (daily), `recent.md` (7 days), `archive*.md` (older). Read newest first. Older archives are usually not preloaded - grep them only when a question reaches past what you already have. 3. **Handoff files in the repo.** `HANDOFF.md`, `docs/handoffs/`, `docs/plans/`, `*handoff*.md`, `*-state.md`. 4. **Th