What problem does it solve? After a change is merged and verified, teams often skip reflecting on how the work was done, losing lessons learned and forgetting issues that were noticed but never filed. This Skill ensures every released change produces a retrospective record and that no out-of-scope findings fall through the cracks. ## Core Features & Use Cases - Dropped-issue recovery: Searches GitHub issues by origin (source issue and PR numbers) and cross-checks against quality-gate reports, review comments, and plan files to find findings that were never filed, then files them via the out-of-scope workflow. - Fact-based reflection: Collects evidence from specs, review rounds, release verification results, and plan files across five dimensions (acceptance criteria, rework, oversights, scope, process) instead of relying on memory. - Actionable outcomes: Requires at least one concrete change classified as a Skill procedure update, a project convention update (AGENTS.md/CLAUDE.md), or a filed follow-up issue. - Structured recording: Posts a single retrospective comment to the correct issue or PR (resolved via a three-stage branch/PR lookup), and adds a traceability link line to the source issue body. - Use Case: After merging and verifying a feature PR, run the retrospective to confirm all review findings were filed, decide to add a verification step to the release Skill, and post the retrospective comment to the originating issue. ## Quick Start Run the retrospective for the change that was just released and verified, and record what to change in how the work was done.
