bmad-correct-course

Analyze sprint issues and generate structured change proposals.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-correct-course-ncptuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/ncptuan/stock_backtest_project/tree/main/.claude/skills/bmad-correct-course
Command: npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-correct-course-ncptuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams handle significant changes discovered during sprint execution without losing clarity, alignment, or control. It provides a structured way to assess what changed, why it matters, and how that change affects epics, stories, product requirements, architecture, UX, and delivery plans.

Core Features & Use Cases

  • Structured change analysis: Walks through a detailed checklist to identify the trigger, validate evidence, and assess project-wide impact.
  • Cross-artifact impact review: Evaluates how a change affects PRDs, epics, stories, architecture, UX, technical planning, and related delivery artifacts.
  • Sprint Change Proposal generation: Produces a documented recommendation with rationale, before-and-after edits, implementation handoff, and approval flow.
  • Use case: When a team discovers during implementation that a current story is blocked by a technical limitation or a newly surfaced stakeholder requirement, this Skill helps propose a controlled sprint course correction instead of making ad hoc changes.

Quick Start

Ask the AI to use bmad-correct-course to analyze a newly discovered sprint issue and propose the best path forward with impact on epics, requirements, architecture, and delivery.

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 a major sprint course correction when we discover new technical constraints?

Manage a major sprint course correction by analyzing the triggering issue, executing an interactive impact checklist across artifacts, and producing a structured change proposal with before-and-after edits and implementation handoff.

What is the best way to assess the impact of requirement changes on epics and backlog stories?

Assess the impact of requirement changes by loading existing PRDs, epics, architecture, and UX artifacts, then running an interactive impact checklist to map how the changes affect project-wide delivery plans.

How does a structured change proposal handle failed implementation approaches during sprint planning?

A structured change proposal handles failed implementation approaches by validating evidence of the failure, drafting before-and-after edits to epics and stories, and defining an implementation handoff after obtaining approval.

Can I review MVP scope and reshape epics without making ad hoc changes to the product requirements?

You can review MVP scope and reshape epics by loading related planning artifacts, executing an impact assessment, and documenting the reshaping through a controlled change proposal with a formal approval flow.

When do I need a formal impact assessment for backlog refinement and PRD updates?

You need a formal impact assessment for backlog refinement and PRD updates when newly discovered technical limitations or stakeholder requirements threaten the clarity, alignment, or control of the current sprint execution.

What planning artifacts are required to evaluate project-wide impact during change management?

Evaluating project-wide impact during change management requires loading the product requirements document, epics, architecture documents, UX designs, and related technical planning artifacts to draft accurate before-and-after edits.