The project board is where discovery turns into durable delivery work.
Workflow states
The current board flow is:
- Todo
- Doing
- Checking
- Reviewing
- Done
Each lane should represent a real change in delivery state, not just a cosmetic move.
How to use the board well
Keep tickets small enough that one person can understand the goal, complete the checklist, and prove the result without needing a second planning cycle.
Packet-backed execution
When a ticket moves into packet-backed execution, the extension can create a linked packet file in the repository. That file becomes the shared implementation surface for notes, staged checklist work, and sync back into SwarmCraft.
For a customer setup session where SwarmCraft should prepare packets and run the board from the terminal, use Run one-shot with the CLI. The CLI still uses the board as the source of truth.
Keep movement honest
Move tickets when the work actually changed state. SwarmCraft is more useful when the board reflects reality instead of optimism.