bmad-correct-course

Analyze sprint change triggers and generate an approved Sprint Change Proposal.

36|16|Updated May 1, 2026
One-click install
npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-correct-course-tronghieu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/tronghieu/lumina-wiki/tree/main/.agents/skills/bmad-correct-course
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-correct-course-tronghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams handle “correct course” moments by turning an unclear or late-breaking sprint change into a structured proposal that updates the right project artifacts.

Core Features & Use Cases

  • Sprint Change Proposal generation: Produces a clear, actionable proposal including issue summary, impact analysis, recommended approach, and implementation handoff.
  • Cross-artifact impact assessment: Assesses how PRD, epics/stories, architecture, UX specs, and other planning artifacts must change to accommodate the new direction.
  • Interactive change refinement: Supports incremental review/iteration by presenting edits proposal-by-proposal and collecting approvals or edits.

Quick Start

Ask your AI to run bmad-correct-course when you say something like “correct course” or “propose sprint change” for your current sprint.

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 a sprint change and assess its impact across project artifacts?

To manage a sprint change, you need a structured proposal that analyzes the trigger context and assesses cross-artifact impact on your PRD, epics, architecture, and UX specs. This ensures you update the right planning documents before executing the pivot.

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

A sprint change proposal is a structured plan for deciding and executing a project pivot during a sprint. You need one when a late-breaking change requires impact analysis and updates to your PRD, epics, stories, or architecture artifacts.

How do I analyze the impact of a sprint pivot on my PRD and architecture?

Cross-artifact impact analysis evaluates how a new direction affects your PRD, epics, architecture, and UX specifications. It halts execution to review required changes proposal-by-proposal, ensuring all planning artifacts align before implementation handoffs.

Can I review and refine sprint change proposals incrementally before approval?

Yes, interactive change refinement supports incremental review by presenting edits proposal-by-proposal. You can collect approvals or request edits to the sprint change plan before finalizing the implementation handoff.

Does this sprint change workflow require existing project configuration and epics?

Yes, the workflow loads persistent facts and project configuration languages, performing artifact discovery that requires existing PRD and epics. It halts if these core planning artifacts are missing before generating the proposal.

What is the best way to turn a late-breaking sprint change into an actionable plan?

The best way to handle an unclear sprint change is generating a structured proposal with an issue summary, impact analysis, recommended approach, and implementation handoff. This transforms ambiguous triggers into clear edit handoffs for your team.