bmad-correct-course

Analyze sprint changes and produce structured change proposals with impact assessment.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-correct-course-geneducation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-correct-course
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-correct-course-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams respond to significant mid-sprint changes without losing clarity, by turning an unclear issue into a structured impact analysis and decision path.

Core Features & Use Cases

  • Trigger Analysis: Identifies the story or event that caused the change request and captures concrete evidence.
  • Cross-Artifact Impact Review: Checks PRD, epics, architecture, UX, and supporting artifacts for conflicts and ripple effects.
  • Path Recommendation: Evaluates direct adjustment, rollback, and MVP scope review options to recommend the best course of action.
  • Use Case: A sprint exposes a new technical constraint, and this Skill helps the team decide whether to revise stories, reshape epics, or update the MVP plan.

Quick Start

Use the bmad-correct-course skill to analyze the triggering issue, assess its impact across project artifacts, and draft a sprint change proposal with a clear handoff plan.

Frequently Asked Questions about bmad-correct-course

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze mid-sprint changes to epics and stories without disrupting the PRD?

To analyze mid-sprint changes, identify the triggering story and capture concrete evidence. Then assess impacts across your PRD, epics, architecture, and UX artifacts to produce a structured change proposal with a clear handoff plan.

What is the best way to handle a new technical constraint discovered during a sprint?

The best way to handle a new technical constraint is to evaluate direct adjustment, rollback, or MVP scope review paths. This structured impact assessment recommends whether to revise stories, reshape epics, or update the MVP plan.

Can I use this approach to assess UX and architecture ripple effects from a backlog change?

Yes, you can assess UX and architecture ripple effects by performing a cross-artifact impact review. This process checks supporting artifacts for conflicts to ensure the backlog change does not break existing design or structural constraints.

When do I need a structured sprint change proposal instead of just updating the backlog?

You need a structured sprint change proposal when a significant mid-sprint event requires careful validation. If the change impacts your PRD, architecture, or UX, a proposal ensures you evaluate scope options and document the implementation handoff.

Does this method require existing product artifacts to evaluate sprint scope options?

Yes, this method requires existing product artifacts like PRD, epics, architecture, and UX documentation. It validates triggers and evidence against these artifacts to accurately recommend direct adjustment, rollback, or MVP scope review options.