dev-spec-reviewer

Validate SPEC.md specification documents for completeness and quality.

19|5|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/edwinhu/workflows --skill dev-spec-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-spec-reviewer
Source: https://github.com/edwinhu/workflows/tree/main/lib/skills/dev-spec-reviewer
Command: npx skills add https://github.com/edwinhu/workflows --skill dev-spec-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents wasted development effort by ensuring that specification documents are complete and well-defined before the exploration and implementation phases begin.

Core Features & Use Cases

  • Automated Spec Review: Dispatches a subagent to rigorously check SPEC.md for completeness, clarity, and consistency.
  • Early Issue Detection: Catches ambiguities, missing information, and scope creep before they impact development.
  • Use Case: After brainstorming a new feature, use this skill to have an AI reviewer verify the SPEC.md document is ready, preventing costly rework later in the development cycle.

Quick Start

Use the dev-spec-reviewer skill to verify the completeness of the spec document located at .claude/SPEC.md.

Frequently Asked Questions about dev-spec-reviewer

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

FAQPage Schema
How do I validate a software specification before starting development?

A spec review checks your specification document for completeness, clarity, and consistency before development starts. It prevents wasted effort by catching ambiguities, missing information, and scope creep early in the software development lifecycle.

How do I check if my SPEC.md is ready for the implementation phase?

You can check if your SPEC.md is ready by running an automated spec review that verifies all required sections like edge cases, testing strategies, and success criteria are adequately defined. This enforces a strict phase gate before proceeding to exploration.

What sections should a specification document include to pass a phase gate review?

To pass a phase gate review, a specification document must include adequately defined sections for error handling, edge cases, testing strategies, and success criteria. This requirement validation ensures the spec is complete and unambiguous.

Why does requirement validation fail during the development workflow?

Requirement validation fails when the specification document contains ambiguities, missing information, or scope creep. Catching these issues early through an automated spec review prevents costly rework later in the development cycle.

Can I use automated spec review to catch scope creep before coding?

Yes, you can use automated spec review to catch scope creep before coding begins. The reviewer rigorously checks the specification document for consistency and completeness, preventing the exploration of incomplete or ambiguous requirements.

Does the spec review process work with existing markdown specification files?

Yes, the spec review process works with existing markdown specification files by targeting the SPEC.md document located in your project. It validates the completeness and quality of the specification directly within your development workflow.