bmad-correct-course

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

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

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 the PRD, epics, architecture, and UX artifacts. This Skill guides a structured change-management workflow that produces an actionable Sprint Change Proposal with clear handoff routing. ## Core Features & Use Cases - Impact Analysis Checklist: Works through a six-section checklist covering trigger context, epic impact, artifact conflicts, path-forward options, proposal components, and final review. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, PRD sections, architecture, and UX documents, in incremental or batch review mode. - Scope-Based Handoff: Classifies the change as Minor, Moderate, or Major and routes it to the Developer, Product Owner, or Product Manager/Architect accordingly. - Use Case: A developer discovers a technical limitation that invalidates a planned story. Invoke this Skill to assess the impact on remaining epics, update sprint-status.yaml, and produce a Sprint Change Proposal for PO approval. ## Quick Start Ask the agent to correct course and analyze the impact of the issue you describe on the current sprint plan.

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, epics, architecture, and UX documents, runs a structured impact checklist, and produces a Sprint Change Proposal with before/after edit proposals and a handoff plan.

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, UX specifications, and spec documents are loaded when available, and AGENTS.md project context is read if present.

Can I review each proposed change individually instead of all at once?

Yes. The workflow offers two modes: Incremental, where each edit proposal is presented for approve/edit/skip review, and Batch, where all proposals are collected and presented together at the end of the drafting step.

What happens after the Sprint Change Proposal is approved?

The change is classified by scope: Minor changes route to the Developer agent for direct implementation, Moderate changes go to Product Owner/Developer for backlog reorganization, and Major changes escalate to Product Manager/Architect for replanning.

When should I not use the correct course workflow?

It is designed for significant changes affecting project direction, such as epic re-scoping or MVP review. Small bug fixes or routine story tweaks that do not alter the plan should be handled directly by the developer without this workflow.