esdd-validate

To validate spec artifacts, analyze proposal.md, design.md, tasks.md, and all files under specs/ for the named change. This process detects missing sections, structural issues, and cross-file referential inconsistencies, providing a consolidated report for teams to fix before proceeding.

Cross-file referential validation checks consistency and guarantees across proposal.md, design.md, tasks.md, and specs. It ensures that references between these engineering artifacts match and that no required sections are missing before implementation begins.

Invoke a spec validator with the change name to check completeness and consistency across all related design docs and tasks. It enforces all schema and content rules as errors, producing a detailed validation report with a final verdict on readiness.

Spec validation enforces all detected issues as errors. It produces a detailed validation report containing per-file results and a final verdict, ensuring teams resolve all structural and referential problems before moving forward.

The best way to triage risk is to validate all spec artifacts for the change at once. Analyzing proposal, design, tasks, and specs together detects missing sections and cross-file inconsistencies, yielding an actionable report to fix issues before implementation.

Yes, you can validate multiple spec files simultaneously. The validator analyzes all specs under the specs/ directory along with proposal.md, design.md, and tasks.md for a named change, reporting all detected issues in a single consolidated report.