Work Breakdown
Key Capabilities
- Task Identification — Identify discrete, implementable work units from high-level requirements
- Dependency Analysis — Determine task order, relationships, and blocking dependencies
- Scope Definition — Create clear, bounded task descriptions with acceptance criteria
- Phase Organization — Group related tasks into logical implementation phases
Approach
1. Read and Understand Requirements
- Review the complete requirements document
- Understand the full scope and all success criteria
- Identify major components and subsystems affected
- Note security requirements and constraints
2. Identify System Components
- What parts of the codebase are affected?
- Which APIs, services, databases, UIs need changes?
- What external systems or dependencies are involved?
- Are multiple platforms affected (web, desktop, mobile, CLI)?
3. Break into Phases
Organize work into logical phases:
Phase 1: Architecture & Design
- Design system architecture and data models
- Create sequence diagrams, data flow diagrams
- Define API contracts and interfaces
- Security threat modeling (if applicable)
Phase 2: Implementation
- Core functionality development
- Database schema changes
- API endpoint creation
- UI component development
- Integration work
Phase 3: Testing
- Unit test development
- Integration test development
- End-to-end test scenarios
- Security testing (if applicable)
- Cross-platform verification
Phase 4: Documentation & Deployment
- User documentation
- API documentation
- Deployment procedures
- Migration scripts (if needed)
4. Define Individual Tasks
Each task should be:
- Right-sized: Completable in 2-8 hours (not days)
- Independent: Can be worked on without blocking on other incomplete tasks (except explicit dependencies)
- Testable: Has clear acceptance criteria that can be verified
- Specific: Clear description of what needs to be done
- Assigned: Identified role or team (e.g., "Backend team", "Security team", "QA")
5. Identify Dependencies
- What tasks must be completed before others can start?
- Are there parallel work streams that can proceed independently?
- What external dependencies exist (library updates, third-party APIs)?
- What approval gates are needed (security review, design review)?
6. Validate Completeness
- Do the tasks cover all functional requirements?
- Are non-functional requirements addressed (performance, security, reliability)?
- Is testing adequately planned?
- Is documentation included?
- Are verification commands/tests defined?
Task Template
Each task should follow this structure:
**Task X.Y**: [Concise task title]
- **Description**: [What needs to be done]
- **Team/Role**: [Backend | Frontend | Security | QA | DevOps]
- **Estimated Duration**: [2-8 hours]
- **Dependencies**: [Task IDs that must complete first, or "None"]
- **Deliverables**: [Specific outputs or changes]
- **Acceptance Criteria**: [How to verify completion]
Example
See examples/oauth-authentication.md for a complete worked example.
Best Practices
Do's
- ✅ Right-size tasks — 2-8 hours each, not full days or weeks
- ✅ Clear acceptance criteria — Must be testable and specific
- ✅ Assign appropriate teams — Match task to expertise
- ✅ Group related tasks — Organize into phases for clarity
- ✅ Identify dependencies — Make blocking relationships explicit
- ✅ Ensure completeness — All requirements covered, nothing orphaned
- ✅ Include verification — Testing and validation tasks for every feature
- ✅ Plan documentation — Technical and user docs are deliverables
- ✅ Consider security — Threat modeling and security testing included
- ✅ Think cross-platform — Bitwarden runs everywhere; plan for it
Don'ts
- ❌ Tasks too large — >1 day tasks should be broken down further
- ❌ Vague acceptance criteria — "Make it work" is not testable
- ❌ Circular dependencies — Tasks shouldn't block each other in loops
- ❌ Missing phases — Don't skip design, testing, or documentation
- ❌ Unclear deliverables — Every task should produce something concrete
- ❌ Ignoring platforms — Don't forget mobile, CLI, browser extensions
- ❌ Skipping security — Security tasks are not optional at Bitwarden
Output Format
Organize work breakdown in structured phases:
# Work Breakdown: [Feature Name]
## Summary
- **Total Estimated Duration**: X-Y hours
- **Number of Tasks**: N tasks across M phases
- **Teams Involved**: [List of teams]
- **Critical Path**: [Key dependencies or bottlenecks]
---
## Phase 1: [Phase Name]
**Goal**: [What this phase accomplishes]
**Task 1.1**: [Task title]
- **Description**: [What needs to be done]
- **Team/Role**: [Who does this]
- **Estimated Duration**: [Hours]
- **Dependencies**: [Prerequisites or "None"]
- **Deliverables**: [Concrete outputs]
- **Acceptance Criteria**: [How to verify]
**Task 1.2**: [Next task]
...
---
## Phase 2: [Phase Name]
...
---
## Verification
After all phases complete, verify:
- [ ] All functional requirements implemented
- [ ] All non-functional requirements met
- [ ] All security requirements addressed
- [ ] All tests passing (unit, integration, E2E)
- [ ] Documentation complete and accurate
- [ ] Deployment procedures tested
1---2name: work-breakdown3description: Work Breakdown4---56# Work Breakdown78## Key Capabilities9101. **Task Identification** — Identify discrete, implementable work units from high-level requirements112. **Dependency Analysis** — Determine task order, relationships, and blocking dependencies123. **Scope Definition** — Create clear, bounded task descriptions with acceptance criteria134. **Phase Organization** — Group related tasks into logical implementation phases1415## Approach1617### 1. Read and Understand Requirements1819- Review the complete requirements document20- Understand the full scope and all success criteria21- Identify major components and subsystems affected22- Note security requirements and constraints2324### 2. Identify System Components2526- What parts of the codebase are affected?27- Which APIs, services, databases, UIs need changes?28- What external systems or dependencies are involved?29- Are multiple platforms affected (web, desktop, mobile, CLI)?3031### 3. Break into Phases3233Organize work into logical phases:3435**Phase 1: Architecture & Design**3637- Design system architecture and data models38- Create sequence diagrams, data flow diagrams39- Define API contracts and interfaces40- Security threat modeling (if applicable)4142**Phase 2: Implementation**4344- Core functionality development45- Database schema changes46- API endpoint creation47- UI component development48- Integration work4950**Phase 3: Testing**5152- Unit test development53- Integration test development54- End-to-end test scenarios55- Security testing (if applicable)56- Cross-platform verification5758**Phase 4: Documentation & Deployment**5960- User documentation61- API documentation62- Deployment procedures63- Migration scripts (if needed)6465### 4. Define Individual Tasks6667Each task should be:6869- **Right-sized**: Completable in 2-8 hours (not days)70- **Independent**: Can be worked on without blocking on other incomplete tasks (except explicit dependencies)71- **Testable**: Has clear acceptance criteria that can be verified72- **Specific**: Clear description of what needs to be done73- **Assigned**: Identified role or team (e.g., "Backend team", "Security team", "QA")7475### 5. Identify Dependencies7677- What tasks must be completed before others can start?78- Are there parallel work streams that can proceed independently?79- What external dependencies exist (library updates, third-party APIs)?80- What approval gates are needed (security review, design review)?8182### 6. Validate Completeness8384- Do the tasks cover all functional requirements?85- Are non-functional requirements addressed (performance, security, reliability)?86- Is testing adequately planned?87- Is documentation included?88- Are verification commands/tests defined?8990## Task Template9192Each task should follow this structure:9394```markdown95**Task X.Y**: [Concise task title]9697- **Description**: [What needs to be done]98- **Team/Role**: [Backend | Frontend | Security | QA | DevOps]99- **Estimated Duration**: [2-8 hours]100- **Dependencies**: [Task IDs that must complete first, or "None"]101- **Deliverables**: [Specific outputs or changes]102- **Acceptance Criteria**: [How to verify completion]103```104105## Example106107See `examples/oauth-authentication.md` for a complete worked example.108109## Best Practices110111### Do's112113- ✅ **Right-size tasks** — 2-8 hours each, not full days or weeks114- ✅ **Clear acceptance criteria** — Must be testable and specific115- ✅ **Assign appropriate teams** — Match task to expertise116- ✅ **Group related tasks** — Organize into phases for clarity117- ✅ **Identify dependencies** — Make blocking relationships explicit118- ✅ **Ensure completeness** — All requirements covered, nothing orphaned119- ✅ **Include verification** — Testing and validation tasks for every feature120- ✅ **Plan documentation** — Technical and user docs are deliverables121- ✅ **Consider security** — Threat modeling and security testing included122- ✅ **Think cross-platform** — Bitwarden runs everywhere; plan for it123124### Don'ts125126- ❌ **Tasks too large** — >1 day tasks should be broken down further127- ❌ **Vague acceptance criteria** — "Make it work" is not testable128- ❌ **Circular dependencies** — Tasks shouldn't block each other in loops129- ❌ **Missing phases** — Don't skip design, testing, or documentation130- ❌ **Unclear deliverables** — Every task should produce something concrete131- ❌ **Ignoring platforms** — Don't forget mobile, CLI, browser extensions132- ❌ **Skipping security** — Security tasks are not optional at Bitwarden133134## Output Format135136Organize work breakdown in structured phases:137138```markdown139# Work Breakdown: [Feature Name]140141## Summary142143- **Total Estimated Duration**: X-Y hours144- **Number of Tasks**: N tasks across M phases145- **Teams Involved**: [List of teams]146- **Critical Path**: [Key dependencies or bottlenecks]147148---149150## Phase 1: [Phase Name]151152**Goal**: [What this phase accomplishes]153154**Task 1.1**: [Task title]155156- **Description**: [What needs to be done]157- **Team/Role**: [Who does this]158- **Estimated Duration**: [Hours]159- **Dependencies**: [Prerequisites or "None"]160- **Deliverables**: [Concrete outputs]161- **Acceptance Criteria**: [How to verify]162163**Task 1.2**: [Next task]164...165166---167168## Phase 2: [Phase Name]169170...171172---173174## Verification175176After all phases complete, verify:177178- [ ] All functional requirements implemented179- [ ] All non-functional requirements met180- [ ] All security requirements addressed181- [ ] All tests passing (unit, integration, E2E)182- [ ] Documentation complete and accurate183- [ ] Deployment procedures tested184```