mcpField
P
planning-validate

planning-validate

github.com/drillanTesting & quality362 installsUpdated 40w ago
Repository

About planning-validate

planning-validate is a skill that checks planning artifacts after /speckit.plan and before task generation. It assesses required sections, consistency, contracts, and constitution compliance, then reports GREEN, YELLOW, or RED status.

Key features

  1. 01Check spec.md required sections
  2. 02Assess plan.md executability
  3. 03Compare data-model.md entities with the spec
  4. 04Check API contract coverage
  5. 05Assess constitution compliance
  6. 06Report GREEN, YELLOW, or RED

Use cases

  1. 01Validate artifacts after /speckit.plan
  2. 02Find gaps before generating tasks
  3. 03Review entity and contract consistency
  4. 04Identify blockers in planning documents

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/drillan/speckit-gates --skill planning-validate

After installing, type/planning-validatein Claude Code to confirm it loaded.

Bundled filesscripts/validate.sh

Details

From the project README

planning-validate

Validates planning artifacts for quality and consistency after /speckit.plan completes.

Purpose

This skill automatically validates your planning artifacts to catch specification gaps before task generation. It checks:

  • spec.md completeness: All mandatory sections present with content
  • plan.md executability: Technical context, project structure, and constitution check completed
  • data-model.md consistency: Entities align with spec requirements (if exists)
  • Contract coverage: API contracts defined for required endpoints (if contracts/ exists)
  • Constitution compliance: Plan follows project constitution rules (if constitution.md exists)

Output

The skill outputs a Quality Assessment with:

  • GREEN: All checks pass - proceed to /speckit.tasks
  • YELLOW: Minor warnings - review but can proceed
  • RED: Blockers found - must resolve before proceeding

Usage

This skill runs automatically after /speckit.plan. You can also run it manually:

npx skills run planning-validate

Exit Codes

CodeStatusMeaning
0GREENAll checks pass
1YELLOWWarnings present
2REDBlockers present
3ErrorRequired files missing

Checks Performed

spec.md Checks
  1. File exists and is readable
  2. Summary section present with content
  3. User Stories section present with at least one story
  4. Functional Requirements section present with FR-XXX items
  5. Success Criteria section present
plan.md Checks
  1. File exists and is readable
  2. Technical Context section present
  3. Project Structure section present
  4. Constitution Check section present (unless skipped)
  5. Gate Result shows PASS status
data-model.md Checks (if exists)
  1. Entities section present
  2. At least one entity defined
  3. Entity names are consistent with spec.md terminology
contracts/ Checks (if exists)
  1. At least one contract file present
  2. Contract files are valid markdown
  3. Contract endpoints match spec.md requirements
constitution.md Checks (if exists)
  1. Plan.md references constitution principles
  2. No constitution violations in Gate Result

Blocker Examples

  • "spec.md: Missing User Stories section"
  • "plan.md: Constitution Check section shows FAIL status"
  • "data-model.md: Entity 'UserAccount' not referenced in spec.md"

Recommendations

After receiving a RED or YELLOW status:

  1. Review the specific blockers or warnings listed
  2. Update the affected artifacts to address issues
  3. Re-run /speckit.plan to regenerate plan.md
  4. Run planning-validate again to verify fixes

Comments

Markdown supported