GSD Plan Checker

To validate a PLAN.md file, run the plan-checker to verify requirement coverage, task completeness, dependency correctness, and cross-link integrity across all defined project dimensions. It surfaces gaps between goals and tasks to prevent execution failures.

Plan validation is the process of checking planning artifacts for completeness, coherence, and proper linking before execution. You need it after creating ROADMAP.md and PLAN.md files to catch quality problems and ensure all requirements are properly covered.

Yes, the plan-checker validates both ROADMAP.md and PLAN.md documents across all project phases. It checks dependency correctness and cross-link integrity while ensuring frontmatter includes phase, plan, wave, depends_on, and must_haves fields.

Verify plan tasks by running the checker to ensure each task lists the Files, Action, Verify, and Done dimensions. This validation guarantees task completeness and confirms that frontmatter contains the required phase and dependency metadata.

Common issues caught include missing frontmatter fields like phase, plan, wave, depends_on, and must_haves, incomplete task dimensions lacking Files, Action, Verify, or Done, and incorrect dependencies or broken cross-links between requirements and tasks.

No dependencies are required to check PLAN.md files for execution failures. The plan-checker operates independently to validate requirement coverage, task completeness, dependency correctness, and cross-link integrity across your planning artifacts.