rcode-sprint-planninglisted

@.rcode/references/karpathy-guidelines.md ## Overview Generate or update a sprint plan that sequences stories for dev execution. ## Workflow Follow the instructions in ./workflow.md. ## Output Format - Output: sprint-status.yaml (path from {status_file}, per workflow.md step 4) — an epic/story status tracker, NOT a SPRINT.md - Fixed structure: generated/last_updated/project metadata + development_status (epic -> stories -> retrospective, ordered) - Distinct from `/rcode-sprint-planning` the slash command (`rcode/workflows/sprint-planning.md`), which writes a SPRINT.md via a separate in-line flow - Stories ranked by priority from epics.md - Leave 20% capacity buffer - Do NOT commit to stories without explicit owners - Sprint Goal must be one verifiable sentence — if it cannot be verified at sprint end without interpretation, rewrite it - `Assumptions` block required: list capacity assumptions, any known blockers assumed absent, any dependencies assumed resolved ## Examples ### Happy Path **Input:** "Plan the next 2-week sprint" **Expected behavior:** Read epics.md, ask team capacity, select stories fitting capacity with 20% buffer, assign owners, produce sprint file. ### Edge Case: No Capacity Info **Input:** "Plan the sprint" **Expected behavior:** Ask: "How many devs, any PTO, any known meetings? I need capacity numbers before committing to stories." ### Negative Example: Fabricated Capacity **Input:** "Plan the sprint" (no prior capacity info, no `mode: yolo`, no