Coding Session Retrospective

Inspect a real coding session and propose improvements to the agent's environment, not the product code. The goal is to make the next run easier to navigate and harder to get wrong.

This is human-in-the-loop. Present findings first; do not edit steering files, standards, hooks, CI, or skills until the user chooses which findings to apply.

When to Use

Use when:

• A coding session was unusually long, confusing, or error-prone.
• The user asks to review recent agent sessions.
• A bug or repeated mistake suggests a missing guardrail.

The default target is the current session. If the user names a count or date range, inspect that exact range. If session history is unavailable, say so and review the repository evidence only.

Sources

Read the real sources before judging: