skills.rest
qa-aman
qa-amanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-reviewer

Validates product specifications against completeness, clarity, and consistency checks with a pass/fail scorecard.

11|Updated Mar 20, 2026
Search Tags:#requirements#user stories#quality gate#spec review#product specification#scorecard#prd validation
One-click install
npx skills add https://github.com/qa-aman/next-leap-claude-code --skill spec-reviewer-qa-aman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-reviewer
Source: https://github.com/qa-aman/next-leap-claude-code/tree/main/.claude/skills/spec-reviewer
Command: npx skills add https://github.com/qa-aman/next-leap-claude-code --skill spec-reviewer-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product specs often reach Engineering, Design, and QA with missing sections, vague language like "fast" or "user-friendly", and incomplete user stories, causing misalignment and rework during the build phase. ## Core Features & Use Cases - Section Completeness Checks: Verifies required sections such as Objective, Scope, Personas, Functional Requirements, User Stories, Non-Functional Requirements, and Success Metrics exist and are not placeholder-only. - Vague Language Detection: Flags unquantified adjectives and verbs ("fast", "handle", "improve") and demands concrete metrics, dates, and quantities. - Story Coverage & ID Validation: Confirms every functionality block covers happy, edge, error, and empty paths, and that requirement IDs are unique and sequential. - Use Case: Before sending a Smart Follow-Up feature spec to stakeholders, run the review to get a scorecard grading each check as PASS, FAIL, or WARN, plus an ordered fix list. ## Quick Start Review the spec at 08-product-features/smart-follow-up-prd.md and give me a pass/fail scorecard with fix suggestions.

Frequently Asked Questions about spec-reviewer

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

FAQPage Schema
How do I review a product spec before sending it to engineering?▼

Run the spec review on your draft file to check section completeness, vague language, requirement IDs, and story coverage. It returns a scorecard with PASS, FAIL, or WARN per check plus a fix list ordered by severity.

What sections should a complete product specification include?▼

A complete spec includes an Objective or Problem Statement, in-scope and out-of-scope definitions, User Personas, Functional Requirements, User Stories covering all four paths, Non-Functional Requirements, and Success Metrics.

What counts as vague language in a product requirements document?▼

Vague language includes unquantified terms like "fast", "user-friendly", "soon", "many", and verbs like "handle" or "improve" without measurable targets. Each instance is flagged as a WARN with a suggestion to specify metrics, dates, or exact operations.

Why does a spec fail the quality review?▼

A spec fails when it has one or more FAIL results, such as missing required sections, empty out-of-scope tables, or "TBD" placeholders in critical sections. Zero FAILs with warnings grades as PASS WITH WARNINGS.

What user story paths should every feature cover?▼

Every functionality block should include stories for the happy path, edge cases, error states, and empty states. Missing any of these four paths is flagged during the story coverage check.

Related Skills

Explore More Product & Management Skills→
kmshihab7878kmshihab7878
6

product-manager-toolkit

Score feature CSVs with RICE and synthesize interview transcripts into roadmaps.

Community
Advanced
hongmaple0820hongmaple0820
9

agile-product-owner

Convert requirements into INVEST-aligned user stories and backlog items.

Community
Advanced
clawpod-appclawpod-app
46

research-synthesis

Synthesize user research data into structured reports with themes and recommendations.

Community
Advanced
jasonmeansjasonmeans
2

todo-launch-checklist

Walks product managers through a customizable launch checklist covering readiness to go-to-market.

Community
Intermediate