← ClaudeAtlas

sessionlisted

Use for start, checkpoint, handoff, compaction, or end-of-session continuity on substantial work. Not for a multi-session route map; use work-map for effort state.
mblauberg/provenant · ★ 1 · AI & Automation · score 67
Install: claude install-skill mblauberg/provenant
# Session Read the repository's `Repository process` declaration and its declared scope/story and workflow-state owners first. If absent, use existing owners or return a chat handoff; never invent one. Write continuity only to an authorised handoff or explicit run-local state; without that authority, propose a chat delta. Updating an external tracker requires external-write authority. There is no default rolling project state file. Run state remains run-local, not project-wide truth. Project instructions may override continuity paths. Fallbacks: handoffs `docs/handoffs/`, archive `docs/archive/`. ## Start For substantial work, reopen disk state; distrust injected state. Resume using declared owners and the digest-bound handoff, reading only relevant docs/open decisions. User gates stay unanswered until decided. Bounded work may continue within authority. ## Checkpoint Before compaction or handoff, update the canonical handoff when authorised; otherwise return it without writing. Use `HANDOFF-YYYY-MM-DD-<slug>.md` with: - `Status: active`, effort/leg IDs, superseded path, `Consumed-at: pending`; - original goal, disk-backed progress paths/commits, ordered remainder; - invariants and exact verification commands. Keep one active handoff per effort/leg. Archive a consumed handoff, mark and index it; never delete it. Update `work-map` only when the durable route changes; live state belongs to the declared workflow-state owner. Before checkpoint load [context-hygiene.md](re