boss-briefing

# boss-briefing Vault health check skill. Analyzes workflow patterns, syncs profile, recovers from session gaps, and proposes persona rules based on temporal agent call sequences. > **Relationship with other skills:** > - `briefing-vault` handles vault templates and initialization > - `boss-briefing` handles sync, analysis, and pattern detection > - `stop-profile-update.js` still runs as a fallback if this skill was not invoked during the session ## Steps Execute all 9 steps in order. If any step fails due to missing data, log the issue and continue to the next step. ### Step 1: Read state.json Read `.briefing/state.json` to get session metadata: - `date` — last session date - `workCounter` — file edit count this session - `sessionMessageCount` — user message count this session - `lastVaultSync` — ISO timestamp of last /boss-briefing run - `sessionStartHead` — git HEAD or `YYYY-MM-DD:cwd` identifier If state.json does not exist or is empty, use defaults: `{ date: "", workCounter: 0, sessionMessageCount: 0, lastVaultSync: "", sessionStartHead: "" }`. ### Step 2: Previous session gap detection Compare the `date` field from state.json with today's date. If the gap is >= 1 day: 1. Scan `.briefing/sessions/` for the most recent session file (by filename date prefix) 2. Report the gap: "Last session was on YYYY-MM-DD (N days ago). Topic: <extracted from filename>" 3. Read the most recent session file and provide a brief recovery summary of what was last worked on If gap ...