boss-briefinglisted

# Boss Briefing Skill Vault sync, workflow pattern analysis, and persona rule management. Run this skill during or at the end of a session to keep `.briefing/` healthy and up to date. This skill **replaces the profile update functionality** from `stop-profile-update.js` (which remains as a fallback for sessions where `/boss-briefing` is not run). The existing `briefing-vault` skill handles vault templates and initialization; this skill handles sync, analysis, and persona learning. The my-codex runtime uses `briefing-runtime.js` for state management. State is stored in `.briefing/state.json` and can be read/written via standard filesystem operations. --- ## Step 1: Read state.json Read `.briefing/state.json` and extract session metadata: - `date` — session date (YYYY-MM-DD) - `workCounter` — number of meaningful work events - `sessionMessageCount` — total prompts in this session - `lastVaultSync` — ISO timestamp of last boss-briefing run - `sessionStartHead` — git HEAD at session start (empty for non-git projects) - `promptCount` — prompt counter - `editCount` — edit counter - `subagentCount` — subagent completion counter - `subagentSeq` — sequential subagent index for agent-log enrichment If `state.json` does not exist or is empty, report that and skip to Step 6. ## Step 2: Previous Session Gap Detection Compare the `date` field in state.json with today's date. - If the gap is >= 1 day, scan `.briefing/sessions/` for the most recent session file (by filename date p