GSD Plan Checker

You can validate execution plans by checking requirement coverage, task completeness, dependency correctness, and scope sanity. This prevents execution failures by rigorously auditing planning documents against defined criteria to ensure readiness before running.

Checking for acyclic dependencies involves validating valid links between plans and consistent wave assignments. This ensures correct dependency management across multiple plans within a phase, preventing circular execution roadblocks.

Requirement coverage is the verification that every phase requirement is addressed by at least one task. It ensures task completeness by confirming all tasks include necessary elements like Files, Action, Verify, and Done criteria.

You can assess scope sanity by analyzing if plans are within reasonable limits for tasks, files, and context size. This scope sanity check prevents quality issues by catching overly complex or unmanageable plans early in the cycle.

Generating a quality gate report requires parsing PLAN.md, ROADMAP.md, and REQUIREMENTS.md files. This produces a comprehensive readiness assessment by analyzing requirement coverage, task completeness, and dependency correctness across multiple plans.

Execution plans often fail due to incomplete task elements, invalid dependencies, or poor requirement coverage. Validating plans against defined criteria before running catches these problems early, thus avoiding costly rework.