spec-validator

Spec validation checks that required files (spec.md, plan.md, tasks.md) exist and are properly structured within your feature directory. Point the validator at your specs folder—for example, specs/001-user-auth—and it produces a comprehensive report detailing missing sections, gaps, and actionable recommendations to ensure specs are complete before implementation.

The validation report details findings across spec completeness, plan feasibility, and task breakdown accuracy. It checks cross-reference consistency between artifacts, verifies all user stories are covered, highlights ambiguities and scope issues, and provides recommendations to resolve gaps before development begins.

Yes. Spec validation performs cross-artifact checks across specs, plans, and tasks to ensure they align and cover all user stories. It enforces required files and sections, then validates that information flows consistently between artifacts without conflicts or missing coverage.

Run spec validation before implementation begins. It catches completeness issues, consistency problems, and scope misalignments early, reducing rework and miscommunication. Apply it to specs, plans, and task artifacts across feature directories as part of your pre-development quality gate.

Spec validation ensures Spec-Driven Development artifacts are complete, consistent, and aligned with project conventions before coding starts. It addresses spec completeness, plan feasibility, task breakdown accuracy, and cross-reference consistency—reducing implementation delays caused by incomplete or conflicting requirements.

Yes. Spec validation requires your feature directory to contain spec.md, plan.md, and tasks.md files. It validates their structure and content; if required files are missing, the validation report highlights those gaps so you can create them before proceeding.