bmad-sprint-run

To autonomously run an agile sprint, you need unattended story creation, implementation, quality gating, and stateful orchestration that drives all stories until they reach done or blocked states. This requires deterministic sequential execution and safe git operations.

Enforcing quality gates in automated sprint execution requires deterministic checks like typecheck and tests before accepting reviews, blocking progress on critical issues, and mandating review findings to exist. Stateful orchestration ensures these validations persist across workflow transitions.

Retry orchestration handles failed stories by applying a fixed retry budget and avoiding destructive git operations. This prevents wiping completed work while allowing the autonomous sprint execution to safely re-attempt failed implementations.

Yes, you can use state machine workflows to track sprint story transitions. Stateful orchestration persists progress using sprint state files, enforcing correct transitions through states like backlog, ready-for-dev, in-progress, review, done, or blocked across restarts.

Autonomous sprint execution blocks during code review when quality gate checks fail or critical issues are found. The orchestration requires review findings to exist and blocks progress to prevent advancing stories with unresolved critical defects.

Yes, you need a sprint-status.yaml file or similar persistent state tracking format to start autonomous story implementation. The workflow relies on these state files to persist progress, sequence stories, and enforce deterministic transitions across epics.