story-done

Automating story closure verification requires checking acceptance criteria, DoD alignment, and ADR/GDD references. This process orchestrates phase-driven checks, gathers test evidence, records deviations, and updates the story file and sprint status upon approval.

End-to-end QA validation for sprint stories is an automated process that verifies completion by checking acceptance criteria, GDD/ADR alignment, and code-review gates. It generates a completion report with test evidence and surfaces the next ready story to maintain workflow momentum.

Checking ADR and GDD references during sprint closure is handled by phase-driven verification that aligns story completion with design documents. The process validates references, activates review gates for QA leads and lead programmers, and records any deviations found.

Triggering QA lead and lead programmer review gates automatically is supported during story verification. The process activates these gates as part of phase-driven checks, ensuring code-review compliance before updating the story file and sprint status when approved.

Automated story completion works by gathering test evidence automatically during phase-driven checks. It validates acceptance criteria and DoD alignment, records deviations, and generates a completion report, reducing manual QA overhead while ensuring sprint plan alignment.

Surfacing the next ready story after sprint closure is best handled by end-to-end QA verification that updates story status upon approval. The process maintains workflow momentum by automatically identifying the next actionable story after validating completion criteria.