sprint-planninglisted

## Inputs - `state.json` → phase: backlog_created | retrospective - `backlog.json` → PBIs with status: refined ## Outputs - `sprint.json`: id, goal, type: development, status: planning - `backlog.json` → items[].sprint_id, implementer_id assigned (per-PBI review runs Developer-side inside pbi-pipeline as the Integrity stage; Sprint end adds only the audit-only `cross-review` ceremony). **Sprint PBI membership is derived from these `sprint_id` assignments** — `sprint.json` no longer carries a `pbi_ids` array (OD-4 single-source). - Oversized PBIs split into children (parent_pbi_id set) - `state.json` → phase: sprint_planning ## Preconditions - state.json phase: "backlog_created" or "retrospective" - backlog.json has ≥1 refined PBI - No active Sprint in progress ## PO Mode (po_mode: "agent") When `.scrum/config.json.po_mode == "agent"`, every PO-approval prompt in the numbered Steps below re-targets to the `product-owner` teammate per `../../rules/scrum-context.md` § PO seat resolution; the ceremony shape is unchanged. The "ask the user" points are re-targeted as follows: | Step | Phrase in human mode | Agent-mode override (kind, scope, defaults) | |---|---|---| | 1 | Uncommitted-file 3-way choice (commit now / stash / proceed anyway) | `kind=git_dirty`, `scope=sprint-N`, `options=[commit_now,stash,proceed_anyway]`. The full `git status` file list is included as payload. **PO default policy:** if every changed path lies inside a deliverable directory → `choice:commit_no