What problem does it solve? When a project roadmap is fully shipped, teams often jump straight into the next version without capturing what worked, what drifted from the plan, and what new ideas emerged from real usage. This Skill structures that end-of-version retrospective so findings are filed consistently instead of being lost. ## Core Features & Use Cases - Roadmap completion check: Verifies every phase in docs/roadmap.md is marked done before starting, and asks how to proceed if not. - Outline drift analysis: Compares the shipped product against the original outline to surface must-haves that changed shape or were silently dropped. - Structured user interview: Asks in small batches about what works, what to change, what to add, and whether the tech stack caused real friction. - Findings filing: Routes each item to either the outline's feature list (adopted now) or docs/FUTURE.md (parked, with a concrete revisit trigger), grouped under a dated retro heading. - Use Case: After finishing v1 of your app, say "the roadmap's done, let's do a retro" and the Skill walks you through a review, updates the outline to match reality, and seeds docs/FUTURE.md for the next planning pass. ## Quick Start Tell the assistant "the roadmap is done, let's run a project retro" and it will verify completion, interview you about the shipped product, and file the results.
