discussion-validate

To validate discussion docs, you check them for frontmatter presence, section structure, numbering, markers, and ownership mapping. This identifies and reports any deviations from the established SDD standard.

Yes, you can run batch validation across the specs directory. The tool supports checking individual discussions and batch validation to support code reviews and pre-commit checks.

Structural checks enforce frontmatter presence, required fields, section names, order, numbering, and markers. This ensures consistent, high-quality discourse documentation without confusing structural deviations.

Ownership mapping validation ensures clear ownership responsibilities are documented within the discussion docs. It enforces checks that map accountability according to the SDD standard.

The best way to lint discussion documentation is applying validation checks to frontmatter, sections, and ownership mapping. This enforces consistent structure and prevents review delays caused by non-standard formatting.

You need SDD standard validation when discussions fail to adhere to a standardized structure, causing review confusion. It enforces consistent formatting for frontmatter, naming, sections, and ownership responsibilities.