speckit-test-plan

Review gating determines whether a test plan proceeds or needs human review by evaluating behavior, contracts, and accepted coverage gaps. When ambiguity exists in API changes or workflows, the gating mechanism pauses automation to force manual validation of the negotiated test scope.

Scenario-to-test mapping connects each requirement or risk to specific validation types including API, E2E, regression, fixture, smoke, or manual coverage. This mapping ensures every public contract change or visible workflow shift has a corresponding test-case plan documented in spec.md and plan.md.

Spec-kit workflows support automated regression and fixture coverage planning through negotiated test-case plans. The workflow maps requirements to specific coverage types, updates spec and plan documents with review status, and gates progression when behavior or contracts remain ambiguous.

The best way to update spec.md and plan.md is by writing the agreed validation scope and review status directly into the artifacts. This maps requirements to API, E2E, and regression coverage, ensuring downstream implementation continues with clear, documented test intent.

Manual coverage should be used when behavior, public contracts, or accepted gaps remain ambiguous during test plan negotiation. The review gating mechanism identifies these scenarios, pausing automated E2E or API validation to require human review before proceeding with implementation.