validate-spec

Automates specification validation for completeness and compliance across draft-to-approved lifecycles.

69|7|Updated Jan 19, 2026

Search Tags:#documentation #specification #quality-assurance #validate #pre-implementation #acceptance-scenarios #post-implementation

Ready to run

npx skills add https://github.com/TaylorHuston/local-life-manager --skill validate-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-spec
Source: https://github.com/TaylorHuston/local-life-manager/tree/main/.claude/skills/validate-spec
Command: npx skills add https://github.com/TaylorHuston/local-life-manager --skill validate-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates validation of specifications to ensure completeness and compliance before approval or after implementation.

Core Features & Use Cases

Mode-aware validation: detects pre- or post- implementation mode based on spec status and runs the appropriate checks
Structural completeness checks: ensures Summary, Problem Statement, Acceptance Scenarios, Agent Context, Out of Scope, and Dependencies are present
Quality guidance: highlights gaps, suggests concrete remediation, and supports post-implementation verification

Quick Start

Run the /validate-spec SPEC-001 to validate a spec in its current state and apply the appropriate pre- or post-validation mode.

Frequently Asked Questions about validate-spec

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

FAQPage Schema

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

Specification validation checks essential sections like Summary, Problem Statement, Acceptance Scenarios, Agent Context, Out of Scope, and Dependencies to ensure structural completeness and compliance before approval. It provides clear remediation guidance for any identified gaps.

Can I check if my specification meets acceptance criteria after implementation?▼

Post-implementation validation verifies specifications against acceptance scenarios and compliance requirements after development. It detects the spec status to apply mode-aware checks, ensuring the implementation matches the approved specification.

What sections are required in a specification to pass validation?▼

Specifications must include Summary, Problem Statement, Acceptance Scenarios, Agent Context, Out of Scope, and Dependencies sections to pass structural completeness validation. Missing any of these essential sections triggers remediation guidance.

How does mode-aware validation work for different spec lifecycle states?▼

Mode-aware validation detects pre- or post-implementation mode based on spec status signals, applying appropriate checks for draft, in_progress, or approved states. This ensures validation logic matches the current lifecycle stage of the specification.

What is the best way to automate specification quality assurance checks?▼

Automating specification quality assurance involves running validation checks across the spec lifecycle to verify completeness and compliance. The process highlights gaps, suggests concrete remediation, and applies lightweight readiness criteria before approval.

Why does specification validation fail when acceptance scenarios are missing?▼

Specification validation fails when acceptance scenarios are missing because they are an essential structural component required for completeness. The validator highlights this gap and provides concrete remediation guidance to add the missing section.