bmad-correct-course

Analyze sprint changes and generate a Sprint Change Proposal with implementation handoff.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-correct-course-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-correct-course
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-correct-course-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams navigate major mid-sprint changes without losing control of scope, dependencies, or delivery timing. It converts a vague problem into a structured change analysis so the team can decide what must change and why.

Core Features & Use Cases

  • Trigger and impact analysis: Identifies the issue, classifies the change type, and gathers evidence from the triggering story or stakeholder feedback.
  • Artifact-aware planning: Reviews PRD, epics, architecture, UX, and related project documents to find conflicts and required updates.
  • Proposal and handoff generation: Drafts a Sprint Change Proposal with recommended next steps, detailed edit proposals, and implementation routing.
  • Use case: A developer discovers a story cannot be implemented as written; this Skill traces the impact, recommends whether to adjust scope or replan, and prepares the change for approval.

Quick Start

Tell this Skill the triggering issue, the affected artifacts, and whether you want incremental or batch review so it can produce a Sprint Change Proposal.

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 mid-sprint scope changes without losing track of architecture and PRD updates?

To handle mid-sprint scope changes, analyze the triggering issue and its impact on PRD, epics, architecture, and UX plans, then generate a Sprint Change Proposal with structured edit proposals and approval routing for clear implementation handoff.

What is the best way to trace project artifact conflicts when a stakeholder introduces new requirements mid-sprint?

Tracing project artifact conflicts involves reviewing PRD, epics, architecture, and UX documents against the new requirements to identify required updates, then routing a Sprint Change Proposal for approval.

How do I convert a failed story implementation into a structured sprint change analysis?

Converting a failed implementation requires gathering evidence from the triggering story, classifying the change type, evaluating affected artifacts through a checklist, and drafting a Sprint Change Proposal with recommended next steps.

Can I batch review edit proposals for multiple affected epics and UX plans during a sprint pivot?

Yes, you can request incremental or batch review when evaluating sprint pivots, allowing the tool to process affected epics and UX plans collectively before generating the final Sprint Change Proposal.

When do I need a formal Sprint Change Proposal for project blockers?

You need a formal Sprint Change Proposal when mid-sprint blockers, scope pivots, or failed approaches affect your PRD, epics, architecture, or UX plans and require structured edit proposals and implementation routing.

Does this sprint change management process require specific input artifacts to evaluate stakeholder feedback?

Yes, evaluating stakeholder feedback requires the triggering issue details and the affected project artifacts, such as the PRD, epics, architecture, or UX plans, to perform checklist-driven evaluation and generate accurate edit proposals.