bmad-correct-course

Analyzes sprint change impact across PRD, epics, and architecture to produce a Sprint Change Proposal.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-correct-course-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-correct-course
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-correct-course-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a significant issue emerges mid-sprint, teams lack a structured way to assess its impact across planning artifacts and decide how to respond. This Skill guides a systematic change analysis and produces an actionable Sprint Change Proposal with clear handoff. ## Core Features & Use Cases - Impact Analysis: Loads PRD, epics, architecture, and UX documents to assess how a triggering issue affects each artifact. - Structured Checklist: Works through a six-section change navigation checklist covering trigger context, epic impact, artifact conflicts, and path-forward options. - Sprint Change Proposal: Generates a proposal document with issue summary, impact analysis, recommended approach, detailed edit proposals, and implementation handoff routing. - Use Case: A developer discovers the chosen authentication library cannot support a required 2FA feature. The Skill analyzes affected stories and architecture, drafts before/after edit proposals, and routes the approved change to the right agent. ## Quick Start Ask the AI to correct course and propose a sprint change for the issue you just discovered during implementation.

Frequently Asked Questions about bmad-correct-course

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle a major change request in the middle of a sprint?

Run the correct course workflow to analyze the triggering issue against your PRD, epics, and architecture documents. It produces a Sprint Change Proposal with impact analysis, a recommended path forward, and a handoff plan based on change scope.

What documents are required to assess sprint change impact?

The PRD and current epics are required; the workflow halts without them. Architecture, UX specifications, and technical specs are loaded if available, and the AGENTS.md project context block is read when present.

Can the workflow handle both small story edits and full replanning?

Yes. It classifies the change scope as minor, moderate, or major. Minor changes route to a developer agent, moderate ones to product owner and developer, and major ones escalate to product manager and architect for replanning.

What happens if the change trigger is unclear or evidence is missing?

The workflow halts and asks for specific details about what needs to change and why. The checklist requires concrete evidence such as error messages, stakeholder feedback, or technical constraints before impact analysis begins.

Does the sprint change proposal update sprint status tracking?

Yes. After user approval, the checklist updates sprint-status.yaml to reflect added, removed, or renumbered epics and stories, keeping the backlog consistent with the approved changes.