story-done

Validating acceptance criteria before updating story status to complete involves verifying every criterion against the implementation and ensuring any GDD or ADR deviations are explicitly documented rather than silently introduced. This creates a traceable completion record.

End-of-story completion review is the process of closing stories properly by validating acceptance criteria, documenting deviations, prompting code review, and updating the story file status to Complete while surfacing the next ready story to maintain sprint momentum.

Documenting GDD and ADR deviations during story completion requires gathering implementation details and making any deviations from acceptance criteria explicit in the completion record, producing a completion note ready for inclusion in the sprint log.

Yes, surfacing the next ready story automatically after marking a story as complete is supported. The workflow locates the active story, gathers implementation details, updates the status to Complete, and then surfaces the next ready story to keep team momentum going.

The best way to prompt for code review during story completion is to integrate it into the end-of-story workflow, prompting for review where needed while simultaneously validating acceptance criteria and updating the story file status to reflect actual completion.

Your story completion process lacks traceability if deviations are silently introduced without documenting GDD or ADR changes. Automating the completion workflow produces a complete, traceable completion record and a completion note ready for inclusion in the sprint log.