What problem does it solve? When a coding session ends, everything held only in context — why an approach was abandoned, which results are proven versus assumed, and what to do next — evaporates. The next session wastes an hour re-deriving state and often repeats dead ends the previous session already ruled out. ## Core Features & Use Cases - Fact routing triage: Directs each fact to its authoritative home (progress tracker, program file, diff, doctrine, or ADR) so the checkpoint only holds what nothing else records. - Structured handoff format: Writes .void/machine/checkpoint.md with sections for proven state, dead ends, labelled assumptions, open loops, and exactly one executable next action. - Freshness and quality checks: Converts time-relative references to absolute dates and commits, and self-tests whether a stranger could resume without asking questions. - Use Case: Before clearing context mid-task, invoke the skill to record that pnpm verify was green on commit a1b2c3d, that the caching approach failed because of stale invalidation, and that the next step is running a specific failing test. ## Quick Start Ask the agent to write a session checkpoint before clearing the context so the next session can resume without re-deriving anything.
