# Booth Compact Recovery

> Booth daemon compaction recovery signal. Restores session context after CC context compaction. Tells DJ/deck their role and points to recovery files. Activates when daemon injects /booth-compact-recovery after compaction.

- Skill: `motiful/booth-compact-recovery` (Agent Skill)
- Install (CLI): `npx skillmds@latest add motiful/booth-compact-recovery`
- Raw SKILL.md: https://api.skillmd.com/api/skills/motiful/booth-compact-recovery/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: motiful (https://skillmd.com/u/motiful)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/motiful/booth-compact-recovery

---


# /booth-compact-recovery — Context Recovery Signal

Injected by the Booth daemon when CC compaction is detected. Restore identity, recover context, then **wait for user confirmation before reading other files**.

## Why this skill exists

Without explicit guidance, fresh post-compact sessions read every progress file, build conflicting pictures, and dump stale summaries asking user to pick. This skill enforces a **narrow, single-source recovery loop**: read raw JSONL for context, read NOW for direction, state intent, wait.

## What To Do

1. **Read the last ~5 real user-assistant exchanges from your session JSONL** at the path in the signal. Skip entries where the message is only `tool_use` or `tool_result` blocks (they have no human-readable text). The JSONL is the authoritative source of pre-compact context — read it directly, no predigest involved.

2. **Identity-specific recovery**:
   - **DJ**: read `progress/README.md` 🎯 NOW segment — that single segment is authoritative for "what's next". Do **not** read multiple progress files.
   - **Deck**: run `booth status <name>` to see your original goal. Optionally `git log` / `git diff` for your recent work.

3. **State next action in one sentence**. Wait for user confirmation before reading anything else.

4. **Do NOT re-execute completed work** — the compaction summary + JSONL + NOW segment together tell you where you left off.

## Anti-patterns (don't do)

- Reading `progress/README.md` cover-to-cover (ignore archive references; only NOW matters)
- Reading multiple progress files to "build a fuller picture" — they conflict by design (history vs current)
- Running `booth ls` + `booth reports` + `git log` all at once before stating intent — that's noise, not context
- Reporting "I've reviewed everything, here are 5 options to proceed" — pick the one NOW says, ask user to confirm