testspec-review

Audit test specifications across 14 dimensions and generate review-report.md.

5|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/winhok/testkit --skill testspec-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testspec-review
Source: https://github.com/winhok/testkit/tree/main/skills/testspec-review
Command: npx skills add https://github.com/winhok/testkit --skill testspec-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Test specifications often suffer from quality gaps, ambiguity, and traceability issues that hinder reliable testing outcomes. This Skill performs a comprehensive 14-dimension review on generated test cases to surface actionable improvements.

Core Features & Use Cases

  • Comprehensive 14-dimension checks (R1–R6 and H1–H8) to validate coverage, naming, readability, and traceability.
  • Generates a structured review-report.md detailing issues with severity (S1–S3) and a clear closure path, plus context seeds for downstream skills.
  • Supports mode and depth controls (Strict/Legacy, auto or --deep) and loads upstream context when available.

Quick Start

Provide a change directory that contains testcases.json and specs/testpoints.md, then trigger the testspec-review workflow to generate a review-report.md.

Frequently Asked Questions about testspec-review

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

FAQPage Schema
How do I review test specifications for quality and traceability issues?

You can review test specifications by loading a change directory containing testcases.json and specs/testpoints.md to trigger an automated audit. The workflow applies 14-dimension checks across R1–R6 and H1–H8 dimensions, producing a structured review-report.md detailing actionable issues with S1–S3 severity ratings.

What is a testspec review report and how does it work?

A testspec review report is a structured markdown document generated after auditing test cases for executable quality and traceability. It details discovered issues with severity ratings from S1 to S3 and includes context seeds to guide downstream testing workflows.

How do I run a deep quality assurance check on generated test cases?

Trigger the testspec-review workflow with the --deep mode to execute comprehensive 14-dimension checks on generated test cases. This loads available upstream context and validates coverage, naming, readability, and traceability across R1–R6 and H1–H8 dimensions.

Does the test specification audit support strict mode for legacy workflows?

Yes, the test specification audit supports both Strict and Legacy mode detection. It automatically determines the appropriate mode or accepts manual depth controls to ensure the review aligns with your specific workflow generation requirements.

What input files are required to generate a structured test spec review report?

Generating a structured review report requires a change directory containing testcases.json and specs/testpoints.md. The workflow performs input health checks on these files before executing the 14-dimension audit and outputting the final markdown report.

Why do my generated test cases fail traceability checks during spec analysis?

Test cases fail traceability checks during spec analysis when they lack clear links to upstream requirements or test points. The audit identifies these gaps across 14 dimensions and outputs an actionable review report with S1–S3 severity ratings to guide closure.