story-done

Verify story completion by automatically checking file existence, running test suites, and prompting for manual confirmations against defined acceptance criteria. This ensures all requirements are met before finalizing the active sprint story.

Enforce test evidence and design compliance by cross-checking GDD requirements, ADR constraints, and manifest versions. This process ensures required unit or integration tests and evidence documents exist before marking the story done.

Code review gating optionally runs a lead-programmer review before story completion. This step acts as a final verification barrier to ensure code quality standards are met before updating the story status and session state.

Yes, verifying story completion requires access to story files, GDD/ADR documents, and test suites. These documents provide the necessary acceptance criteria and design constraints required to validate the active sprint story.

Update story status and queue the next ready task by running the sprint progression checks. This automatically finalizes the current story and surfaces the next ready story in the sprint while updating the session state.

If required test evidence is missing, story verification fails the automatic checks and prompts for manual confirmations. This prevents the story status from being updated until all required evidence documents exist.