session-reflectionlisted

# Session-End Reflection Catch blind spots and under-investigated areas before concluding a session by asking two questions: 1. **Confidence audit:** What am I least confident about right now? 2. **Blind-spot check (Sam Altman):** What's the biggest thing I'm missing about this situation? What don't I realize? ~1 in 4 sessions, one of the answers reveals a critical gap that would silently invalidate work. This skill catches those gaps at the cheapest possible moment. ## Prerequisites - A session that appears to be concluding (user signals completion, asks for summary, or starts wrap-up language) - The `RULES.md` rule "Always conduct session-end reflection" should already be active (it references this skill) — the rule lives in the agents directory under the repo root - For persisting uncovered findings: the `context-file` skill, and optionally the `adr-capture` skill if a binding decision emerges - For genuine gaps that aren't being fixed in this session: the `context-file` skill's `KNOWN_ISSUE` type (`.context/known-issues/`) — this is the primary, intended source of known-issue entries; see step 6 ## Quick Start ```bash # No commands needed — this is a behavioural skill. # The rule in RULES.md triggers the reflection automatically. # Read this skill for detailed guidance on execution. ``` ## Workflow ### 1. Detect session-end signals Look for cues like: - User says "we're done", "thanks", "that's all", "wrap it up", "sign off" - User asks for a summary or next ste