Session retrospective Claude command

retrospective.md

Conduct a session retrospective to capture learnings and improve future work.

Instructions

Review the current session and identify:

1. Unexpected Failures

Go through the conversation and find moments where:

• Something failed that you didn't anticipate
• You made incorrect assumptions (wrong model IDs, API parameters, etc.)
• A fix didn't work on the first try
• You had to debug or iterate unexpectedly

2. Unfixed Issues

Identify issues we noticed but didn't address:

• Code smells or tech debt we saw but skipped
• Edge cases we discussed but didn't handle
• TODOs or follow-up work mentioned but not done
• Bugs or limitations we worked around

3. Report Back

Summarize your findings in the chat with two sections:

• Unexpected Failures: What went wrong and the root cause
• Unfixed Issues: What we left behind and why

4. Propose Actions

After reporting, use AskUserQuestion to offer two separate actions:

First question: "Should I write these issues to ISSUES.md?"

• Options: "Yes, create/update ISSUES.md" / "No, skip"

Second question (if there are learnings about coding patterns): "Should I update CLAUDE.md with learnings?"

• Options: "Yes, update CLAUDE.md" / "No, skip"

Only ask the second question if there are genuine patterns or conventions worth documenting (not one-off bugs).

Output Format

## Session Retrospective

### Unexpected Failures
1. **[Brief title]**: [What happened] → [Root cause]
2. ...

### Unfixed Issues
1. **[Brief title]**: [What we saw] → [Why we skipped it]
2. ...

Then proceed with the confirmation dialogs.