Overview
Spec Workflows#
CafeKit Spec follows a clear spec-driven command chain for planning, implementation, verification, and review.
Command Chain#
/spec-init
Initialize Spec
Create initial spec file with basic information
/spec-requirements
Analyze Requirements
Create EARS format requirements from PRD
/spec-design
Technical Design
Create technical design document
/spec-tasks
Break Down Tasks
Decompose into implementable tasks
/code
Implement
Implement from approved task list
/test
Validate
Run tests and analyze failures
/review
Review
Review correctness, security, and regressions
/spec-status
Check Status
View current spec phase and approvals
Syntactic Differences#
| Platform | Syntax |
|---|---|
| Claude Code | /spec-init, /spec-requirements, /spec-design, /spec-tasks, /code, /test, /review, /spec-status |
| Antigravity | /spec-init, /spec-requirements, /spec-design, /spec-tasks, /code, /test, /review, /spec-status |
SDD Process#
/spec-init -> /spec-requirements -> /spec-design -> /spec-tasks -> /code -> /test -> /review
|
+--> /spec-status (view current phase anytime)
When to Use Spec Workflows?#
Use when:#
- Developing complex new features
- Need clear technical documentation
- Team collaboration, need alignment
- Refactoring large codebase
Not needed when:#
- Simple bug fixes
- Small changes (1-2 lines of code)
- Hotfix production
Generated Files#
Core files generated by the spec phases:
.specs/
└── [feature-name]/
├── spec.json # Phase + approval status metadata
├── requirements.md # Requirements input/output
├── research.md # Discovery notes (if needed)
├── design.md # Technical design (from spec-design)
└── tasks.md # Task breakdown (from spec-tasks)
Real Examples#
See complete examples: