spec-validation

You can validate specifications by checking required sections, header hierarchy, and frontmatter presence to ensure specs are structurally correct, navigable, and ready for reliable builds.

Cross-reference validation verifies that delta references and label integrity match across specs, preventing drift between documentation and implementation by ensuring all linked content is consistent.

Completeness validation enforces that every requirement has at least one scenario and no empty sections exist, avoiding ambiguous language and ensuring specs are fully ready for implementation.

Yes, spec validation enforces frontmatter presence, requiring both a name and description in the metadata to ensure documents are well-formed and properly identified before processing.

Yes, the validation workflow applies directly to changes and deltas within brainstorm and plan workflows, checking structure, content, cross-references, and completeness for reliable builds.

Running the superspec validate command allows you to execute the validation workflow on a single change or across all specs, checking structure, content, and consistency automatically.