reflectlisted

# Tandem: reflect (self-improvement) Use at the end of a substantive session (>30 min of real work) to capture lessons that should bleed back into the kit's rules. The blog's "self-improvement loop" pattern. ## What to scan in this session 1. **Decisions made** — did you create an ADR? Did you make a decision that *should* have become an ADR but didn't? (the rule says "any non-obvious decision" — be honest.) 2. **Friction encountered** — did you have to explain the same convention to Claude twice? That's a `PROJECT-CONTEXT.md` candidate. 3. **Workarounds applied** — did you bypass a rule or use a one-off command? Why? Should the rule change, or should there be a new entry in PROJECT-CONTEXT.md's "Known stack gotchas"? 4. **Skills that didn't fire** — did Claude paste a prompt's content instead of loading a skill? The skill's `description:` may not match the trigger phrase the user actually used. 5. **Tools used that surprised you** — was an agent invoked when a direct Read would have been faster? Was main-thread context bloated by grep results? Subagent policy adjustment needed? 6. **Patterns that recurred** — did you tell Claude to do something three times that could be a hook? ## What to output A proposal — **not** a commit. The user decides what lands. ``` 🪞 Session reflection — <ISO date> What worked: - <specific thing, ≤2 lines> What hurt: - <specific thing, ≤2 lines> Proposed kit changes (review before applying): 1. [PROJECT-CONTEXT.md] Add to "Known sta