What problem does it solve? After a frustrating or inefficient re-frame2-pair session, users lack a structured way to identify what went wrong, why the pair tool fell short, and which concrete improvement would matter most. This Skill turns a completed or recapped pair session into a one-response product retrospective with evidence-grounded findings and an optional copy-pasteable GitHub issue draft. ## Core Features & Use Cases - Session friction analysis: Reconstructs causal order from a transcript or recap, distinguishing retries, stale results, workarounds, and hidden prerequisites, and assigns each finding to the correct owner (pair tool vs upstream re-frame2 framework). - Read-only issue drafting: Produces one focused, copy-pasteable GitHub issue draft against day8/re-frame2 with tool-vs-framework ownership in the title and body, plus optional duplicate search via gh issue list/view. - Known-friction pattern matching: Consults references/known-frictions.md to tell recurring product gaps from one-off problems. - Use Case: After a session where restore-epoch kept failing with :rf.epoch/restore-version-mismatch, ask for a retro and receive the friction diagnosis, the smallest credible fix, and a ready-to-file issue draft in one response. ## Quick Start Ask the assistant to retro on your just-finished re-frame2-pair session and draft a GitHub issue for the biggest friction it finds.
