What problem does it solve? After finishing a task or issue, teams often move on without understanding what went wrong, what wasted effort, or why failures repeated. This Skill structures a retrospective over the chat history, issue cycle, and workflow so root causes surface and durable fixes get routed into skills, docs, or scripts instead of being forgotten. ## Core Features & Use Cases - Root Cause Analysis: Goes beyond surface symptoms to identify underlying causes in prompts, skills, tools, or workflow sequencing. - Issue-Cycle Review: Closes the plan → build → verify → retro workflow by reviewing the issue, PR, verify findings, and non-blocking gaps. - Durable Fix Routing: Converts learnings into concrete changes to SKILL.md files, repo runbooks, or scripts — never memory. - Use Case: After a PR merges, run the retro to review verify's non-blocking findings, post any missing artifacts to the issue, and commit a test-debt row or doc fix as the retro follow-up. ## Quick Start Ask the assistant to run a retro on the issue that just closed, reviewing the plan, build, and verify stages for mistakes and improvements.