reflect

# Reflect — step back and audit the work, not just the code <!-- routing-eval reads this line; it lives in the BODY so the always-on skill LISTING stays inside Claude Code's budget (1% of the context window) — an overflowing listing gets descriptions truncated or dropped, which strips the very keywords a match depends on. --> Trigger phrases: "reflect", "retro", "retrospective", "what did we miss", "step back", "introspect" ## When A nontrivial chunk of work just finished (a feature, a plan, a debugging session) and it's worth a deliberate step back **before** committing or moving on. This is the meta-cognitive counterpart to [[iterate]]: iterate drives a change *to* its exit test; reflect asks whether the exit test — and the approach behind it — was even the right one. Skip it for a one-line, unambiguous change; there's nothing to reflect on. ## Measure first, then remember Run **`bash .claude/hooks/session-stats.sh`** before answering anything below, and open the pass with what it reports. A retro built only on recall is an interview with the least reliable witness in the room: the model reconstructs a tidy story from a context that has already been summarised, and the stretches where it span on a failing approach are exactly the ones it remembers least. The script counts what actually happened — prompts, tool calls, failing loops, near-duplicate prompts, interrupts, auto-compactions. Treat each ⚠️ as a **question to answer in the pass**, not a verdict: a runa...