story-done

Automated story validation reads the story file and cross-checks each acceptance criterion against GDD and ADR references. It outputs a completion status, logs architectural deviations, and recommends the next ready story.

GDD and ADR alignment checks ensure implemented features match the Game Design Document and Architecture Decision Records. The process validates story acceptance criteria against these reference documents to detect design or architectural deviations during the closure phase.

Automating release notes from completed stories uses a completion notes summary generated during the acceptance review. The workflow validates story completion, records GDD/ADR deviations, and outputs a structured summary for downstream release reporting.

Story validation supports manual QA review workflows by offering configurable verification paths. Users can select automated validation, manual human verification, or test evidence traceability to close the story loop according to their specific process.

Finding the next ready story after closure is handled by loading manifest metadata during the completion check. The workflow outputs a completed status for the current story and automatically recommends the next target story to accelerate team progress.

Automated acceptance criteria validation should be bypassed when a story lacks defined criteria or GDD/ADR reference documents. Teams should rely on manual verification paths when test evidence traceability is required but unavailable in the current workflow.