qa-strategy

To generate a QA strategy, you need to codify test matrices, UAT criteria, regression scenarios, and observability guidelines directly from your SPEC.md, ARCH.md, and DEV-SPEC.md artifacts. This ensures traceability from requirements through tests to deployment.

Creating a test matrix involves deriving components from ARCH.md and defining the test Type, Tool, Coverage Target, and Owner for each. This approach anchors test planning directly to your architectural components and ensures structured coverage.

Yes, you need confirmed SPEC.md, ARCH.md, and DEV-SPEC.md prerequisites before generating UAT criteria. The system guarantees these upstream prerequisites exist and derives UAT criteria directly from SPEC.md acceptance criteria with explicit traceability.

Regression scenarios and observability guidelines are core sections of a cohesive QA plan. Regression scenarios capture critical non-negotiable behaviors, while observability guidelines specify logging expectations to support operations and incident response.

QA planning lacks traceability when test matrices and UAT criteria are not anchored to SPEC.md and ARCH.md. By generating a cohesive QA.md that serves as a gating document between Layer 1 artifacts and release, you ensure end-to-end traceability.

No, you cannot effectively use this approach without predefined acceptance criteria. The tool explicitly derives UAT criteria and test matrices from SPEC.md acceptance criteria and ARCH.md components, requiring these inputs to function correctly.