skills.rest
davidmatousek
davidmatousekCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-validator

Validate spec.md files for completeness, quality, and readiness.

21|6|Updated Feb 8, 2026
Search Tags:#documentation#specification#requirements#validation#clarity#acceptance-criteria
One-click install
npx skills add https://github.com/davidmatousek/agentic-oriented-development-kit --skill spec-validator-davidmatousek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-validator
Source: https://github.com/davidmatousek/agentic-oriented-development-kit/tree/main/.claude/skills/spec-validator
Command: npx skills add https://github.com/davidmatousek/agentic-oriented-development-kit --skill spec-validator-davidmatousek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically validates specification files (spec.md) for completeness, quality, and readiness for architecture and implementation phases.

Core Features & Use Cases

  • Locate specification files under specs/*/spec.md and validate structural requirements.
  • Check mandatory sections (User Scenarios & Testing, Requirements, Success Criteria, Scope) and verify scope boundaries.
  • Identify and report [NEEDS CLARIFICATION] markers for clarification and provide actionable recommendations.
  • Ensure requirements are testable and success criteria are measurable to accelerate progression to planning and implementation.
  • Generate a structured validation report with issues found and recommendations.

Quick Start

Run the spec validator against your repository to locate specs, perform validations, and generate a readiness report.

Frequently Asked Questions about spec-validator

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

FAQPage Schema
How do I validate a specification document for completeness before implementation?▼

Specification validation identifies missing mandatory sections like User Scenarios & Testing, Requirements, and Success Criteria, while verifying that requirements are testable and scope is bounded to ensure readiness for architecture phases.

How do I check if my requirements and acceptance criteria are testable and measurable?▼

Checking testable requirements involves verifying that success criteria are measurable and scope boundaries are explicitly defined, automatically flagging untestable conditions and generating actionable recommendations for clarification.

What is the best way to track down unresolved [NEEDS CLARIFICATION] markers in my specs?▼

The best way to track unresolved markers is to run an automated validation pass across specs/*/spec.md files, which identifies [NEEDS CLARIFICATION] tags and outputs a report detailing exactly where clarifications are needed.

Does spec validation work with specification files located in custom directories?▼

Spec validation specifically targets files located under the specs/*/spec.md directory structure, automatically locating and validating specification files within this bounded path to ensure structural requirements are met.

When do I need to run a specification readiness check for my project?▼

You need to run a specification readiness check when transitioning from requirements gathering to architecture and implementation phases, ensuring all user stories, acceptance criteria, and scope boundaries are clearly defined and free of clarification markers.

Related Skills

Explore More Product & Management Skills→
yoshisadayoshisada

specify

Convert natural language feature descriptions into structured spec.md files.

Community
Advanced
silaslopes100silaslopes100

reversa-designer

Design target system architectures and migration plans from legacy system analysis.

Community
Advanced
ddobrinddobrin
39

plan-refiner

Refine architectural plans by applying user feedback to Markdown documents.

Community
Advanced
lionbenjaminlionbenjamin
15

clarify

Review feature specifications for clarity, completeness, and edge cases.

Community
Advanced