brieflisted

# Session Brief Run this at the end of a session to capture context and checkpoint all work to GitHub. ## Steps ### 1. Review Existing Brief Read `/brief/session-brief.md` to understand what was there from last session. ### 2. Write the New Brief Overwrite `/brief/session-brief.md` with a comprehensive brief covering: - **Date, time (EST), and session number** at the top - Important progress made in the current session - Key decisions and architectural changes - Unfinished tasks and next steps - Technical details that need to be preserved - Any context that would be lost between sessions This is NOT about brevity — be as thorough as needed to retain all important context. ### 2.5. Reflect on Skills After writing the brief, run the `reflect` skill to scan the conversation for learnings. This is a delegation, not a repeat of the reflect instructions. Load and follow the reflect skill. - If learnings are found: present them to the user alongside the brief, before asking about git - If no learnings: report "no new skill learnings detected" in one line and continue to Step 3 - Any approved skill updates will be committed together with the brief in Step 4 ### 3. Ask About Git After writing the brief, **always ask the user** which option they want: 1. **Commit + push** — full checkpoint to GitHub 2. **Commit only** — local save point, push later 3. **Brief only** — just the file update, no git operations Present these as a quick choice. Do NOT assume commit+push. ###