spec-review

Name: spec-review
Availability: InStock
Author: Pandaworks

Cross-check design documents against Gherkin specs for coverage and alignment.

Updated Mar 1, 2026

Search Tags:#design #verification #traceability #quality-assurance #gherkin #specs #gap-analysis

Ready to run

npx skills add https://github.com/pandaworks-software-plt/pandahrms-skills --skill spec-review-pandaworks-software-plt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/pandaworks-software-plt/pandahrms-skills/tree/main/skills/spec-review
Command: npx skills add https://github.com/pandaworks-software-plt/pandahrms-skills --skill spec-review-pandaworks-software-plt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-checks the design document against the written Gherkin specs to ensure full coverage and alignment.

Core Features & Use Cases

Design-to-spec alignment: verify every design requirement has corresponding spec coverage.
Spec coverage mapping: identify which feature specs cover each design requirement.
Gap and drift reporting: produce a report detailing gaps and extra spec scenarios, with traceability.

Quick Start

Run this skill after specs are written to validate alignment between the design document and the feature specs.

Frequently Asked Questions about spec-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify design specs fully align with Gherkin feature specs?▼

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.

What is design-to-spec traceability and when do I need it?▼

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.

Can I identify gaps between my design document and feature specs?▼

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.

Does this design review process work without existing Gherkin specs?▼

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.

What's the best way to report spec coverage gaps and drift?▼

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.