bmad-correct-course

Analyzes sprint change requests and generates structured Sprint Change Proposal documents.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-correct-course-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-correct-course
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-correct-course-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a significant issue emerges mid-sprint, teams lack a systematic way to assess its impact across PRD, epics, architecture, and UX artifacts, leading to ad-hoc decisions and undocumented scope changes. ## Core Features & Use Cases - Impact Analysis Checklist: Walks through a six-section checklist covering trigger context, epic impact, artifact conflicts, and path-forward evaluation. - Structured Change Proposals: Produces a Sprint Change Proposal with issue summary, impact analysis, recommended approach, detailed before/after edits, and implementation handoff. - Scope-Based Routing: Classifies changes as Minor, Moderate, or Major and routes them to Developer, Product Owner, or Product Manager/Architect roles. - Use Case: A developer discovers an authentication requirement conflict mid-sprint; the workflow loads the PRD and epics, assesses affected stories, and produces an approved proposal routed to the right agent. ## Quick Start Say "correct course" or "propose sprint change" and describe the issue that triggered the need for a 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 handle a major change request in the middle of a sprint?▼

Invoke the correct course workflow and describe the triggering issue. It loads your PRD and epics, runs an impact-analysis checklist, and produces a Sprint Change Proposal with specific before/after edits and a recommended path forward.

What documents are required to run a sprint change analysis?▼

The PRD and current epics/stories are required; the workflow halts if they cannot be found. Architecture documents, UX specifications, and project knowledge files are loaded optionally when available.

What is included in a Sprint Change Proposal?▼

The proposal contains an issue summary, impact analysis across epics and artifacts, a recommended approach (direct adjustment, rollback, or MVP review), detailed edit proposals with before/after text, and an implementation handoff plan.

Can I review each proposed change individually before approving?▼

Yes. Choose Incremental mode to review and refine each edit proposal one at a time with approve, edit, or skip options. Batch mode presents all proposals together at the end for a single review.

When should I use correct course instead of just editing stories directly?▼

Use it for significant changes affecting project direction, such as new requirements, technical limitations, or strategic pivots. Minor story tweaks that do not impact epics, PRD, or architecture do not need this full workflow.