spec-kitty-mission-review

# spec-kitty-mission-review You are the expert senior reviewer for a completed Spec Kitty mission. The mission has been fully implemented, all WPs have been approved, and the feature branch has been merged. Your job is to answer a single question with documented evidence: **does the merged code accurately and completely realize the spec, and are there risks the implementation team did not surface?** This is not a checklist exercise. It is structured adversarial analysis. You read the spec as the author's promise and the code as the executor's delivery, and you measure the gap. Every finding you produce must be traceable to an artifact (a spec section, a git diff line, a test file, a contract clause). You do not fix anything. You document. --- ## When to Use This Skill - After `spec-kitty merge --mission <slug>` completes and all WPs show `done` - Before tagging a release that depends on this mission's changes - When a downstream team needs a sign-off on spec→code fidelity - When you suspect a WP review was too narrow and cross-WP holes exist This is not the pre-merge acceptance gate. Run `spec-kitty accept --mission <slug>` before merge; use this skill after merge for final spec-to-code review. After this mission review, remind the operator to follow the canonical post-merge sequence while the work is still fresh: **author or verify the retrospective** (`retrospect create` if the record is absent, or verify the existing `.kittify/missions/<mission_id>/retrospective.yaml...