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
- 01Check spec.md required sections
- 02Assess plan.md executability
- 03Compare data-model.md entities with the spec
- 04Check API contract coverage
- 05Assess constitution compliance
- 06Report GREEN, YELLOW, or RED
Use cases
- 01Validate artifacts after /speckit.plan
- 02Find gaps before generating tasks
- 03Review entity and contract consistency
- 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-validateAfter installing, type/planning-validatein Claude Code to confirm it loaded.
Bundled filesscripts/validate.sh
Details
From the project READMEplanning-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
| Code | Status | Meaning |
|---|---|---|
| 0 | GREEN | All checks pass |
| 1 | YELLOW | Warnings present |
| 2 | RED | Blockers present |
| 3 | Error | Required files missing |
Checks Performed
spec.md Checks
- File exists and is readable
- Summary section present with content
- User Stories section present with at least one story
- Functional Requirements section present with FR-XXX items
- Success Criteria section present
plan.md Checks
- File exists and is readable
- Technical Context section present
- Project Structure section present
- Constitution Check section present (unless skipped)
- Gate Result shows PASS status
data-model.md Checks (if exists)
- Entities section present
- At least one entity defined
- Entity names are consistent with spec.md terminology
contracts/ Checks (if exists)
- At least one contract file present
- Contract files are valid markdown
- Contract endpoints match spec.md requirements
constitution.md Checks (if exists)
- Plan.md references constitution principles
- 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:
- Review the specific blockers or warnings listed
- Update the affected artifacts to address issues
- Re-run
/speckit.planto regenerate plan.md - Run
planning-validateagain to verify fixes