What problem does it solve? Closing a GitHub issue often loses the context of what shipped, how it was implemented, and whether it actually worked. This Skill enforces a consistent close-time retrospective record on every completed issue and supports later outcome validation, so the issue tracker remains a durable source of project history. ## Core Features & Use Cases - Close+Retro Operation: Closes an issue and posts a structured ## Retrospective comment (Resolved by, What shipped, How, Tests, Follow-ups) in one transaction, with carve-outs for duplicate/wontfix/not-planned/invalid closes. - Outcome Validation: Posts a dated ## Outcome validation comment on already-closed issues, recording whether the change achieved its intent (achieved / partial / not-achieved / deferred) with a signal source and rationale. - Epic Close Detection: After closing a sub-issue, checks the parent epic via the GitHub sub-issues API and prompts an epic retrospective when the last open sub-issue closes. - Auto-Filed Remediation: For partial or not-achieved outcomes, files a deduplicated tech-debt follow-up issue with priority labels via the backlog skill's auto-file contract. - Use Case: When a PR with Closes #42 is about to merge, run close+retro to document the shipped change on issue #42; months later, run validate to confirm the fix actually resolved the reported behavior. ## Quick Start Close issue #42 with a retrospective comment documenting what shipped, how it was implemented, and which tests cover it.
