skills.rest
LeeHusung
LeeHusungCOMMUNITY
Explore all skills by this author →
GitHub

spec-validator

Validate requirements documents for six mandated sections and EARS patterns.

Updated Apr 21, 2026
Search Tags:#design#testing#requirements#validation#spec#ears
One-click install
npx skills add https://github.com/LeeHusung/harness --skill spec-validator-leehusung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-validator
Source: https://github.com/LeeHusung/harness/tree/main/.claude/skills/spec-validator
Command: npx skills add https://github.com/LeeHusung/harness --skill spec-validator-leehusung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Spec Validator ensures that design requirements are complete and unambiguous by confirming the six essential sections are present and properly defined before progress to design.

Core Features & Use Cases

  • Verify that all six sections (Outcomes, Scope, Constraints, Prior, Tasks, Verification) exist in a requirements document.
  • Enforce explicit scope with at least three included items, ensure every requirement uses one of the five EARS patterns, and remove ambiguous language like TBD or TODO.
  • Provide a clear, executable validation that guides teams to resolve gaps and prepares the design phase for rapid, high-quality development.
  • Use case: a product team runs the validator on a new feature spec to ensure it is production-ready before design sessions begin.

Quick Start

Run the spec-validator against your design requirements.md to verify all six sections are present and compliant.

Frequently Asked Questions about spec-validator

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

FAQPage Schema
How do I validate that a design spec contains all required sections?▼

To validate a design spec, you run a deterministic check ensuring the document contains the six mandated sections: Outcomes, Scope, Constraints, Prior, Tasks, and Verification. This enforces a complete contract before the design phase begins.

How do I check if requirements follow EARS syntax patterns?▼

You can check EARS syntax by validating the requirements document against the five EARS patterns. This removes ambiguous language like TBD or TODO, ensuring every requirement is structured and unambiguous.

What is the best way to enforce a minimum scope size in a requirements document?▼

The best way to enforce scope size is by applying a validation check that requires Scope OUT lists to contain at least three items. This ensures explicit boundaries are set before design.

Can I use steering markdown files for requirements compliance checks?▼

Yes, requirements validation can reference steering/*.md sections to verify compliance. This ensures design specs align with established project guidelines and removes gaps early.

Does spec validation work for ambiguity removal in design reviews?▼

Spec validation works for ambiguity removal by applying deterministic checks that flag undefined terms like TBD or TODO. It enforces unambiguous EARS pattern usage to prepare specs for rapid development.

Why does my requirements document fail validation before design?▼

Requirements documents fail validation when they are missing any of the six mandated sections, lack at least three scope items, or contain ambiguous language like TBD. Resolving these gaps ensures production-readiness.

Related Skills

Explore More Software Engineering Skills→
lionbenjaminlionbenjamin
15

specify

Draft product specifications with problem, goals, user stories, and acceptance criteria.

Community
Intermediate
kalamdbkalamdb
48

speckit-plan

Generate design artifacts and implementation plans from a feature specification.

Official
Advanced
ryowatanaberyowatanabe

kiro-steering

Generate and synchronize .kiro/steering/ project memory from codebase changes.

Community
Intermediate
Mahaboob26Mahaboob26

markdown-documentation

Create structured Markdown documentation with GitHub Flavored Markdown formatting.

Community
Basic