plan-validator

Markdown plan validation checks filenames for YYYY-MM-DD-slug.md format, enforces H1 headings as the first non-empty line, verifies phase markers like [ ] or [x], and ensures a non-empty final Итог block to maintain document consistency.

To enforce date-formatted filenames and headers in markdown plans, use a validation tool that checks for YYYY-MM-DD-slug.md kebab-case format and requires an H1 heading as the first non-empty line of the document content.

Yes, you can integrate markdown plan validation into pre-commit hooks. Running the validator before committing automatically verifies format compliance, preventing invalid or inconsistent plans from entering the workflow.

Plan filenames need to follow the YYYY-MM-DD-slug.md format for markdown validation. This requires a valid date prefix and a kebab-case slug to pass the repository's planning standards checks.

Yes, the validator checks phase markers and final content structure in markdown. It validates the presence and formatting of phases marked with [ ] or [x] and ensures a non-empty final Итог section at the end of the document.

Your markdown plan fails validation before a commit if it violates repository rules from CLAUDE.md and plans/README.md, such as incorrect filename format, missing H1 header, invalid phase markers, or an empty final Итог block.