Software Development
From requirements to production with TDD, code review, and compliance.
Overview
Software development is Datarim's original and most natural domain. The pipeline maps directly to structured development practices: gather requirements, plan architecture, implement with TDD, verify through quality gates, and reflect on what was learned. Every stage has a responsible agent, and complexity routing ensures that a one-line fix doesn't go through the same ceremony as a new authentication system.
Example: Add JWT Authentication to an API
A backend team needs to add JWT-based authentication to their REST API. The task involves middleware, a token service, login endpoints, and comprehensive tests — a clear L3 feature.
Pipeline Walkthrough
| Stage | What happens |
|---|---|
| /dr-init | Assess complexity (L3), create task TASK-0012 |
| /dr-prd | Define auth requirements: token format, expiration, refresh flow, protected routes |
| /dr-plan | Break into phases: middleware, token service, login endpoint, tests |
| /dr-design | Consilium panel: Architect + Security evaluate JWT vs session tokens |
| /dr-do | TDD implementation: write tests first, then code, one method at a time |
| /dr-qa | Verify: PRD alignment, security review, test coverage, OWASP checks |
| /dr-archive (Step 0.5) | Note: refresh token rotation was underestimated in planning |
| /dr-archive | Archive task, update backlog |
Key Benefits
- TDD by default — the Developer agent writes tests before code, catching regressions early and producing self-documenting APIs
- Security baked in — the Security agent participates in design reviews, and OWASP checks are part of QA, not an afterthought
- Architectural consistency — the Architect agent ensures every feature aligns with existing patterns recorded in systemPatterns.md
- Automatic knowledge capture — reflections and archived tasks build an institutional memory that informs future planning
Relevant Agents
Which agents are most active in this use case:
- Developer — TDD implementation, one method at a time
- Architect — system design and pattern alignment
- Reviewer — code review and security verification
- Security — auth patterns, input validation, OWASP compliance
- Tester — platform QA and integration testing
Complexity Routing
How complexity levels apply to software development:
- L1 — Fix a typo in an error message, update a dependency version
- L2 — Add a new API endpoint with validation and tests
- L3 — Implement JWT authentication with middleware, token service, and security review
- L4 — Migrate from monolith to microservices with phased rollout and zero-downtime deployment