plan-checker

Validates PLAN.md files against six quality dimensions before execution.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/amanpal3/SKILLs --skill plan-checker-amanpal3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-checker
Source: https://github.com/amanpal3/SKILLs/tree/main/.agent/plugins/gsd/.agents/skills/plan-checker
Command: npx skills add https://github.com/amanpal3/SKILLs --skill plan-checker-amanpal3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans written for autonomous execution often contain hidden flaws—missing tasks, circular dependencies, or oversized scope—that only surface as failures mid-execution. This Skill catches those problems before execution begins, acting as a quality gate between planning and execution. ## Core Features & Use Cases - Six-Dimension Validation: Checks requirement coverage, task completeness, dependency correctness, key links between artifacts, scope sanity, and verification derivation. - Structured Issue Reporting: Outputs issues in YAML format with severity levels (blocker, warning, info), affected plan/task, and concrete fix hints. - Dependency Graph Analysis: Parses depends_on frontmatter across plans to detect cycles, missing references, and incorrect wave assignments. - Use Case: After running a planning phase that generates PLAN.md files for a multi-phase roadmap, run this checker to confirm every requirement has covering tasks and no circular dependencies exist before starting execution. ## Quick Start Validate all PLAN.md files in the current phase against the roadmap and report any blockers or warnings before execution.

Frequently Asked Questions about plan-checker

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

FAQPage Schema
How do I validate implementation plans before executing them?▼

Run the plan checker after planning completes and before execution starts. It reads ROADMAP.md and all PLAN.md files in the phase, checks six validation dimensions, and reports blockers and warnings with suggested fixes.

What makes a task complete in a PLAN.md file?▼

A complete auto task requires Files, Action, Verify, and Done elements. TDD tasks need behavior plus implementation actions, test commands, and expected outcomes. Missing verify or done elements are flagged as blockers.

How are circular dependencies between plans detected?▼

The checker parses depends_on from each plan's frontmatter, builds a dependency graph, and checks for cycles, missing references, and future references. Wave numbers must equal max dependency wave plus one.

When should the plan checker run in the workflow?▼

Run it after planning completes, before execution starts, and after any plan modifications. It serves as the quality gate between the planning and execution phases.

What is the difference between a blocker and a warning?▼

A blocker will cause execution failure and must be fixed before proceeding, such as a missing verify element or circular dependency. A warning indicates quality or efficiency risk, like an oversized plan, and can be proceeded past.