~aod-spec

Validate spec.md files for mandatory sections and readiness markers.

86|21|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/davidmatousek/tachi --skill aod-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ~aod-spec
Source: https://github.com/davidmatousek/tachi/tree/main/.claude/skills/~aod-spec
Command: npx skills add https://github.com/davidmatousek/tachi --skill aod-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates specification files (spec.md) for completeness, quality, and readiness for architecture and implementation phases, ensuring specifications are ready for architecture and implementation.

Core Features & Use Cases

  • Locate and validate specs at specs/*/spec.md
  • Check mandatory sections (User Scenarios & Testing, Requirements, Success Criteria, Scope)
  • Detect [NEEDS CLARIFICATION] markers and report line numbers
  • Verify testable criteria and bounded scope
  • Generate a structured readiness report

Quick Start

Run the spec validator on a target spec.md to generate a complete quality report.

Frequently Asked Questions about ~aod-spec

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

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

To validate specification completeness, run the validator against specs/*/spec.md to check mandatory sections like Requirements and Success Criteria. It detects [NEEDS CLARIFICATION] markers and generates a structured readiness report indicating READY or NOT READY with actionable recommendations.

What mandatory sections must a spec.md file include to pass validation checks?▼

Mandatory sections for spec validation include User Scenarios & Testing, Requirements, Success Criteria, and Scope. The validator locates specs at specs/*/spec.md and verifies these sections exist and meet completeness criteria before producing a readiness report.

How do I check if my requirements document has unresolved clarification markers?▼

To check for unresolved clarification markers, run the spec validator on your spec.md file. It detects [NEEDS CLARIFICATION] markers and reports their exact line numbers in the structured readiness report, flagging the specification as NOT READY until resolved.

When should I run a specification readiness report for architecture and implementation phases?▼

Run a specification readiness report before starting architecture and implementation phases to ensure your spec.md is complete and clear. The validator checks for bounded scope and testable criteria, producing a READY or NOT READY status to confirm preparation for downstream development.

Does the specification validator work with any markdown file or only specific directory structures?▼

The specification validator works specifically with spec.md files located at specs/*/spec.md across repositories. It identifies and validates specification files within this exact directory structure, verifying mandatory sections, testable criteria, and bounded scope to produce a structured readiness report.