bmad-correct-course

Assess sprint change impact across PRD, epics, architecture, and UX documents to produce a sprint change proposal.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-correct-course-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-correct-course
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-correct-course-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a significant issue emerges mid-sprint, teams lack a structured way to evaluate its ripple effects across planning artifacts and decide whether to adjust stories, roll back work, or rescope the MVP. ## Core Features & Use Cases - Impact Analysis Checklist: Systematically evaluates the change trigger, epic impact, and conflicts across PRD, architecture, and UX documents. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, PRD sections, and architecture decisions with rationale. - Scoped Handoff Routing: Classifies changes as Minor, Moderate, or Major and routes them to Developer, Product Owner, or Architect roles. - Use Case: A developer discovers a technical limitation invalidating a planned epic; the workflow analyzes all planning artifacts, proposes story and PRD edits, and produces an approved Sprint Change Proposal document. ## Quick Start Ask the agent to correct course and propose a sprint change for the issue you just discovered during implementation.

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 in agile?

Run the correct course workflow to assess impact across your PRD, epics, architecture, and UX documents. It guides you through a change analysis checklist, drafts specific edit proposals, and produces a Sprint Change Proposal with an implementation handoff plan.

What documents are required to run a sprint change analysis?

The PRD and current epics are required; the workflow halts if they cannot be found. Architecture, UX design, and spec documents are loaded if available, and AGENTS.md project context is read when present.

Can I review change proposals one at a time instead of all at once?

Yes, the workflow offers Incremental mode where each edit proposal is presented individually for approve, edit, or skip decisions. Batch mode presents all proposals together at the end for a single review.

When should I use correct course versus just editing stories directly?

Use it for significant changes affecting project direction, such as invalidated epics, MVP scope questions, or architecture conflicts. Minor story tweaks that do not ripple across planning artifacts can be handled directly by a developer.

What happens after the sprint change proposal is approved?

The workflow classifies scope as Minor, Moderate, or Major and routes handoff accordingly: Developer for direct implementation, Product Owner for backlog reorganization, or Product Manager and Architect for fundamental replanning.