bmad-sprint-status

To summarize sprint status and surface risks, aggregate sprint-state data from stories, epics, and retrospectives. The tool detects in-progress items without dependencies, overdue updates, and orphaned stories, then suggests corrective actions to keep the sprint on track.

Tracking epic and story progress across statuses like backlog, ready-for-dev, in-progress, review, and done requires aggregating sprint-state files. This approach automatically presents a clear health snapshot and detects risks such as overdue updates or orphaned stories.

To get next actionable step recommendations for ongoing sprints, analyze the current sprint status data. The workflow evaluates stories, epics, and retrospectives to propose a concrete next-step action that keeps the sprint on track.

Yes, you can detect orphaned stories and overdue updates in your sprint workflow. By automatically aggregating sprint-state data, the system identifies these specific risks and suggests corrective actions to resolve them.

Yes, you need project context and the bmad tooling to resolve customization blocks and load persistent facts during activation. These dependencies are required to properly summarize sprint status and surface risks.

Your sprint status summary shows risks for in-progress items without dependencies because the workflow automatically detects them. Identifying these items helps surface potential issues and suggests corrective actions to maintain sprint health.