1listed

Recover a session after a hard crash (app died, machine rebooted, context lost mid-work): replay the turn-state ledger for the last requests, files and decisions, run a green/red health ping over the system map, file sync and MCP connectors, then rebuild the previous session history for pickup. Triggers: "/1", "resume after crash", "wake".
tonydzi/second-brain-starter-kit · ★ 6 · AI & Automation · score 78

Install: claude install-skill tonydzi/second-brain-starter-kit

# /1 — resurrection after a crash ("where were we + is everything working") **The operator's pain:** the session died mid-work (a crash / the computer went off) → the new session is empty. Before: remember by hand, then separately fire `/arch`, `/sync-check`, `/mcp`, then work out "where did we stop". Now it is one word: `/1` (or `/!`). **What this is NOT:** `/retro` is for a CLEAN end of session (inventory of what was built → routing to homes → /compact). After a sudden crash there is nothing left to package, the context is already gone → you need resurrection, NOT `/retro`. Two different tools. ## 3 steps (run them in order, report as one panel) ### Step 1 — RECALL: where we were (0 tokens, deterministic) The TurnState black box writes EVERY turn into SQLite (a Stop hook), and it survives any crash. Read the last turns: ```bash python "$IMPORTS_ROOT/turnstate/turnstate_show.py" --n 12 ``` From the output pull out: what the operator asked for last · which files were touched · which DECISIONS were made · the next step. That is "where we were cut off". (Flags: `--stats`, `--session <id>`, `--n N`.) **⚠️ Fallback if the box is EMPTY** (`turnstate_show.py --stats` shows `turns: 0` — it happens when the Stop hook hasn't fired yet after a Claude Code restart; see [[crash-recovery-command]]): do NOT say "there is no data". Derive "where we were" from the LAST session — its full seed is already assembled in step 3 (`_Dashboards/sessions-md/_continue/<cli>.seed.md`): read the TA