What problem does it solve? Sessions end without a consistent record: close-outs come in five different shapes, handovers go stale within hours, and the next session starts from memory instead of facts. This Skill closes every session with one After Action Report (AAR) posted on the dispatch ticket, so pickup always reads exactly one current record. ## Core Features & Use Cases - Standardized AAR template: Captures intended vs. actual work, the gap and its systemic cause, what to sustain, improvements with owners, watch-outs, and a trail of links — signed by seat and dispatch id, never a model name. - Vault supersede sweep: When the vault is mounted, saves the report as aar-YYYY-MM-DD-[thread].md and flips the thread's previous ACTIVE report to superseded, keeping one live record per thread. - Pickup protocol: Before resuming work, reads the latest AAR first, verifies ticket ids, statuses, paths and SHAs, and repairs drift when two ACTIVE reports exist. - Use Case: At the end of a coding session dispatched at LIAB-1162, run /wrap-up to post a structured AAR comment on the ticket, save the vault copy, and give the next session a verified starting point. ## Quick Start Say "wrap up" or run /wrap-up at the end of your session to generate and post the After Action Report on the dispatch ticket.
