reflectlisted

# Structured Reflection After completing a significant task, generate a structured reflection capturing surprises, patterns, and gotchas for future sessions. Inspired by Addy Osmani's REFLECTION.md pattern — turning tacit knowledge into durable project memory. **Trigger:** When user types `/reflect` or `/reflect <topic>` ## Arguments - `$ARGUMENTS` — optional topic string (e.g., `opencl-fix`, `eval-batch-failures`). If omitted, the topic is derived from the most recent git diff or conversation context. ## Prerequisites - Work must be done in the current session (git diff or recent commits to reflect on) - Project root: `{{PROJECT_ROOT}}` ## Workflow ### Phase 1: Gather Context Read the current session's work to understand what was done: ```bash cd {{PROJECT_ROOT}} # What changed in this session? echo "=== UNCOMMITTED CHANGES ===" git diff --stat HEAD echo "=== RECENT COMMITS (last 5) ===" git log --oneline -5 echo "=== FILES CHANGED ===" git diff --name-only HEAD ``` If there are uncommitted changes, use `git diff HEAD` to understand the substance. If changes are already committed, use `git diff HEAD~3..HEAD` to see recent work. **Also read the conversation context** — identify moments of surprise, course corrections, failed approaches, or non-obvious decisions made during the session. ### Phase 2: Derive Topic If `$ARGUMENTS` provides a topic, use it directly (slugified for the filename). If no topic is provided, derive one from: 1. The most-changed direc