gsd-verify-work

To verify acceptance criteria and definition of done before a milestone review, load your phase requirements, enumerate each criterion, evaluate them with evidence, and output a clear readiness status such as READY or NEEDS_WORK to prevent unfinished work from advancing.

Checking code review readiness involves identifying and verifying that phase criteria are satisfied across post-phase tasks. The process evaluates each acceptance criterion with concrete evidence to ensure quality and outputs a clear status indicating whether the work is READY or NEEDS_WORK.

Phase management verification prevents unfinished work from advancing by loading phase requirements and enumerating acceptance criteria. It evaluates each criterion with evidence and outputs a clear status, ensuring only fully verified work passes milestone reviews and code reviews.

Yes, you can use quality assurance to collect evidence for the definition of done. The process evaluates each acceptance criterion explicitly, gathers verification evidence, and outputs a clear readiness status to confirm all phase criteria are satisfied before milestones.

You need to verify work quality across post-phase tasks immediately after completing a phase and before milestone reviews. This ensures all acceptance criteria and definition of done requirements are satisfied with evidence, preventing unfinished work from advancing.

Milestone reviews fail without explicit acceptance criteria verification because phase requirements are not confirmed with evidence. Verifying each criterion prevents unfinished work from advancing and outputs a clear NEEDS_WORK status when quality readiness is unmet.