reflectlisted

# Reflect - session truth reconciliation A deliberate pause before closeout to ask two questions about everything this session surfaced: 1. **Is any of it durable knowledge that should outlive this session?** → promote it to permanent memory. 2. **Did any of it invalidate something already written down as true?** → find that stale claim wherever it lives - memory, docs, comments, configs - and correct it so the whole record lines up. Reflect is about *truth*, not documentation. It is **not** `/notes`. `/notes` sweeps session work into the repo's living docs; reflect promotes durable facts to memory and reconciles stale claims, then *reminds* you about `/notes` rather than doing its job. **Reflect proposes; the user approves; then reflect applies.** It never writes a memory or edits a file off its own conclusions - every belief it intends to commit is surfaced to the user for validation first. The user owns what becomes permanent truth. Run when invoked as `/reflect` or when the user says "reflect" / "reconcile". A whole-session closeout ("close out the session", "wrap it up") belongs to `wrap-up`, which runs this skill as its first link. ## Step 1 - Reconstruct what's new Think back over the whole session and list, concretely, what changed in your understanding of the world - not what you *did* (that's `/notes`), but what is now **true or known** that wasn't before: - **Learned / discovered** - non-obvious facts about the code, tools, environment, or the us