bmad-correct-course

Generate a structured Sprint Change Proposal with impact analysis across PRD, epics, architecture, and UX.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage significant changes during sprint execution by analyzing impact across PRD, epics, architecture, and UX, and producing a structured Sprint Change Proposal with clear handoff.

Core Features & Use Cases

  • Cross-artifact impact analysis across PRD, epics, architecture, and UX to determine the full scope of a change
  • Generation of explicit edit proposals, risk and effort estimates, and a concrete handoff plan
  • Structured Sprint Change Proposal suitable for review, approval, and execution by the team

Quick Start

Describe the triggering issue to start the workflow and generate a review-ready 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 manage sprint changes when requirements shift mid-execution?

To manage sprint changes, you need a structured Sprint Change Proposal that assesses impact across PRD, epics, architecture, and UX. This ensures cross-artifact alignment, formal documentation, risk estimation, and a clear handoff plan for stakeholder review.

What is a sprint change proposal and when do I need one?

A sprint change proposal is a structured document detailing the need for sprint changes and their cross-artifact impact. You need one when a course correction occurs during sprint execution to inform decisions, estimate effort, and align stakeholders.

How do I analyze the impact of a PRD change on existing epics and architecture?

Analyzing PRD change impact on epics and architecture requires a cross-artifact assessment to determine the full scope. It generates explicit edit proposals, risk estimates, and a concrete handoff plan to guide execution.

Can I generate a review-ready handoff plan for a sprint course correction?

Yes, you can generate a review-ready handoff plan by triggering the workflow with a description of the issue. It produces a structured Sprint Change Proposal with actionable handoff, risk estimates, and execution planning for team approval.

What's the best way to document risk and effort estimates for a sprint change?

The best way to document risk and effort estimates is through a structured Sprint Change Proposal. It evaluates changes across PRD, epics, architecture, and UX artifacts, producing formal estimates and a concrete handoff plan for stakeholder alignment.