gsd-plan-checker

Validate PLAN.md files for task completeness, dependencies, and file ownership.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tDalile/dotfiles --skill gsd-plan-checker-tdalile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-plan-checker
Source: https://github.com/tDalile/dotfiles/tree/main/agents/skills/gsd/agents/plan-checker
Command: npx skills add https://github.com/tDalile/dotfiles --skill gsd-plan-checker-tdalile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces plan quality by validating that every plan created during the GSD planning phase is complete, correctly dependent, owned without file conflicts, and appropriately scoped so plans are executable and predictable.

Core Features & Use Cases

  • Task completeness checks: Ensures each task contains required fields such as name, files, action, verify, and done.
  • Dependency and cycle detection: Validates depends_on arrays, wave assignments, and flags invalid or circular dependencies.
  • File ownership and scope validation: Detects overlapping file modifications, enforces plan sizing rules, and verifies must_haves structure for goal-backward derivation.
  • Use case: Run this agent as part of the /gsd:plan-phase verification loop to produce a VERIFICATION-CHECKER.md that lists blockers, major issues, and minor issues for plan authors to fix.

Quick Start

Validate all PLAN.md files in the current phase and produce a VERIFICATION-CHECKER.md with categorized issues.

Frequently Asked Questions about gsd-plan-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate task dependencies and detect cycles in a plan?

Plan validation parses depends_on arrays and wave assignments to detect invalid or circular dependencies. It checks task completeness and flags dependency issues, producing a structured report of categorized blockers and major issues.

What is the best way to check for overlapping file modifications in a plan?

File ownership validation detects overlapping file modifications across tasks to prevent conflicts. It enforces plan sizing rules and verifies must_haves structure, ensuring files are owned without conflicts for predictable execution.

How do I verify that PLAN.md files have all required task fields?

Task completeness checks parse YAML frontmatter and task blocks to find missing fields. It ensures each task contains required fields like name, files, action, verify, and done, emitting a verification report with categorized issues.

Can I use plan validation for scope sanity checks and goal-backward derivation?

Yes, plan validation verifies scope sanity by checking must_haves structure for goal-backward derivation. It enforces plan sizing rules and ensures the plan is appropriately scoped and executable.

Why does my plan validation report show blockers and major issues?

A verification report categorizes issues into blockers, major issues, and minor issues. Blockers typically indicate missing required task fields, invalid dependencies, or overlapping file modifications that prevent executable plans.