speckit-validator

To validate a spec.md file, check for mandatory sections including User Scenarios & Testing, Requirements, Success Criteria, and Scope. Spec validation verifies testable criteria and bounded scope to prevent gaps before implementation begins.

A requirements specification is testable when it contains clear acceptance criteria, bounded scope, and resolved clarification markers. Validation checks ensure all mandatory sections exist and no [NEEDS CLARIFICATION] tags remain before proceeding to architecture.

Checking for unresolved clarification markers involves scanning the spec.md file for [NEEDS CLARIFICATION] tags. Automated validation detects these markers and generates a structured report highlighting areas requiring further definition before implementation.

Yes, you can automate spec quality checks by running a validator against your repository. It confirms the presence of mandatory sections—Scope, Success Criteria, Requirements, and User Scenarios & Testing—and produces a concise validation report with actionable recommendations.

A specification validation report includes the status of mandatory sections, detected [NEEDS CLARIFICATION] markers, testability verification of acceptance criteria, scope bounding confirmation, and actionable recommendations to improve spec quality.

You should run a spec validation check after drafting your spec.md and before starting architecture or implementation phases. Validating early prevents requirement gaps, untestable criteria, and unbounded scope from causing downstream development issues.