>
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
| 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
You Might Also Like
Related Skills

fix
Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.
facebook
frontend-testing
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
langgenius
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
langgenius
code-reviewer
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
google-gemini
session-logs
Search and analyze your own session logs (older/parent conversations) using jq.
moltbot

