story-done

To verify acceptance criteria for story completion, cross-check each criterion against required test evidence, registries, and manifests. The process enforces traceability and runs full QA and code-review gates before updating the story status to Complete.

ADR deviation checking detects mismatches between implementation reality and architectural design records. It identifies GDD/registry mismatches, manifest staleness, numeric hardcoding, and out-of-scope file touches to prevent drift from original architecture intent during story closure.

Enforce test evidence requirements by building a criterion-to-test traceability table that applies blocking gates for missing Logic unit tests and advisory checks for missing UI/Visual evidence. This ensures deterministic verification before a story is marked complete.

Story closure verification performs automated file, test, string, and dependency checks automatically, but requires optional manual confirmation for subjective or hard-to-automate acceptance criteria. Full mode also requires passing QA and code-review gates.

When GDD and registry mismatches are detected during story completion, the process reports deviations explicitly, prompts for code review, and surfaces the next ready story. The story status is not updated to Complete until all blocking issues are resolved.

The best way to close the loop on an implementation story is to run an end-of-implementation closure workflow that cross-checks acceptance criteria, validates test evidence, and detects ADR deviations. This deterministic verification updates story status and reveals the next sprint work.