WTF Reflect

Capture learnings from this session. Route them into the right steering document. Every hard-won insight belongs in a steering doc so it guides future work. This includes where the AI went wrong and where implementation was harder than expected.

This skill is the producer for the ## Hard-Won Lessons section of the four steering docs. See ../references/steering-doc-process.md for the producer/consumer model and how other skills load these docs.

Intervention tracker: The hooks/track-interventions.py hook runs on every UserPromptSubmit event. It increments a per-user counter file in $WTF_STATE_DIR when it detects correction or frustration language (e.g. "no,", "wrong", "actually", "stop that"). Default path: $XDG_STATE_HOME/wtf/interventions-<user>. Else use ~/.local/state/wtf/ or $TMPDIR/wtf/. When the counter reaches 3, the hook prints a reminder at the end of the session to run wtf.reflect. Step 6 of this skill resets the counter to zero. No manual tracking is needed. The hook handles it.

Process

1. Check which steering docs exist

ls docs/steering/ 2>/dev/null

Build a map of which of the four docs are present: TECH.md, QA.md, DESIGN.md, VISION.md.