What problem does it solve? Founders who did not watch a spec's implementation cannot tell what the product now does differently, which changed numbers are intentional, or what to test by hand. This Skill turns a finished or in-flight spec into a tech-lead briefing that transfers exactly that knowledge. ## Core Features & Use Cases - State-based reconstruction: Reads the issue body, merged PRs, report comments, and ADRs instead of reconstructing the story from the comment event log. - PR triage into three bins: Classifies merged work as result-changing, new surface, or result-preserving so testing effort goes only where behavior actually changed. - Ranked manual test plan: Derives one concrete check per result change and new surface, with expected outcomes, expected blockers, and risk-ranked ordering. - Use Case: After a tax-calculation spec ships, ask for a walkthrough and receive the story, the numbers that changed on purpose with links to their recorded decisions, a checklist of manual tests against real local data, known gaps already filed, and honest confessions about untested paths. ## Quick Start Ask the agent to walk you through what spec number 42 delivered and what you should manually test.
