Retro

A retrospective proposes prioritized remedies. Implement only the remedies the user approves, either in the request that started the retro or by replying to Recommended changes.

Inspect the session

Use the current session unless the user names another. Read the relevant transcript, tool results, and existing decision logs, and point to specific events. State what evidence is missing or incomplete, and draw conclusions only from the parts of the session you could inspect.

For each observed difficulty, inspect the relevant repository configuration before proposing a remedy. Existing check commands, CI, hooks, standards, and docs/agents/workflow.md may already address it but be disconnected, unclear, or broken.

For code changes, also check whether required feedback-loop commands run through CI or local hooks. Report missing or broken enforcement where those checks should protect the changed work. A documented command alone does not establish that it runs.

Done when every observed difficulty has an evidence pointer and the repository configuration bearing on it has been inspected.

Choose improvements

Consider these remedies where the evidence supports them: