validate-links

To check for broken Markdown links in a repository, you can validate cross-link integrity by scanning relative link targets across all Markdown files. This process detects broken relative links while excluding external links, ensuring documentation stays internally consistent.

Verifying schema and requirement bidirectional symmetry involves checking that requirements listing a schema under 'Used by' correctly link back via the requirement's Schema section. This ensures bidirectional symmetry constraints are satisfied across all spec files.

The best way to enforce index completeness for Markdown documentation is to validate that index files like requirements/index.md and schemas/index.md list all existing files and include every file present in their respective directories, enforcing index inclusion rules.

Your requirements index shows a different file count than the actual directory due to a counter consistency mismatch between declared counts in prose files and actual file counts. Running a counter consistency verification detects these mismatches between README or index declarations and on-disk reality.

You should run link validation in a repository maintenance workflow after editing spec files, adding schemas or requirements, or restructuring documentation. This ensures link existence verification, bidirectional symmetry, and index completeness are maintained after content changes.

Yes, you can detect missing required sections in challenge and requirement files through content completeness reporting. This reports which specific files are missing required sections, guiding ongoing authoring and ensuring required section coverage across the CLI Agent Spec.