Reflection

Capture what was learned and identify a single skill to practice deliberately next time.

Philosophy

Experience density is not just about writing more code. It is about extracting learning from each piece of code written.

Without reflection, the same mistakes repeat. With it, each PR builds toward a specific, named skill. The developer begins to see their own growth.

This is also where patterns in feedback become visible. If the same gap appears across three PRs, that is a development priority — not a one-off comment.

Questions

Ask these in order, one at a time. Let the developer answer in their own words before asking the next question. Never paste the full list into the conversation. Do not produce the reflection summary until the sequence is complete.

Start with: