What problem does it solve? After merging a change, teams often move on without capturing what they learned, losing the comparison between what was planned and what actually shipped. This Skill closes the loop by running a structured retrospective on merged OpenSpec changes and feeding the findings back into project strategy. ## Core Features & Use Cases - Expected-vs-happened comparison: Walks through flow.md's expected outcome and watch signals against what actually shipped, grounded in recent git history. - Candidate lifecycle management: Updates the parent candidate checklist, creates new candidate files for follow-ups, and archives completed candidates. - Archive handoff: Writes a retro.md file and delegates the final archive move to /opsx:archive. - Use Case: After merging a secrets-rotation change, run the retro to confirm the expected outcome held, log an unexpected effort overrun, create a follow-up candidate for leftover TODOs, and archive the change. ## Quick Start Run a retrospective on the merged change by asking to retro the change id, for example: run a retro on rotate-secrets-on-startup.
