verify-requirements-complete

Requirement validation checks that architect, tester, and formatter reports exist with non-empty content, proper markdown structure, and required sections. Run verify-requirements-complete to gate progression to synthesis and catch missing or malformed reports before downstream processing begins.

Validation confirms three report files exist, contain actual analysis with required sections, use valid markdown formatting, and verifies agent completion status via status.json. This ensures data quality and consistency across all stakeholder inputs before synthesis proceeds.

Yes, verification applies during the requirements phase across architect, tester, and formatter agents. It works when all agents report completion, ensuring synchronized handoff and preventing synthesis from starting with incomplete or missing stakeholder analysis.

If reports are missing, empty, lack required sections, contain malformed markdown, or agent statuses show incomplete, validation gates progression and alerts you to fix the reports before synthesis can proceed, preventing downstream errors.

No. Requirement validation automates these checks—verifying file presence, content structure, formatting, and agent statuses—eliminating manual inspection and catching issues early in the requirements phase.