briefinglisted

# Briefing Produce a concise orientation briefing for session start or context recovery. Aggregate signals from multiple sources into a single scannable summary so the user can quickly re-orient. Read-only. Reads issue-tracker state and git history; never writes, never modifies state. ## Relationship to native `/recap` Native [Claude Code `/recap`](https://code.claude.com/docs/en/changelog) (v2.1.108+) provides a recap of prior session activity when returning after a 75+ minute absence, or on demand. `briefing` **complements** `/recap` rather than replacing it: - `/recap` is auto-triggered after idle and operates on Claude Code session history. - `briefing` is invoked explicitly and aggregates *cross-tool* signals: issue tracker, git, working-memory presence, staging directory staleness. Use `/recap` when you want the narrative of the last session. Use `briefing` when you want a structured snapshot of where the project stands across tools. ## Data sources `briefing` reads from sources the user's project has configured. **Detect available sources from project signals; ask the user when ambiguous.** | Signal | Source detection | What to read | |--------|-----------------|--------------| | Issue tracker | `.beads/` directory → Beads. `.linear/` or environment → Linear. `gh` CLI authenticated → GitHub Issues. Explicit declaration in `CLAUDE.md` → use that. None of the above → **ask the user.** | Ready / available work, in-progress items, blocked items, project counts | |