bmad-correct-course

Analyze change impact across project artifacts and generate a Sprint Change Proposal.

26|23|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/laraxot/laravelpizza.com --skill bmad-correct-course-laraxot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/laraxot/laravelpizza.com/tree/main/.github/skills/bmad-correct-course
Command: npx skills add https://github.com/laraxot/laravelpizza.com --skill bmad-correct-course-laraxot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill manages significant changes during sprint execution, ensuring smooth course corrections with a structured approach.

Core Features & Use Cases

  • Change Impact Analysis: Assess the impact of changes on epics, stories, and artifacts.
  • Epic Impact Assessment: Evaluate the current epic's viability and determine required changes.
  • Artifact Conflict Analysis: Review PRD, architecture, and UI/UX for conflicts and adjustments.
  • Path Forward Evaluation: Choose the best course of action based on analysis.
  • Sprint Change Proposal: Generate a comprehensive proposal for implementation.

Quick Start

Execute the bmad-correct-course skill to manage a significant change in your sprint.

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 significant changes during sprint execution without disrupting project artifacts?

Manage significant sprint changes by analyzing the impact across epics, stories, and artifacts to produce a structured Sprint Change Proposal. This approach assesses epic viability, reviews PRD and architecture conflicts, and evaluates the best path forward for smooth course correction.

What is a Sprint Change Proposal and when do I need one for project management?

A Sprint Change Proposal is a comprehensive document generated after assessing change impacts on epics, stories, and artifacts. You need one during sprint execution when significant changes arise, requiring conflict analysis across PRD, architecture, and UX specifications to determine the best path forward.

How do I analyze the impact of a sprint change on epics and architecture documents?

Analyze sprint change impact by interactively evaluating the current epic's viability and reviewing project artifacts like PRD, architecture, and UI/UX specifications for conflicts. This artifact conflict analysis identifies required adjustments and helps choose the best course of action.

Do I need existing project documents like a PRD to use sprint change management?

Yes, sprint change management requires existing project documents like PRD, epics, architecture, and UX specifications. These artifacts are necessary inputs to perform accurate change impact analysis and generate a structured Sprint Change Proposal during sprint execution.

What's the best way to assess epic viability when a sprint requires course correction?

The best way to assess epic viability during sprint course correction is to perform a structured change impact analysis across all project artifacts. This evaluation reviews PRD, architecture, and UI/UX conflicts to determine required epic changes and choose the best path forward.

Why does sprint planning fail when significant changes are introduced mid-sprint?

Sprint planning encounters issues mid-sprint when significant changes occur because unanalyzed impacts ripple across epics, stories, and artifacts. Without structured artifact conflict analysis and a Sprint Change Proposal, teams struggle to evaluate the path forward and adjust requirements smoothly.