bmad-correct-course

Assess sprint change impact across PRD, epics, architecture, and UX documents to produce a sprint change proposal.

Updated Sep 4, 2026
One-click install
npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-correct-course-joao-victor-medeiros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/Joao-Victor-Medeiros/save-sc/tree/main/.agents/skills/bmad-correct-course
Command: npx skills add https://github.com/Joao-Victor-Medeiros/save-sc --skill bmad-correct-course-joao-victor-medeiros

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a significant issue emerges mid-sprint, teams lack a structured way to evaluate its impact across planning artifacts and decide how to respond. This Skill guides a systematic change analysis and produces a formal Sprint Change Proposal with clear handoff routing. ## Core Features & Use Cases - Impact Analysis Checklist: Works through an interactive checklist covering trigger context, epic impact, artifact conflicts (PRD, architecture, UX), and path-forward options. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, PRD sections, architecture, and UX specs, in incremental or batch review mode. - Scoped Handoff Routing: Classifies the change as Minor, Moderate, or Major and routes it to the Developer, Product Owner, or PM/Architect accordingly. - Use Case: During implementation you discover the chosen authentication approach cannot support a new 2FA requirement. Run this workflow to assess the impact on epics and the PRD, then generate an approved Sprint Change Proposal routed to the right role. ## Quick Start Ask the agent to correct course and propose a sprint change for the issue you just discovered during story 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 discovered during sprint execution?▼

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

What documents are required to run a sprint change impact analysis?▼

The PRD and current epics are required; the workflow halts if they cannot be found. Architecture, UX design, spec documents, and the repo's AGENTS.md context block are loaded when available, supporting both whole-file and sharded layouts.

What is included in a Sprint Change Proposal document?▼

The proposal contains an issue summary, epic and artifact impact analysis, a recommended approach (direct adjustment, rollback, or MVP review) with effort and risk estimates, detailed before/after edit proposals, and an implementation handoff plan.

Can I review proposed changes one at a time instead of all at once?▼

Yes, the workflow offers an Incremental mode where each edit proposal is presented individually for approve, edit, or skip decisions. A Batch mode presents all proposals together at the end if you prefer a single review.

When should I not use the correct course workflow?▼

It is designed for significant changes affecting project direction, not minor bug fixes or small story tweaks. It also cannot proceed without a clear change trigger, supporting evidence, and access to the PRD and epics.