bmad-correct-course

Generate a structured Sprint Change Proposal from sprint-change triggers.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/ldk-hub/broke-shopping --skill bmad-correct-course-ldk-hub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/ldk-hub/broke-shopping/tree/main/_bmad/bmm/4-implementation/bmad-correct-course
Command: npx skills add https://github.com/ldk-hub/broke-shopping --skill bmad-correct-course-ldk-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage significant changes during sprint execution by analyzing triggering issues and producing a structured Sprint Change Proposal that aligns PRD, epics, architecture, and UX artifacts.

Core Features & Use Cases

  • End-to-end change analysis: evaluate the triggering issue across PRD, epics, architecture, and UX artifacts to determine impact and required updates.
  • Sprint Change Proposal generation: produce a comprehensive document with issue summary, impact analysis, recommended approach, and implementation handoff.
  • Artifact-aware routing: assign changes to the correct stakeholders (Developers, Product Owners, Architects) with clear responsibilities and handoff details.
  • Activation workflow guidance: follow a predefined workflow with steps to resolve, load facts, configure context, and generate final outputs.

Quick Start

Describe the triggering issue and run the Correct Course workflow to generate 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 manage sprint changes across PRD, epics, and architecture artifacts?▼

Manage sprint changes by analyzing triggering issues and generating a structured Sprint Change Proposal that aligns PRD, epics, architecture, and UX artifacts. This enforces an end-to-end workflow to assess impact and surface recommended updates.

What is a Sprint Change Proposal and when do I need one?▼

A Sprint Change Proposal is a comprehensive document summarizing triggering issues, impact analysis, recommended approaches, and implementation handoffs. You need one during sprint execution to manage significant changes across product and technical artifacts.

How do I analyze the impact of a sprint change trigger on UX and architecture?▼

Analyze sprint-change triggers by evaluating the issue across PRD, epics, architecture, and UX artifacts to determine impact and required updates. This artifact-aware routing assigns changes to correct stakeholders with clear responsibilities and handoff details.

Can I use a structured workflow to hand off sprint changes to developers and product owners?▼

Yes, you can use an activation workflow with predefined steps to resolve, load facts, configure context, and generate final outputs. This produces edit proposals and a handoff plan assigning changes to developers, product owners, and architects.

What's the best way to document a triggering issue during sprint execution?▼

The best way to document a triggering issue is to run an end-to-end change analysis workflow that generates a Sprint Change Proposal. This ensures the issue summary, impact assessment, and recommended approach are structured for stakeholder handoff.

What are the limitations of handling sprint changes without a structured proposal?▼

Without a structured Sprint Change Proposal, managing sprint changes lacks artifact-aware routing and persistent facts, leading to misaligned PRD, epics, architecture, and UX updates with unclear stakeholder responsibilities and handoff details.