story-done

Documenting GDD and ADR deviations during story completion involves surfacing and explicitly recording any misalignment between the implementation and the current architecture rules. The skill surfaces these deviations rather than hiding them, ensuring design and implementation stay synchronized.

Prompting a code review when a story is done is triggered automatically when implementation exists. The skill detects completed implementation within the agile workflow and prompts a lead programmer review as part of the end-to-end completion gate process.

Surfacing the next ready sprint item after story completion is handled by updating the sprint state and automatically identifying the next ready story. The skill completes the current workflow and immediately presents the next actionable item for the sprint.

Architecture references are required to verify agile story completion and check alignment with current rules. The skill needs both the story file and architecture references to validate the story against GDD and ADR standards and surface a completion-ready report.

Automated QA gates across design and development for sprint stories are supported through the end-to-end completion gate. The skill applies verification across design, development, and QA gates to ensure every acceptance criterion is met before the story is marked complete.