Development Workflow¶
Build software from idea to production in 7 phases.
Overview¶
graph LR
S["/0-start"] --> B["/1-bootstrap"]
B --> P["/2-plan"]
P --> BU["/3-build"]
BU --> R["/4-review"]
R --> D["/5-deploy"]
D --> O["/6-operate"]
Phases¶
| Phase | Command | Orchestrator | What happens |
|---|---|---|---|
| 0. Start | /0-start |
— | See the workflow, validate readiness |
| 1. Bootstrap | /1-bootstrap |
— | Scaffold project structure |
| 2. Plan | /2-plan |
conceptual | Research, architecture, specs |
| 3. Build | /3-build |
— | Implementation with learning capture |
| 4. Review | /4-review |
implementation | 6 parallel code reviewers |
| 5. Deploy | /5-deploy |
deployment | Pre-deploy verification |
| 6. Operate | /6-operate |
bugfix, incident | Production issue handling |
When to use¶
Use the development workflow when you're writing code: APIs, web apps, services, libraries, CLI tools.
Typical flow¶
1. Create PRD.md with your vision
2. /1-bootstrap typescript-api my-project
3. /2-plan "Implement core features from PRD"
4. Write code based on the plan
5. /4-review
6. Fix issues from the review
7. /5-deploy
8. Deploy to production
Key features¶
- Automatic knowledge capture:
/journalrecords decisions during development - 6 parallel reviewers: security, TypeScript quality, race conditions, complexity, performance, patterns
- Security hooks: secret scanning and security lint on every write
- Learning loop: solutions compound over time