GSD Plan Checker

Validate GAPL-format plans for coverage, completeness, cycles and wiring before execution.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/apsulli/gmail-intel --skill gsd-plan-checker-apsulli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GSD Plan Checker
Source: https://github.com/apsulli/gmail-intel/tree/main/.opencode/skills/plan-checker
Command: npx skills add https://github.com/apsulli/gmail-intel --skill gsd-plan-checker-apsulli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GSD Plan Checker helps product teams catch plan gaps, coverage issues, and dependency problems before execution, reducing risk and rework across multi-phase projects.

Core Features & Use Cases

  • Validates requirement coverage: ensures every phase goal has one or more tasks addressing it.
  • Ensures task completeness: checks that each task has Files, Action, Verify, and Done where applicable.
  • Verifies dependency correctness: detects cycles, missing references, and invalid wave sequencing.
  • Connects artifacts: verifies that plans are wired to roadmaps and that components like tasks, plans, and requirements align.

Quick Start

Run the plan checker on your ROADMAP.md, REQUIREMENTS.md, and all PLAN.md files to surface coverage gaps and circular dependencies before execution.

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 requirements coverage before starting multi-phase roadmap execution?

To validate requirements coverage, check that every phase goal in your roadmap has corresponding tasks addressing it. This ensures complete requirements-to-task coverage and prevents execution gaps across project waves.

What causes circular dependencies in project plans and how do I detect them?

Circular dependencies occur when task references form cycles across waves. Detect them by verifying dependency correctness, checking for invalid wave sequencing, and identifying missing references between connected plan components.

How do I check if my task plans have all required fields for execution completeness?

Check task completeness by verifying each task includes Files, Action, Verify, and Done fields where applicable. This ensures plans have the necessary wiring between components before execution begins.

Can I use plan validation for multi-phase roadmaps with complex wave dependencies?

Yes, plan validation applies to multi-phase roadmaps with complex wave dependencies. It analyzes coverage, completeness, and cycles across phases by reading ROADMAP.md, REQUIREMENTS.md, and PLAN.md frontmatters.

Why does my plan execution fail due to missing wiring between roadmaps and task plans?

Plan execution fails when artifacts are not properly wired together. Verify that plans connect to roadmaps and that components like tasks, requirements, and plans align to catch gaps before execution.