bmad-sprint-planning

Sprint planning automation infers story status by checking for the presence of story markdown files. It builds a complete status structure by scanning epic files and preserves any advanced existing statuses from a prior sprint-status.yaml across re-runs.

Story status detection works by checking whether corresponding story markdown files exist. If a prior sprint-status.yaml exists, it preserves more advanced states and applies legal state transitions to maintain accurate sprint tracking.

Yes, YAML frontmatter-driven activation is required. The system uses frontmatter to resolve customizations, load configurations, and perform full epic discovery, including handling sharded epic layouts during the parsing process.

Yes, this Python 3-based automation tool loads all epic markdown files to build an ordered status structure. It generates a standardized sprint-status.yaml output suitable for ongoing agile sprint management and re-runs.

When re-running sprint planning, the tool preserves any more advanced existing statuses from a prior sprint-status.yaml. It validates legal state transitions and updates the inventory while maintaining previously tracked story progress.

Yes, full epic discovery includes support for sharded layouts. The tool scans all referenced markdown shards to extract epic and story identifiers, ensuring complete inventory generation before writing the final sprint-status.yaml.