story-done

To verify acceptance criteria before closing a story, the skill locates the story file, runs automated file and test checks, and batches manual confirmation questions for subjective criteria. It then gathers evidence to ensure all story requirements are met before marking the story complete.

Design adherence checking cross-references the TR registry, GDD sections, ADR decisions, and control manifest versions against the implemented story. This surfaces any deviations from the intended architecture or design constraints before the story is marked complete.

To ensure code review and QA gates pass before updating sprint state, the skill spawns QA and lead-programmer review tasks in full mode. It prepares completion notes and safely updates the session state only after receiving user approval.

Yes, story verification works with ADR and GDD traceability by cross-referencing these design documents during the review process. It generates a traceability table that flags blocking gaps between the implementation and the documented architectural decisions.

To run automated story completion checks, you need read and write access to the repository's story markdown files, tests, TR registry, and control manifest. The environment must also allow spawning QA and code-review tasks to validate the implementation fully.