bmad-sprint-planning

Run the sprint planning flow, which parses Epic and Story headings from your epic Markdown files and writes a sprint-status.yaml with backlog defaults. Stories that already have files on disk are floored at ready-for-dev, and existing statuses are preserved, never downgraded.

Use the readiness intent, which inventories planning artifacts like PRDs, specs, architecture, and epics, then returns a PASS, CONCERNS, or FAIL verdict. It checks that requirements trace into stories and that no story depends on decisions nothing records.

Stories use backlog, ready-for-dev, in-progress, review, and done; epics use backlog, in-progress, and done; retrospectives use optional or done. Legacy v6 values like drafted and contexted are normalized to ready-for-dev and in-progress automatically.

Yes, the fix flow validates the file, gathers evidence from epic files, story files, and git history, proposes corrected statuses for your confirmation, then regenerates a pristine file with the script's --fresh and --set options.

Yes, headless mode runs the readiness gate and generates tracking without asking questions, ending with a JSON response containing status, intent, and gate verdict. Ambiguities that would require user input halt with a blocked status instead of guessing.