bmad-correct-course

Analyzes sprint change triggers and generates structured Sprint Change Proposals with impact assessment.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-correct-course-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-correct-course
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-correct-course-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a significant issue emerges mid-sprint (technical limitation, new requirement, strategic pivot), teams lack a structured way to assess its impact on the PRD, epics, architecture, and UX artifacts before deciding how to respond. ## Core Features & Use Cases - Systematic Impact Analysis: Walks through a six-section checklist covering trigger context, epic impact, artifact conflicts, path-forward options, proposal components, and final handoff. - Sprint Change Proposal Generation: Produces a dated proposal document with issue summary, impact analysis, recommended approach, detailed before/after edit proposals, and implementation handoff plan. - Scope-Based Routing: Classifies changes as Minor, Moderate, or Major and routes them to the appropriate role (Developer, Product Owner, or Product Manager/Architect). - Use Case: During implementation, a developer discovers the chosen database cannot support a required query pattern. Use this Skill to evaluate epic and architecture impact, compare direct adjustment versus rollback versus MVP rescoping, and produce an approved change proposal. ## Quick Start Ask the AI 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 change discovered mid-sprint?▼

Use a structured change navigation workflow that identifies the trigger, assesses epic and artifact impact, evaluates path-forward options, and produces a Sprint Change Proposal. This Skill guides that analysis interactively and requires explicit user approval before implementation.

What is a Sprint Change Proposal in agile workflows?▼

A Sprint Change Proposal is a document capturing an issue summary, impact analysis across epics and planning artifacts, a recommended path forward, detailed edit proposals, and an implementation handoff plan. It formalizes how significant mid-sprint changes are evaluated and approved.

What documents does this change analysis workflow require?▼

The workflow requires access to the PRD and Epics documents, and halts if they are missing. Architecture, UX design, spec documents, and project knowledge indexes are loaded when available to broaden the impact assessment.

When should I use rollback versus direct adjustment for sprint changes?▼

The workflow evaluates three options: direct adjustment within existing epics, rollback of completed stories, or MVP scope review. Each option is scored on effort and risk, and the checklist recommends the path with the best trade-off for timeline, complexity, and business value.

Who implements the changes after a Sprint Change Proposal is approved?▼

Routing depends on scope classification. Minor changes go to a Developer agent, moderate changes to Product Owner and Developer coordination, and major changes escalate to a Product Manager or Solution Architect for fundamental replanning.