gaia-readiness-check

Automate readiness checks by validating planning, architecture, and testing artifacts against defined gates. This enforces mandatory gates like traceability matrices and CI setup to ensure completeness and prevent implementation delays.

A readiness gate validates that mandatory artifacts like traceability-matrix.md and ci-setup.md exist and are non-empty. It enforces artifact completeness and traceability before allowing downstream integration.

Validate cross-artifact consistency by assessing PRD, architecture decisions, test plans, and threat models against defined gates. This ensures all planning and testing materials are complete and aligned before implementation.

Yes, you can generate a machine-readable PASS/FAIL readiness report by running automated readiness checks. The report validates artifact completeness against defined gates and triggers lifecycle notifications for downstream orchestration.

Yes, the readiness check validates cross-artifact completeness across architecture decisions and threat models. These artifacts must exist and be consistent with the PRD and test plans to achieve a PASS readiness summary.

Avoid automated gate management when your project lacks defined artifacts like a PRD, traceability matrix, or CI setup files. The readiness check requires these baseline artifacts to validate completeness and produce a PASS summary.