bmad-correct-course

Analyze sprint change impacts across PRD, epics, architecture, and UX documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Correct course during sprint execution is challenging without a structured approach. This skill provides a formal workflow to analyze impacts across PRD, Epics, Architecture, and UX artifacts, ensuring changes are deliberate and well-communicated.

Core Features & Use Cases

  • Structured impact analysis across planning artifacts (PRD, epics, architecture, UX) to surface dependencies and risks.
  • Sprint Change Proposal generation with clear next steps, handoff plan, and alignment notes for stakeholders.
  • Multiple remediation paths (Direct Adjustment, Potential Rollback, MVP Review) with justification and risk scoring.

Quick Start

Explain the triggering issue and initiate the sprint change workflow to produce an actionable 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 without disrupting existing PRD and epic planning?

Sprint changes are managed by analyzing impacts across PRD, epics, architecture, and UX documents. This structured impact analysis surfaces dependencies and generates a formal Sprint Change Proposal to ensure changes are deliberate and well-communicated.

What is the best way to assess risks when pivoting mid-sprint?

Mid-sprint pivots require a structured impact analysis across planning artifacts to surface dependencies and risks. The process generates a Sprint Change Proposal with multiple remediation paths, effort estimation, and risk scoring to justify decisions.

How do I generate a formal handoff plan after adjusting backlog priorities during a sprint?

Backlog adjustments are formalized by generating a Sprint Change Proposal that includes clear next steps, alignment notes, and a defined handoff plan for implementation. This ensures stakeholders understand the priority shifts and execution expectations.

Can I use this workflow to evaluate sprint changes against architecture and UX specifications?

Yes, the workflow evaluates sprint changes by explicitly analyzing impacts on architecture and UX specifications alongside PRD and epics. This cross-artifact tracking ensures technical constraints and user experience designs are aligned during pivots.

When should I initiate a formal sprint change proposal instead of a direct backlog adjustment?

A formal Sprint Change Proposal is needed when sprint changes require impact analysis across multiple artifacts like PRD, epics, architecture, and UX. It provides structured remediation paths such as Direct Adjustment, Potential Rollback, or MVP Review with risk scoring.

What remediation paths are available when correcting course during sprint execution?

Remediation paths for sprint execution course correction include Direct Adjustment, Potential Rollback, and MVP Review. Each path is evaluated with formal justification and risk scoring within the generated Sprint Change Proposal.