spec-validator

Spec-driven development validation checks your feature specifications, implementation plans, and task breakdowns for completeness, consistency, and alignment with project conventions. Run the validator against your specs directory to identify missing files, content gaps, and cross-reference misalignments before coding begins, reducing rework and accelerating delivery.

Complete SDD artifacts require spec.md, plan.md, and tasks.md files within a feature directory, plus optional governance files like constitution.md. The validator checks that required files exist and that each spec contains a clear name, WHAT-it-does description, user stories, and measurable acceptance criteria.

Yes. The validator performs cross-reference validation to check alignment between your spec, plan, and tasks, flagging gaps and inconsistencies before implementation. This ensures traceability across artifacts and prevents misaligned work downstream.

Content quality checks ensure each spec contains a clear name, WHAT-it-does description, user stories, and measurable acceptance criteria. The validator exposes missing or incomplete sections, providing actionable remediation guidance aligned with your project conventions.

Run spec validation immediately after drafting feature specifications, implementation plans, and task breakdowns—before implementation begins. Early validation catches completeness and consistency issues, ensuring governance alignment and preventing rework.

The validator is designed for projects using spec-driven development conventions with artifacts organized in a specs directory by feature. It checks for standard SDD file structures and governance files; results indicate alignment with project conventions you've established.