bmad-correct-course

Produce a formal Sprint Change Proposal for approving significant sprint changes.

1|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-correct-course-mazenmrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-correct-course
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-correct-course-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Workflow-guided change management across PRD, epics, architecture, and UX artifacts.
  • Interactive, checklist-driven analysis with explicit handoff planning.
  • Generates a concrete Sprint Change Proposal and implementation plan ready for stakeholder approval.

Quick Start

Initiate a sprint-change review by walking through the workflow.md with the user and applying the checklist to produce 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 without losing track of PRD and epic updates?

A Sprint Change Proposal documents significant sprint adjustments by guiding cross-functional impact assessment across PRD, epics, architecture, and UX artifacts, producing a concrete plan ready for stakeholder approval.

When do I need a formal sprint change proposal for product management?

A formal sprint change proposal is needed during sprint execution to manage significant modifications, enabling cross-functional impact assessment and clear alignment before updating artifacts and proceeding to handoff.

How do I document cross-functional impacts when changing sprint architecture or UX?

Document cross-functional impacts using an interactive, checklist-driven workflow that analyzes modifications across architecture and UX artifacts, generating a structured Sprint Change Proposal for stakeholder decisions.

Can I use a checklist-driven workflow for sprint change management and handoff planning?

Yes, a checklist-driven workflow supports end-to-end change management by evaluating sprint modifications and producing explicit handoff planning alongside a concrete implementation plan for stakeholder approval.

What is the best way to assess risks before implementing sprint changes?

The best way to assess risks is through a workflow-guided sprint change review that produces a formal proposal, satisfying end-to-end change management requirements including artifact updates and risk assessment.

Does sprint change management work for updating PRD and epics mid-sprint?

Yes, sprint change management applies directly to updating PRD and epics mid-sprint, analyzing the cross-functional impacts of these modifications to produce an aligned implementation and handoff plan.