skills.rest
wtsi-hgi
wtsi-hgiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spec-reviewer

Validate feature specifications against user descriptions for completeness and architectural adherence.

Updated Nov 27, 2025
Search Tags:#quality assurance#acceptance criteria#requirements coverage#specification review#feature completeness#architectural validation
One-click install
npx skills add https://github.com/wtsi-hgi/llm-knowledge-base --skill spec-reviewer-wtsi-hgi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-reviewer
Source: https://github.com/wtsi-hgi/llm-knowledge-base/tree/main/.github/skills/spec-reviewer
Command: npx skills add https://github.com/wtsi-hgi/llm-knowledge-base --skill spec-reviewer-wtsi-hgi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that feature specifications are complete and accurately reflect the user's original feature description, preventing scope creep and ensuring all requirements are addressed.

Core Features & Use Cases

  • Coverage Analysis: Verifies that every requirement in the feature description has corresponding user stories and acceptance tests in the spec.
  • Testability Check: Assesses if acceptance tests are explicit enough for implementation.
  • Architectural Adherence: Confirms the spec follows defined architectural principles.
  • Use Case: A product manager provides a feature description and a draft specification. The Spec Reviewer Skill analyzes the spec to confirm it fully covers all aspects of the feature description, flagging any missing user stories, vague tests, or architectural inconsistencies.

Quick Start

Use the spec-reviewer skill to check if the feature specification at '/path/to/spec.md' fully covers the user's feature description.

Frequently Asked Questions about spec-reviewer

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

FAQPage Schema
How do I validate a feature specification against user requirements?▼

To validate a feature specification, compare the spec document against the original user feature description to identify missing requirements, untestable acceptance criteria, and architectural deviations, ensuring full requirements coverage and feature completeness.

What is requirements coverage analysis in specification review?▼

Requirements coverage analysis is the process of verifying that every requirement in a user feature description has corresponding user stories and acceptance tests in the specification, preventing scope creep and ensuring all requirements are addressed.

How do I check if acceptance criteria are testable for implementation?▼

You can check acceptance criteria testability by assessing whether the criteria in the specification are explicit enough for implementation. The review process flags vague tests that lack the clarity needed for developers to execute them effectively.

Can I use architectural validation to find inconsistencies in a feature spec?▼

Yes, architectural validation confirms that your feature specification follows defined architectural principles. It operates by comparing user-defined requirements against spec content and architectural guidelines to flag any structural deviations.

What is the best way to prevent scope creep in feature specification documents?▼

The best way to prevent scope creep is to perform a specification review that ensures the feature spec accurately reflects the user's original feature description, verifying complete coverage and adherence to architectural guidelines before implementation begins.

Do I need a draft specification and a feature description to check feature completeness?▼

Yes, you need both a draft specification document and a provided user feature description. The review process requires these two inputs to compare spec content against user-defined requirements and identify missing user stories or vague tests.

Related Skills

Explore More Product & Management Skills→
pretodevpretodev
1

creating-feature-spec

Generate structured feature specification documents from feature definitions.

Community
Intermediate
LaunchPadLabLaunchPadLab
1

feature-review

Review feature specifications for completeness and generate missing Gherkin scenarios.

Official
Intermediate
stratusstratus
2

implement

Automate phased feature implementation with user-story validation and quality gates.

Community
Intermediate
mtaku3mtaku3
2

Requirements Definition

Define structured software requirements with traceability and acceptance criteria.

Community
Basic