planning-validate

/speckit.plan

Purpose

• 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

• GREEN: All checks pass - proceed to

  /speckit.tasks

• YELLOW: Minor warnings - review but can proceed
• RED: Blockers found - must resolve before proceeding

Usage

/speckit.plan

npx skills run planning-validate

Exit Codes

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

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