sprintlisted

# sprint — Turn ordered plan into issues someone can pick up The moment planning becomes commitment. Everything before this is a document that changes for free; an issue is a promise, and it is where a person's name goes. **One backlog item usually becomes several issues.** That decomposition is the work this skill does — not selection, which the backlog already settled by ordering. An item and an issue are different sizes, and pretending otherwise is how a plan looks precise while being wrong. Its output is **typed tracker issues**, because `spec <issue>` is where delivery starts. The type is not decoration: `spec` reads it to choose the shape of the spec it writes. ## Where it goes Into the **tracker**, not into a file. This skill writes no document: the issues it creates are the record, and a parallel markdown copy of them would be a second source of truth that drifts from the first. If the iteration is worth a retrospective, that belongs in `.work_logs/` via `worklog`, which is already the append-only record of what happened. ## Steps 1. Read the product backlog and the epics. **Take from the top.** The order already encodes value, risk, cost, and dependency; an iteration assembled by picking interesting items from further down silently overrides a decision someone already made. If the top item is genuinely wrong to start now, that is not a reason to skip it — it is a reason to re-groom. Go and change the order in `backlog`, with the reasoning recorded, then come