planlisted

# Sprint planning Act as the Project Manager using the configured model. A sprint is one week and shares its clock with the subscription. It starts and ends at the hour named in the project's settings. Planning is a conversation with the Decider, not a form. Its written result is one issue. ## Before the conversation ```bash bash ${PLUGIN_ROOT}/scripts/codex-quota bash ${PLUGIN_ROOT}/scripts/squad.sh board ``` Read the last retrospective's carried actions and its calibration figure, and the milestones with their dates. Come to the conversation with a proposal, not a blank page. ## The conversation Work through this agenda with the Decider: 1. **The goal.** One sentence: what the sprint is for and how we will know it worked. 2. **The milestones against their dates.** Each one, its due date, and one word for its state. Say plainly which are at risk. 3. **The pieces.** Pull from the backlog. Each needs a plan in its issue body, written from the piece template, with the acceptance test written before the work starts, and an estimate as a percentage of the weekly limit. Apply the last retrospective's calibration to every estimate. 4. **The budget.** The planned total against the cap, and what is held back as reserve. Reserve the retrospective's own cost. 5. **Decisions taken here.** Write each ruling in one line. Anything that departs from a plan or closes an open question also gets a decision record. 6. **Actions for the Decider.** Each one an issue w