```
**Prerequisites:** ποΈ Must have existing `plan.md` file
**Example:**
```bash
/implement user-auth-system
```
**β‘ What it creates:**
- β
`todo-list.md` with comprehensive execution plan
- π Continuous implementation flow
- π Progress tracking and updates
- π― Pattern reuse strategy
- π» Implementation artifacts and code
## π Project Structure
```
your-project/
βββ .sdd/ # SDD system configuration
β βββ config.json # Settings and preferences
β βββ guidelines.md # Development process guide
β βββ templates/ # Document templates
β β βββ spec-template.md
β β βββ plan-template.md
β β βββ tasks-template.md
β βββ utils.js # Helper utilities (optional)
βββ specs/ # All feature specifications
β βββ 00-overview.md # Project overview
β βββ index.md # Feature status dashboard
β βββ active/ # Features in development
β β βββ feat-001-user-auth/
β β β βββ spec.md # Requirements
β β β βββ plan.md # Technical plan
β β β βββ tasks.md # Implementation tasks
β β β βββ progress.md # Development tracking
β β βββ feat-002-photo-gallery/
β βββ completed/ # Delivered features
β βββ backlog/ # Future features
βββ src/ # Your actual code
βββ .cursor/ # Cursor configuration
β βββ commands/ # Command definitions
β β βββ specify.md # /specify command
β β βββ plan.md # /plan command
β β βββ tasks.md # /tasks command
β βββ rules/ # Minimal system rules
β βββ sdd-system.mdc # SDD overview (token-efficient)
βββ README.md # This file
```
## π§ Configuration
### Customizing Templates
Edit templates in `.sdd/templates/` to match your project needs:
```markdown
# Example customization in spec-template.md
## Project-Specific Section
- **Team Lead**: {{TEAM_LEAD}}
- **Sprint**: {{CURRENT_SPRINT}}
- **Epic**: {{EPIC_REFERENCE}}
```
### Adjusting Settings
Modify `.sdd/config.json` for your workflow:
```json
{
"settings": {
"defaultFeaturePrefix": "feat-",
"autoNumberFeatures": true,
"requireReviews": true,
"collaborationMode": true
},
"workflow": {
"phases": ["specify", "plan", "tasks", "implement", "review", "complete"]
}
}
```
## π― Example Workflow
> **See SDD in action! From idea to implementation in minutes.**
π¬ Scenario 1: Adding Feature to Existing App
### π‘ **Step 1: Start with a Feature Idea**
*"I want to add a user rating system to my existing e-commerce app"*
### π― **Step 2: Create the Specification**
```bash
/specify user-ratings Allow users to rate items on 1-5 scale with optional comments and display average ratings
```
**β¨ Result:** Creates comprehensive specification
```
π specs/active/feat-003-user-ratings/
βββ π spec.md # Complete requirements with user stories & acceptance criteria
```
### ποΈ **Step 3: Generate the Technical Plan**
```bash
/plan user-ratings
```
**π Result:** Creates detailed implementation strategy
```
π specs/active/feat-003-user-ratings/
βββ π spec.md
βββ ποΈ plan.md # Architecture, tech stack, database schema, APIs
```
### π **Step 4: Break Down into Tasks**
```bash
/tasks user-ratings
```
**π Result:** Creates actionable development roadmap
```
π specs/active/feat-003-user-ratings/
βββ π spec.md
βββ ποΈ plan.md
βββ β
tasks.md # Prioritized tasks with dependencies & estimates
```
### π― **Step 5: Start Development**
Follow the tasks in priority order, updating `progress.md` as you go:
```markdown
## π Current Status: In Progress
- [x] Database schema design β
- [x] API endpoints β
- [x] Frontend rating component β
- [ ] π Integration testing (In Progress)
- [ ] β³ Performance optimization (Pending)
```
**π Result:** Feature delivered on time, on spec, with no surprises!
π Scenario 2: PRD-Based Development
### π **Step 1: Start with Requirements Document**
*"We have a PRD for a real-time chat system for our SaaS platform"*
### π **Step 2: Research External Solutions**
```bash
/research chat-system WebSocket vs Socket.io vs Pusher for real-time messaging in SaaS
```
**β¨ Result:** Creates comprehensive research
```
π specs/active/chat-system/
βββ π research.md # Competitor analysis, technology comparison, best practices
```
### π― **Step 3: Create Specification**
```bash
/specify chat-system Real-time messaging with typing indicators and file sharing
```
**π Result:** Creates detailed specification
```
π specs/active/chat-system/
βββ π research.md
βββ π spec.md # Requirements informed by research findings
```
### ποΈ **Step 4: Generate Technical Plan**
```bash
/plan chat-system
```
**π Result:** Creates implementation strategy
```
π specs/active/chat-system/
βββ π research.md
βββ π spec.md
βββ ποΈ plan.md # Architecture using researched technologies
```
### π **Step 5: Break Down Tasks**
```bash
/tasks chat-system
```
### β‘ **Step 6: Execute Implementation**
```bash
/implement chat-system
```
**π Result:** Chat system built using researched best practices and proven patterns!
---
### π **From Chaos to Clarity in 4 Commands**
| Before SDD | After SDD |
|------------|-----------|
| π΅ Unclear requirements | π― Crystal clear specifications |
| π€ Guessing architecture | ποΈ Well-planned technical design |
| π Vague development tasks | β
Actionable roadmap with estimates |
| π Endless scope changes | π― Focused delivery with minimal rework |
## π‘ Best Practices
### π **Pro Tips for SDD Mastery**
### π― **For Specifications (`/specify`)**
**π¨ Think User-First**
- Be specific about user needs & business value
- Include edge cases & error scenarios
- Define measurable success criteria
- Focus on "what" and "why", not "how"
**β¨ Pro Tip:** *Ask "What problem are we solving?" before writing code*
---
### ποΈ **For Plans (`/plan`)**
**π Design for Success**
- Justify technology choices based on requirements
- Consider scalability & future growth
- Address security & performance early
- Plan for testing & deployment from day one
**β¨ Pro Tip:** *Architecture decisions made now save hours later*
---
### π **For Tasks (`/tasks`)**
**β‘ Execute with Precision**
- Keep tasks small (1-2 days max)
- Define clear dependencies between tasks
- Include testing tasks for each feature
- Estimate effort realistically
**β¨ Pro Tip:** *Small tasks = big wins and faster feedback loops*
### π― **The SDD Golden Rules**
| Rule | Why It Matters | Impact |
|------|----------------|---------|
| π **Spec before code** | Prevents scope creep | π 20% faster delivery |
| ποΈ **Plan before build** | Reduces technical debt | π§ 50% fewer refactors |
| β
**Tasks before work** | Improves team coordination | π€ Better collaboration |
## π€ Team Collaboration
### Multi-Developer Workflow
1. **Assign ownership** of specs, plans, and tasks
2. **Use progress.md** for status updates
3. **Review and iterate** on specifications
4. **Track dependencies** between features
### Status Tracking
Update feature status in `progress.md`:
```markdown
## Current Status: In Progress
- [x] Database schema design
- [x] API endpoints
- [ ] Frontend components (50% complete)
- [ ] Testing suite
```
### Code Reviews
Use `reviews.md` to track review feedback:
```markdown
## Review Comments
- Security: Add input validation (Fixed β
)
- Performance: Optimize database queries (In Progress)
- UI: Improve mobile responsiveness (Pending)
```
## π Troubleshooting
### Common Issues
**"Feature not found" error:**
- Check feature name spelling
- Ensure feature exists in `specs/active/`
**"Missing dependencies" error:**
- Run commands in order: `/specify` β `/plan` β `/tasks`
- Check that required files exist
**Template processing errors:**
- Verify template files exist in `.sdd/templates/`
- Check template syntax for variables
### Getting Help
1. **Check guidelines**: Read `.sdd/guidelines.md`
2. **Review examples**: Look at existing features in `specs/active/`
3. **Validate structure**: Ensure directory structure matches expected format
## π Advanced Usage
### Custom Commands
Extend the system by adding new command files to `.cursor/commands/`:
```markdown
# /review Command
Generate code review checklist based on specifications.
## Usage
```
/review [feature-name]
```
## Purpose
Create comprehensive code review checklist based on feature specification and plan.
```
### Integration with Tools
- **Git hooks**: Automatically update status on commits
- **CI/CD**: Validate implementations against specifications
- **Project management**: Sync with Jira, Linear, etc.
### Analytics
Track your SDD usage:
- Time savings from better planning
- Reduction in scope changes
- Quality improvements through structured approach
## π Benefits
### π **Transform Your Development Process**
### π **Measurable Improvements**
| Metric | Before SDD | After SDD | Improvement |
|--------|------------|-----------|-------------|
| β±οΈ **Development Time** | Baseline | Optimized | π **20% Faster** |
| π **Scope Changes** | Frequent | Minimal | π **80% Reduction** |
| π **Bugs in Production** | High | Low | π― **60% Fewer** |
| π€ **Team Alignment** | Poor | Excellent | β **95% Satisfaction** |
---
### π **Real-World Impact**
**π― For Developers:**
- β
Clear roadmap reduces decision fatigue
- π§ Less time spent guessing requirements
- π Faster implementation with better focus
- πͺ Higher confidence in deliverables
**π₯ For Teams:**
- π€ Improved communication & collaboration
- π Better project visibility for stakeholders
- π― Reduced rework and technical debt
- π Higher quality deliverables
### π° **ROI Calculator**
*Average 40-hour feature development:*
| Phase | Time Saved | Value |
|-------|-------------|--------|
| π Planning | 8 hours | $800 |
| π» Development | 6 hours | $600 |
| π Rework | 12 hours | $1200 |
| **π Total Savings** | **26 hours** | **$2600** |
---
## π **Ready to Transform Your Development Process?**
|
### π **Get Started**
```bash
git clone https://github.com/madebyaris/spec-kit-command-cursor.git
```
[π Read the docs](#-quick-start)
|
### β **Show Support**
Star this repo if SDD helps you!
[](https://github.com/madebyaris/spec-kit-command-cursor/stargazers)
|
### π€ **Contribute**
Help make SDD even better!
[π§ Submit a PR](https://github.com/madebyaris/spec-kit-command-cursor/pulls)
|
---
### π **Try Your First SDD Command Right Now!**
```bash
# π Start with lightweight 30-minute brief (most features)
/brief hello-world Create a simple hello world feature to test the SDD workflow
# ποΈ For complex features, use full SDD 2.0 workflow
/research payment-system β /specify β /plan β /tasks β /implement
```
**Made with β€οΈ by [Aris](https://github.com/madebyaris)**
[β¬οΈ Back to top](#-sdd-cursor-commands)