BMAD Course Corrector
Productivityby AgentBox TeamPublished April 15, 2026
55Sign in to star this agent
0Sign in to follow AgentBox Team
620runs
Try BMAD Course Corrector
Pre-computed resultsInput
Sprint is 80% through but only 40% stories done
Description
Mid-sprint course correction agent following the BMAD correct-course workflow. Assesses blockers, re-estimates remaining work, proposes scope adjustments, and updates sprint status with risk mitigation.
Use in your project
$ agentbox pull bmad-course-corrector
$ agentbox bmad-course-corrector
$ agentbox mcp serve --agent bmad-course-corrector
Works with Claude Code, Cursor, VS Code, and any MCP client.
Sample I/O
Input
Sprint 6 is at day 8 of 10. Story 6-3 (Payment Integration) is blocked by a third-party API outage. Stories 6-4 and 6-5 depend on 6-3. What do we do?
Output
## Course Correction — Sprint 6\n\n### Current State\n- Day 8/10 | 3 stories done, 2 blocked, 1 in-progress\n- Blocker: Stripe sandbox API outage (external)\n- Impact: Stories 6-3, 6-4, 6-5 all blocked\n\n### Options\n| Option | Impact | Risk |\n|--------|--------|------|\n| A: Wait for API recovery | 0 scope change | High: may miss sprint |\n| B: Mock Stripe, continue | Full scope | Medium: integration debt |\n| C: Descope 6-5, extend 6-3/6-4 | -1 story | Low: clean delivery |\n\n### Recommendation: Option B + C hybrid\n1. Mock Stripe SDK for 6-3 unit tests (unblock dev)\n2. Move 6-5 to Sprint 7 backlog (reduce pressure)\n3. Add spike story: "Verify Stripe integration" for Sprint 7 day 1\n\n**Revised Sprint**: 5/6 stories (83%) — acceptable given external blocker
bmadcourse-correctionsdlcrisk-management