story-done

To verify acceptance criteria before story completion, validate each criterion against the current implementation by reading story files, running test evidence checks, and performing grep/glob validations to confirm required files and logic exist.

Traceability and coverage gating in sprint workflows builds a criterion-to-test table, ensuring test evidence sufficiently covers the story type, and escalates review when coverage is insufficient for the selected review mode.

Detect design drift and ADR deviations during code review by checking GDD and manifest staleness against implementation constraints, explicitly recording any architectural deviations instead of letting them go unnoticed before completion.

Yes, story completion verification works in solo and lean sprint modes by running automated evidence checks and scripted validations, bypassing the QA and lead programmer code review gates required in standard team workflows.

After a story passes spec verification and updates to complete status, the workflow surfaces the next ready story from the backlog, allowing immediate transition to subsequent sprint tasks without manual backlog triage.

Story completion fails when hardcoded values or strings bypass acceptance criteria because the verification process checks for required files, dependencies, and test pass evidence, catching hardcoded implementations that violate spec constraints.