By name: spec-plan description: Execute implementation planning workflow to generate design artifacts (research.md, data-model.md, contracts/, quickstart.md). Use when user says "/spec-plan", "create a plan", "plan the implementation" after /spec-specify or /spec-clarify.
Spec-Plan
Generate implementation plan and design artifacts.
Prerequisites: Feature spec must exist.
Workflow
- Setup - Run
.specify/scripts/bash/setup-plan.sh --json - Load context - Read spec.md and constitution.md
- Fill plan template - Technical context, constitution check
- Phase 0: Research - Generate research.md (resolve NEEDS CLARIFICATION)
- Phase 1: Design - Generate data-model.md, contracts/, quickstart.md
- Update agent context - Run
.specify/scripts/bash/update-agent-context.sh - Report - Output plan path and artifacts
Script Usage
.specify/scripts/bash/setup-plan.sh --json
Output: {"FEATURE_SPEC":"...","IMPL_PLAN":"...","SPECS_DIR":"...","BRANCH":"..."}
Plan Template Sections
Technical Context
**Language/Version**: Python 3.11
**Primary Dependencies**: FastAPI, SQLAlchemy
**Storage**: PostgreSQL
**Testing**: pytest
**Target Platform**: Linux server
**Project Type**: web
Constitution Check
- Validate against
.specify/memory/constitution.md - ERROR if violations unjustified
Generated Artifacts
| File | Purpose |
|---|---|
plan.md |
Technical context and structure |
research.md |
Decisions and alternatives |
data-model.md |
Entities and relationships |
contracts/ |
API specifications |
quickstart.md |
Integration scenarios |
Phase 0: Research
For each NEEDS CLARIFICATION:
- Research the unknown
- Document decision and rationale
- List alternatives considered
Phase 1: Design
- Extract entities →
data-model.md - Generate API contracts →
contracts/ - Create test scenarios →
quickstart.md - Update agent context
Next Steps
After /spec-plan:
/spec-tasks- Generate task list/spec-checklist- Create validation checklist