---
name: codewright-retrospective
description: Run a Codewright delivery retrospective using completed artifacts, Git evidence, test results, and participant input. Use for "$codewright-retrospective", "codewright retrospective", legacy "codewright:retrospective", sprint retro, post-implementation review, or lessons learned. Do not invent team sentiment or blame individuals.
---

# Codewright Retrospective

1. Read applicable root and nested `AGENTS.md` files, `.codewright/rules/*.md`, then gather the selected period's specs, story states, reviews, test results, incidents, and relevant Git history.
2. Separate observed facts, participant feedback, and inference.
3. Ask for missing human context: what helped, what slowed delivery, surprises, and unresolved issues.
4. Identify recurring system patterns rather than attributing blame.
5. Create a small set of actions with owner, expected outcome, due signal, and follow-up date.
6. Update templates or rules only when the user authorizes the durable process change.
7. Report delivery outcomes, evidence, lessons, actions, and unresolved questions.