plan-validate

To validate frontmatter metadata in design plan documents, run the validation command on a specific plan or use the --all flag. This identifies missing required fields, invalid values, and structural issues across active and archived entries in .claude/plans.

Enforcing required fields and date formats in plan frontmatter requires a validation script that checks data types, status-progress alignment, and conditional field rules. This ensures metadata consistency and governance across all design plan documents.

Yes, you can integrate plan frontmatter validation into pre-commit hooks or CI workflows. The validation generates actionable feedback and provides integration hooks to automate quality assurance checks before code commits.

Status-progress alignment validation checks that the progress value matches the declared status in plan frontmatter. It enforces required conditional fields like completed/outcome for finished plans and abandoned/archival entries for dropped ones to maintain tracking accuracy.

Design plans fail metadata consistency checks when required frontmatter fields like name, title, created, status, or progress are missing, contain invalid data types, or violate conditional field rules. The validator reports these structural issues with actionable feedback.