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: before the user has walked away.

Prerequisites

• A session that appears to be concluding (user signals completion, asks for summary, or starts wrap-up language)
• A project-level behavioural rule for "always conduct session-end reflection" should already be active, if this project has one -- check the project's own rules file
• For persisting uncovered findings: the context-file skill, and optionally adr-capture if a binding decision emerges
• For genuine gaps that aren't being fixed in this session: the context-file skill's known-issue document type -- this is the primary, intended source of those entries; see Workflow step 6