briefing

# Briefing Command Triggers the Chief of Staff to generate an executive summary. ## Usage ```bash /briefing [period] # Example: /briefing today # Example: /briefing week /briefing --tokens [--since 7d|24h|30m] # Reports real session token usage from Claude Code JSONL. ``` ## Protocol 1. **Collect**: Gather logs from `kb/learnings/`, `maintenance/` logs, and recent runs. 2. **Synthesize**: Group by category (Ops, Strategy, Actions). 3. **Filter**: Remove low-priority success logs. 4. **Present**: Render the Daily Brief. ## Example ``` ## Daily Brief — 2026-04-23 ### Ops - night-watch: 3 dep updates shipped, 1 rolled back (breaking change in `x-pkg@2.0`) - health: all green except `mailpit` (degraded, non-critical) ### Strategy - predict: new PR #42 overlaps with in-flight refactor in `/src/auth` ### Actions needed - Review rollback from night-watch (ETA: 5 min) - Decide on `x-pkg` pin strategy (open question on GitHub #41) ``` ## Rules - **MUST** stay under 200 words unless the user explicitly asks for more detail - **MUST** lead with decision-relevant facts, not chronology — "what should I act on" before "what happened" - **NEVER** invent agent activity — report only what the logs show; absence of logs means "no data", not "nothing happened" - **CRITICAL**: separate Ops (what ran) from Strategy (what was decided) from Actions (what needs a human) — mixing them defeats the brief - **MANDATORY**: when no material activity exists for a category, omit the category head...