Project Board - Task Tracking
This skill manages the project's feature board. The board lives in board.md.
Before Starting Work
Always read board.md first to understand:
- •What's already done
- •What's in progress (don't duplicate work)
- •What's prioritized next
Board Structure
Tasks are organized in columns by status:
| Status | Meaning |
|---|---|
done | Completed and working |
in-progress | Currently being worked on |
todo | Ready to start, prioritized |
backlog | Future work, not yet prioritized |
Priority Levels
| Priority | Meaning |
|---|---|
P0 | Critical - must do next |
P1 | Important - high value |
P2 | Nice-to-have - lower priority |
Updating the Board
When starting a task
- •Move the task from
backlogortodotoin-progress - •Only one task should be
in-progressat a time per feature area
When completing a task
- •Move from
in-progresstodone - •Add completion date if significant
When discovering new work
- •Add to
backlogwith appropriate priority - •Include a brief description
Task Format
markdown
- [STATUS] P#: Task title - Brief description
Example:
markdown
- [todo] P1: Unit tests - Add pytest with coverage for all modules
Board Maintenance Rules
- •Keep it current: Update status as you work
- •One in-progress: Avoid too many concurrent tasks
- •Clear descriptions: Others should understand at a glance
- •No duplicates: Check before adding new tasks
- •Promote when ready: Move from backlog to todo when prioritized