story-done

# Story Done This skill closes the loop between design and implementation. Run it at the end of implementing any story. It ensures every acceptance criterion is verified before the story is marked done, GDD and ADR deviations are explicitly documented rather than silently introduced, code review is prompted rather than forgotten, and the story file reflects actual completion status. **Output:** Updated story file (Status: Complete) + surfaced next story. --- ## Phase 1: Find the Story Resolve the review mode (once, store for all gate spawns this run): 1. If `--review [full|lean|solo]` was passed → use that 2. Else read `production/review-mode.txt` → use that value 3. Else → default to `lean` See `.claude/docs/director-gates.md` for the full check pattern. **If a file path is provided** (e.g., `/story-done production/epics/core/story-damage-calculator.md`): read that file directly. **If no argument is provided:** 1. Check `production/session-state/active.md` for the currently active story. 2. If not found there, read the most recent file in `production/sprints/` and look for stories marked IN PROGRESS. 3. If multiple in-progress stories are found, use `AskUserQuestion`: - "Which story are we completing?" - Options: list the in-progress story file names. 4. If no story can be found, ask the user to provide the path. --- ## Phase 2: Read the Story Read the full story file. Extract and hold in context: - **Story name and ID** - **GDD Requirement TR-ID(s)** r...