spec-kitty-mission-review

To verify spec-to-code fidelity after a merge, trace functional requirements and locked decisions from spec artifacts directly to owning work packages, test suites, and exact git diffs. This post-merge audit produces structured markdown evidence highlighting any broken links in the delivery chain.

A mission-level acceptance audit is a post-merge review that confirms a fully merged implementation faithfully realizes its spec contract. It checks functional requirement coverage, identifies drift from locked decisions, evaluates test adequacy, and surfaces hidden security risks before tagging a release.

Detect code drift and security risks by mapping git diffs to owned work and checking for violations of non-goals or locked decisions. The review flags boundary-condition failures, silent empty-result candidates, dead code, and security issues around paths, subprocesses, HTTP calls, and locking.

Trace functional requirements by absorbing spec, plan, task, and contract artifacts, then mapping each promised requirement to its owning work package and relevant tests. This cross-WP coverage check assesses FR trace quality and identifies punted or uncovered approved requirements.

Yes, this review specifically identifies "passing test, failing system" patterns. By adversarially verifying the implementation against the spec contract, it finds silent error candidates and cross-WP integration gaps that basic test suites might miss.

You need the merged mission implementation and its associated spec artifacts, including the mission identity, status, spec, plan, tasks, and contracts. The audit reads these inputs to perform FR trace quality assessment and output a structured markdown report with cited evidence.