Retrospective

Overview

Run after a session. Reflect honestly on what worked and what didn't, then feed process-level learnings back into the skills used so next session is better.

Core principle: A retrospective is worthless without a concrete change. Every useful finding produces either a skill-file edit or an explicit follow-up note/update. Anything else is venting.

When to Use

Triggers:

• "How well did [the skill / that / it] work?" / "How did that go?"
• "What could we improve?" / "retro" / "what did we learn"
• End of a feature/task, after commit, before moving on

Not for mid-task check-ins or routine status reports.

The Process