| name | planning |
| description | Open an iteration — set the goal, pull prioritized work in against capacity, and leave the board reflecting the plan. |
| disable-model-invocation | true |
Iteration planning
Open the next iteration on the company board. Preset and board values come from docs/agents/board.md; under Kanban (no iterations) this ritual reduces to ordering the Ready column and stops there.
1. Close the loop
Look at the ending iteration before opening the new one: items not Done either carry over (re-justified, not by default) or return to Backlog. Note the planned-vs-delivered ratio — it calibrates today's capacity. Carry-over that keeps recurring is a /retro topic, not a planning fix.
2. Set the goal
One sentence, outcome-shaped: "By the end, users can X." Draft it from the top of the backlog and the active epics, then confirm with the user. Scrumban: a theme instead of a goal. A goal that just lists the tickets is a smell — say so and propose the outcome behind them.
3. Pull the work
Walk the prioritized backlog top-down with the user, pulling items into the iteration until capacity is reached. Capacity = what was actually delivered the last 2–3 iterations, minus known absences — not optimism. Every pulled item must be Ready: labelled, sized, unblocked, and inside an epic if it belongs to one. An item that fails the bar goes to /refinement, not into the iteration.
4. Commit the board
Via the board skill: set each pulled item's Iteration field and Status = Ready. The plan lives on the board, not in the chat.
Done when: the iteration has a recorded goal (in the iteration name or a pinned issue), every pulled item carries the iteration + Ready status, and the user has confirmed the set. Close by restating goal, item count, and capacity basis in three lines.
