bmad-correct-course

Assess sprint plan drift and draft a structured Sprint Change Proposal.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-correct-course-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/bmm-skills/4-implementation/bmad-correct-course
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-correct-course-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, _bmad/scripts/resolve_customization.py.

What problem does it solve?

This Skill helps you respond when implementation or discovery reveals that your sprint plan has drifted, by analyzing impact across PRD, epics, architecture, and UX and producing a structured Sprint Change Proposal you can act on.

Core Features & Use Cases

  • Change-trigger handling: Guides the user to clarify the trigger and describe the issue prompting navigation.
  • Cross-artifact impact analysis: Assesses epic-level effects and checks for conflicts in PRD, architecture, and UI/UX (loading files when available).
  • Structured sprint change output: Generates explicit edit proposals (with before/after where applicable) and compiles a complete Sprint Change Proposal plus implementation handoff.

Quick Start

Use the bmad-correct-course skill when the user says "correct course" or "propose sprint change".

Frequently Asked Questions about bmad-correct-course

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

FAQPage Schema
How do I manage sprint drift when implementation invalidates planning assumptions?

To manage sprint drift, you assess the triggering issue's impact across PRD, epics, architecture, and UX artifacts, then generate a structured Sprint Change Proposal with actionable before/after edits and a role-based handoff.

What is a sprint change proposal and when do I need one?

A sprint change proposal is a structured plan drafted when implementation reveals assumptions are invalid. You need one to document cross-artifact impacts and propose explicit edits to PRD, epics, architecture, and UX artifacts.

How do I analyze the impact of a sprint change across project artifacts?

You analyze sprint change impact by loading configured planning artifacts, assessing epic-level effects, and checking for conflicts in the PRD, architecture, and UI/UX files to ensure governance and consistency.

Do I need Python to generate a sprint change proposal?

Yes, you need Python3 installed because the workflow executes customization resolution via a Python script to load project context and produce the actionable before/after proposals and implementation handoff.

What's the best way to update epics and stories after discovering a planning conflict?

The best way to update epics and stories after a conflict is to compile a complete Sprint Change Proposal containing explicit edit proposals with before/after states, followed by a role-based implementation handoff.