spec-review

To verify design specs align with Gherkin feature specs, cross-check the design document against the authored scenarios to ensure full coverage and traceability before implementation planning.

Design-to-spec traceability maps each design requirement to corresponding Gherkin spec scenarios. You need it during design-review cycles to validate alignment and enforce coverage before development begins.

Yes, you can identify gaps between your design document and feature specs by mapping requirements to Gherkin scenarios, which flags missing coverage and extra spec scenarios in a structured report.

No, this design review process requires both an existing design document and authored Gherkin specs to function, as it cross-checks these two artifacts against each other for alignment.

The best way to report spec coverage gaps and drift is to map design requirements to Gherkin scenarios, automatically flagging missing coverage and extra scenarios with structured traceability reports.