bmad-correct-course

Analyzes sprint change impact and generates a structured Sprint Change Proposal.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-correct-course-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/BMAD-METHOD%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-v6.10.0/src/bmm-skills/4-implementation/bmad-correct-course
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-correct-course-shaahy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a significant issue emerges mid-sprint, teams lack a systematic way to assess its impact across the PRD, epics, architecture, and UX artifacts and to decide how to respond. This Skill guides that analysis and produces an actionable Sprint Change Proposal with a clear implementation handoff. ## Core Features & Use Cases - Impact Analysis Checklist: Walks through a structured checklist covering trigger context, epic impact, artifact conflicts, and path-forward options (direct adjustment, rollback, or MVP review). - Sprint Change Proposal Generation: Compiles findings into a proposal document with issue summary, impact analysis, recommended approach, detailed before/after edit proposals, and handoff plan. - Scope-Based Routing: Classifies the change as Minor, Moderate, or Major and routes it to the appropriate role (Developer, Product Owner, or PM/Architect). - Use Case: During implementation you discover a security requirement that invalidates a planned story. Run this workflow to assess the blast radius across all planning artifacts and produce an approved change proposal before any code is touched. ## Quick Start Ask the agent to correct course and analyze the impact of the issue you just discovered on the current sprint plan.

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 requirement change mid-sprint in an agile workflow?▼

Run a structured change-navigation workflow that assesses impact on epics, stories, PRD, and architecture, then produces a Sprint Change Proposal. The proposal documents the issue, recommended path forward, and handoff plan before any implementation begins.

What is a Sprint Change Proposal and what does it contain?▼

A Sprint Change Proposal is a document capturing a mid-sprint change decision. It contains an issue summary, epic and artifact impact analysis, a recommended approach with rationale, detailed before/after edit proposals, and an implementation handoff plan.

When should I use correct course instead of just editing stories directly?▼

Use it for significant changes affecting project direction, such as invalidated epics, PRD conflicts, or architecture changes. Minor story-level fixes that do not alter scope or plans can be handled directly without the full impact analysis.

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

The PRD and current epics/stories are required; the workflow halts without them. Architecture documents, UX specifications, and project knowledge bases are loaded when available to broaden the impact assessment.

How are approved sprint changes routed for implementation?▼

Changes are classified by scope: Minor changes go directly to a Developer agent, Moderate changes go to Product Owner and Developer for backlog reorganization, and Major changes escalate to Product Manager or Solution Architect for replanning.