Workflows
Step-by-step guides for the most common development scenarios.
Getting Started
| Workflow | Best for | Time |
|---|---|---|
| Starting a New Project | First-time setup | 5 min |
| Adding a Feature | Daily development | 15-60 min |
| Fixing a Bug | Bug investigation | 10-30 min |
Quality & Review
| Workflow | Best for | Time |
|---|---|---|
| Code Review | Pre-merge review | 5-15 min |
| Shipping Code | Deploy pipeline | 5-10 min |
| Security Audit | Security assessment | 15-30 min |
| Writing Tests | TDD workflow | 10-30 min |
| QA Testing | Manual QA + E2E gen | 15-45 min |
Architecture & Design
| Workflow | Best for | Time |
|---|---|---|
| Architecture Decisions | ADRs + system design | 30-60 min |
| Frontend Development | Vue/TS/CSS work | 15-60 min |
| Refactoring | Code improvement | 15-45 min |
Intake & Triage
| Workflow | Best for | Time |
|---|---|---|
| Ticket Evaluation & Estimation | Sprint planning, triage | ~30s per ticket |
| Spec to Sprint Planning | End-to-end: spec analysis → tech review → sprint plan | 5-15 min |
| Ticket to Code | Developer: receive ticket → understand → plan → implement → ship | Varies |
| Spec → PR: Behind the Scenes | Deep-dive: see what every skill does between Confluence and a merged PR | 20 min read |
Operations
| Workflow | Best for | Time |
|---|---|---|
| Documentation | Docs maintenance | 10-20 min |
| Sprint Retrospective | Team reflection | 10-15 min |
| Agile / Scrum Workflow | Sprint goal, DoR/DoD, retro→action, spike governance | Per-sprint |
| Researching Libraries | Tech evaluation | 15-30 min |
| Maintaining Old Projects | Legacy codebases | 30-60 min |