crash-recovery

Rebuild context by inspecting git status and recent commits, checking issue tracker data in .beads files, and asking for missing details. Git state, issue notes, and user memory combine to recreate a resumable plan quickly.

Start by running git status and git log to see uncommitted changes and recent work, then check bd list to review in-progress issues. These artifacts preserve enough state to reconstruct your session without full history.

Yes. Context-limit recovery uses the same approach as crash recovery: inspect git diff for pending changes, review .beads issue data for design decisions and progress notes, then synthesize a coherent resumable plan.

Git shows uncommitted changes and commit history; issue tracker (.beads) stores design notes, resolution status, and lab-notebook fields. Together they provide enough technical context to identify what was being worked on and resume without guessing.

The Skill solicits user input when needed. You describe what you recall, and it synthesizes that memory with git state and issue data to fill gaps and produce a summary with identified missing context.

Yes. Recovery integrates with standard git commands and issue tracker formats (.beads). No workflow changes required; it reconstructs context from artifacts you already maintain.