GSD Plan Checker

Validating development plans before execution requires checking requirement coverage, task completeness, dependency correctness, and scope sanity. This plan validation process analyzes ROADMAP.md, REQUIREMENTS.md, and PLAN.md files to identify blockers, missing elements, and circular dependencies.

Checking for circular dependencies in task management plans involves analyzing PLAN.md files to verify that task dependencies are valid, acyclic, and correctly sequenced. This dependency management process prevents execution blockers by detecting circular references before development begins.

Ensuring requirement coverage across development phases requires analyzing REQUIREMENTS.md and PLAN.md files to verify every phase requirement is addressed by at least one task. This validation process identifies uncovered requirements and missing elements like Files, Action, Verify, and Done criteria.

Assessing scope creep and task completeness in markdown planning files involves evaluating ROADMAP.md, REQUIREMENTS.md, and PLAN.md to determine if plans are within reasonable limits for tasks, files, and context. This scope sanity check ensures all tasks include necessary elements before execution.

A quality gate for dependency checks and scope validation is needed before deploying new features or executing development phases. This validation step prevents costly errors by ensuring development tasks are properly defined, dependencies are met, and the scope is manageable.

GSD Plan Checker works with ROADMAP.md, REQUIREMENTS.md, and PLAN.md files to validate plans against defined criteria. It analyzes these markdown files to identify blockers and warnings, ensuring plans are ready for execution by checking for missing elements and scope creep.