Agent skill · product strategy · aj-geddes
bmad-correct-course
CROSS-PHASE mid-stream scope correction. Re-enters planning when requirements, features, architecture, or constraints change after planning has started. Re-shards affected epics/stories, re-sequences sprint-status.yaml, appends rationale to decision-log.md. Routes to bmad-epics-and-stories, bmad-sprint-planning, or bmad-parallel-plan as needed. Changes the PLAN, never code. Use when: "we need to change course", "scope has changed", "new requirement came in", "we're dropping feature X", "we need to pivot", "re-plan after the change", "requirements changed mid-sprint", "correct course", "architecture changed", "re-scope the backlog", "update epics after feedback", "cancel story X", "add epic for Y", "change the plan", "we got new constraints", or when stories are split/merged/reordered due to a decision not in the original plan. Produces: updated epics.md (affected only), revised/new story files, updated sprint-status.yaml, new decision-log.md entry. NEVER writes code or runs tests.
Why this skill is useful
Provides a structured workflow for mid-stream planning changes, including specific file manipulations and routing directives that the AI wouldn't reliably generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-06-20. 471 stars on the source repository.
What this skill does
BMAD Correct Course Role: Cross-phase re-entry point for mid-stream planning changes. When reality diverges from the plan — a stakeholder pivots, a constraint surfaces, a feature is cut — this skill re-enters the planning phase, makes the minimum-necessary plan changes, and routes forward to the appropriate downstream skill. It changes the plan, never the code. Persona flavor: Mary (Analyst) surfaces the impact; John (PM) scopes the delta; Winston (Architect) re-shards affected epics. Lightweight flavor only — this is a workflow. --- Scope Law (read first) This skill PLANS. It NEVER writes application code, runs tests, lints, checks coverage, builds, or reviews diffs. If tempted to "fix the code" or "run the suite" — STOP. Plan the change and hand it off. The latest artifact this skill may produce is a story file marked ready-for-dev, an updated sprint-status.yaml, or a routing directive to a downstream planning skill. --- When to Use This Skill Trigger when ANY of the following is true: A requirement, feature, or constraint has changed after any planning artifact (PRD, architecture, epics.md, or stories) was produced. Stories need to be added, dropped, split, merged, or re-scoped for reasons not captured in the existing plan. The architecture changed in a way that invalidates Owned File/Module Scope declarations in existing stories. The user wants to document a mid-stream decision in decision-log.md before proceeding. --- Inputs (load these first) File Why ------ ----- bmad-output/project-context.md Project constitution — load every run bmad-output/decision-log.md Threaded decisions; append here bmad-output/epics.md Existing epic map to diff against bmad-output/prd.md Source of truth for requirements bmad-output/architecture.md Tech boundaries (if architecture changed) bmad-output/sprint-status.yaml Current sequencing state bmad-output/stories/.story.md In-flight and backlog stories Output folder default: bmad-output/. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/bmad-correct-course