Development Plan & Tracking
← Back to Documentation Home
This section tracks current work, implementation roadmap, and detailed task planning.
📊 Current Work
Active task tracking with work-in-progress limits.
Current Status:
- Doing: Active implementation (WIP ≤ 2)
- Ready: Prioritized queue (next tasks)
- Blocked: Waiting on decisions or dependencies
- Done: Recently completed work
→ View Kanban
🗺️ Roadmap
High-level roadmap and milestone tracking.
Major Phases:
- Foundation - Core domain models and ports
- Timer Module - Scheduling and firing workflows
- Orchestration - Service call lifecycle
- Execution - External HTTP calls
- API Layer - REST endpoints
- Infrastructure - Persistence and messaging
→ View Project Plan
📝 Implementation Plans
Detailed task breakdowns for complex features:
Active Implementation Plans
Before Starting Work
- Check Kanban for current task priority
- Read relevant module design documentation
- Review related ADRs for architectural decisions
- Follow TDD workflow in Contributing Guide
During Development
- Update Kanban status as you progress (Ready → Doing → Done)
- Link commits to plan items (e.g.,
Refs: PL-##)
- Reference ADRs in code comments (e.g.,
[adr: ADR-0006])
Quality Gates
- Run tests:
bun run test --run
- Validate docs:
bun run docs:check && bun run docs:type-check
- Format code:
bun run format
- Type check:
bun run type-check
📌 Conventions
Task IDs
Plan items use PL-# format (e.g., PL-24, PL-4.6)
[Timer], [Orchestration], [Api], etc. - Module scope[infra] - Infrastructure/cross-cutting[adr: ADR-####] - Links to decision records[docs] - Documentation updates
Priority Levels
- P0 - Critical blockers
- P1 - High priority
- (no prefix) - Normal priority
🎯 Next Steps
Check the Kanban Ready queue for the next prioritized task to work on.