4.6 KiB
Tasks: [FEATURE/AREA_NAME]
Created: [YYYY-MM-DD]
Last Updated: [YYYY-MM-DD]
Sprint/Milestone: [IDENTIFIER]
Overview
Brief context for this task list and its relationship to plans/specs.
Task Categories
Tasks are organized by constitutional principle to ensure balanced development:
🏗️ Implementation Tasks (Principle 1: Code Quality)
-
[TASK-001] Task title
- Description: What needs to be done
- Acceptance: How to verify completion
- Estimate: [S/M/L/XL or hours]
- Dependencies: [Other task IDs]
- Quality checklist:
- Follows style guide (linter passes)
- Type hints added
- No code duplication
- Comments explain "why" not "what"
-
[TASK-002] Next task...
🧪 Testing Tasks (Principle 2: Testing Discipline)
-
[TEST-001] Write unit tests for [Component]
- Coverage target: ≥80% for new code
- Test scenarios:
- Happy path
- Edge case 1
- Edge case 2
- Error handling
- Estimate: [S/M/L/XL]
-
[TEST-002] Integration tests for [Feature]
- Scope: [Component interactions to validate]
- Performance target: <10s execution time
-
[TEST-003] Regression test for [Bug #X]
- Bug reference: [Link to issue]
- Reproduction steps: [Documented]
👤 User Experience Tasks (Principle 3: UX Consistency)
-
[UX-001] Design/implement [UI Component]
- Design system alignment: [Pattern/component to follow]
- Accessibility checklist:
- Keyboard navigable
- Screen reader compatible
- Color contrast WCAG AA
- Focus indicators visible
- Estimate: [S/M/L/XL]
-
[UX-002] Error message improvement for [Feature]
- Current message: [What users see now]
- Improved message: [Clear, actionable alternative]
- Context provided: [Where, why, what to do]
-
[UX-003] User documentation for [Feature]
- Target audience: [End users/API consumers/admins]
- Format: [README/Wiki/API docs/Tutorial]
⚡ Performance Tasks (Principle 4: Performance & Efficiency)
-
[PERF-001] Optimize [Operation/Query]
- Current performance: [Baseline metric]
- Target performance: [Goal metric]
- Approach: [Algorithm change/caching/indexing/etc]
- Estimate: [S/M/L/XL]
-
[PERF-002] Add performance benchmark for [Feature]
- Metric: [Response time/throughput/memory]
- Budget: [Threshold that triggers alert]
- CI integration: [How it blocks bad merges]
-
[PERF-003] Profile and fix [Bottleneck]
- Profiling tool: [Tool to use]
- Suspected issue: [Hypothesis]
- Verification: [How to confirm fix]
🔧 Infrastructure/DevOps Tasks
-
[INFRA-001] Setup [Tool/Service]
- Purpose: [Why this is needed]
- Configuration: [Key settings]
- Documentation: [Where to document setup]
-
[INFRA-002] CI/CD pipeline enhancement
- Addition: [What check/stage to add]
- Constitutional alignment: [Which principle this enforces]
📋 Technical Debt Tasks
-
[DEBT-001] Refactor [Component]
- Current problem: [What makes this debt]
- Proposed solution: [Refactoring approach]
- Impact: [What improves after fix]
- Estimate: [S/M/L/XL]
-
[DEBT-002] Update dependencies
- Packages: [List outdated packages]
- Risk assessment: [Breaking changes?]
- Testing plan: [How to verify upgrade]
Task Estimation Guide
- S (Small): <2 hours, single file, no dependencies
- M (Medium): 2-4 hours, multiple files, minor dependencies
- L (Large): 4-8 hours, multiple components, significant testing
- XL (X-Large): >8 hours, consider breaking down further
Completion Checklist
Before closing any task, verify:
- Code changes committed with clear message
- Tests written and passing (≥80% coverage for new code)
- Linter/type checker passing
- Documentation updated
- Code review completed
- Constitutional principles satisfied
- Deployed to staging/production
Blocked Tasks
Track tasks waiting on external dependencies:
- [TASK-XXX] Task title
- Blocked by: [Reason/dependency]
- Resolution needed: [Action to unblock]
- Owner of blocker: [Person/team]
Completed Tasks
Move completed tasks here with completion date:
- ✅ [TASK-000] Example completed task (2025-11-01)
Notes & Decisions
Document important decisions or context that affects multiple tasks:
- [2025-11-02] Decision about [topic]: [What was decided and why]