What problem does it solve? After finishing backend work on a ticket, there is no durable record of what was implemented and why — the knowledge lives only in the diff and the developer's memory. This Skill produces .ai/<TICKET>/backend-summary.md, a current-state feature document grounded in the real code, and later re-verifies that the document still matches the code after changes. ## Core Features & Use Cases - Summary generation: Reads the ticket branch diff against the base branch, recovers the why from prd.md, decisions.md, and investigation.md, interviews the developer for gaps, and writes a fixed-template summary covering behavior, data model, backend map, decisions, and pending work. - Drift-check mode: On reruns, diffs from the recorded scan baseline, presents discrepancies before editing, updates only facts the code contradicts, and flips status back to Draft for re-approval. - Review gate: The document ships only on explicit developer approval, with Status tracked from Draft to Approved. - Use Case: Before opening a PR for PHG-418, ask for the backend summary; the Skill scopes the diff against dev, reads the touched handlers and migrations, and produces a document your teammates and future documentation efforts can rely on. ## Quick Start Ask the assistant to write the backend summary for the current ticket branch before creating the PR.
