Weft.
If the warp is the plan, the weft is the doing. Individual tasks moving across columns — one thread at a time, row by row, until the fabric is done.
What a task carries
- Title. A short, specific name. “Fix flaky CI tests” beats “CI stuff”.
- Description. Optional, Markdown. Context your future self (or AI) will thank you for.
- Priority. How urgent, not how important. Most tasks are medium.
- Estimate. Optional, in minutes. Honest guesses, not story points.
- Due date. Optional, a hard stop.
- Column. Where on the board it lives right now.
- Sprint. Optional attachment — is this task in the current sprint, or waiting for the next one?
How a task crosses the loom
A task starts in Backlog (or wherever you place it). When you pick it up, you move it to Todo or directly to Doing — the column with semantic="doing" — which starts its cycle time. When you ship it, you move it to Done, which records the completion timestamp. That pair is enough to compute honest cycle-time numbers later.
Why Weft doesn't have subtasks
Subtasks usually signal a task that wants to be a sprint, or a task that wants to be smaller. Either way, the answer is to split it into separate tasks on the board — Scrumban works on individual shippable units, not hierarchies.