plan-checker

Validate PLAN.md files against six critical execution readiness dimensions.

2|Updated Jan 12, 2026

Search Tags:#dependency analysis #plan validation #scope management #execution check #workflow quality #task completeness

Ready to run

npx skills add https://github.com/SukbeomH/HExoskeleton --skill plan-checker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-checker
Source: https://github.com/SukbeomH/HExoskeleton/tree/main/.claude/skills/plan-checker
Command: npx skills add https://github.com/SukbeomH/HExoskeleton --skill plan-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents execution failures and quality issues by rigorously validating PLAN.md files before they are run, acting as a crucial quality gate.

Core Features & Use Cases

Comprehensive Validation: Checks plans against 6 critical dimensions: Requirement Coverage, Task Completeness, Dependency Correctness, Key Links Planned, Scope Sanity, and Verification Derivation.
Early Issue Detection: Identifies blockers and warnings related to missing elements, incorrect dependencies, scope creep, and unlinked components.
Use Case: Before initiating a complex development sprint, run this Skill to ensure all planned tasks are well-defined, dependencies are correctly set up, and the scope is manageable, thereby avoiding costly rework later.

Quick Start

Use the plan-checker skill to validate the plan file located at .hxsk/phases/1/01-PLAN.md.

Frequently Asked Questions about plan-checker

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

FAQPage Schema

How do I validate a development plan before execution?▼

To validate a development plan before execution, check your PLAN.md against six critical dimensions: requirement coverage, task completeness, dependency correctness, planned key links, scope sanity, and verification derivation to ensure readiness.

What is plan validation in agentic workflows?▼

Plan validation in agentic workflows is a quality gate process that prevents execution failures by rigorously checking PLAN.md files for missing elements, incorrect dependencies, scope creep, and unlinked components before the sprint starts.

How do I check dependency correctness and task completeness in a project plan?▼

You can check dependency correctness and task completeness by validating the plan file to identify blockers and warnings related to missing elements, incorrect dependencies, and improperly defined tasks before initiating execution.

Does plan validation help prevent scope creep in complex development sprints?▼

Yes, plan validation prevents scope creep by applying a scope sanity check to your PLAN.md, ensuring all planned tasks are well-defined, dependencies are correctly set up, and the overall scope remains manageable for the sprint.

When do I need to run a plan file validation check?▼

You need to run a plan file validation check before initiating a complex development sprint to ensure all planned tasks are well-defined, dependencies are set up correctly, and scope is manageable, thereby avoiding costly rework later.

What are the limitations of relying solely on automated plan validation?▼

Automated plan validation focuses strictly on six structural dimensions of a PLAN.md file, meaning it verifies requirement coverage, task completeness, dependency correctness, key links, scope sanity, and verification derivation, but does not assess the subjective technical quality of the planned implementation.