bmad-correct-course

Analyze cross-artifact impacts to generate a Sprint Change Proposal.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/mschuerig/peach-ios --skill bmad-correct-course-mschuerig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/mschuerig/peach-ios/tree/main/_bmad/bmm/workflows/4-implementation/bmad-correct-course
Command: npx skills add https://github.com/mschuerig/peach-ios --skill bmad-correct-course-mschuerig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

Core Features & Use Cases

  • Cross-artifact impact analysis: PRD, epics, architecture, and UX are reviewed to understand ripple effects.
  • Structured sprint-change proposal generation: outputs a documented Sprint Change Proposal with sections for issue summary, impact analysis, recommended path, and handoff.
  • Handoff-ready outputs: coordinates with Development, Product Owner/Scrum Master, and Architects for smooth implementation.
  • Trigger-based workflows: activated when stakeholders request course corrections or sprint changes.

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 when stakeholders request a course correction mid-execution?

A sprint change proposal is a structured document that coordinates change management by analyzing ripple effects across PRD, epics, architecture, and UX. It provides an actionable plan containing an issue summary, impact analysis, recommended path, and implementation handoff details.

How do I generate a sprint change proposal for a requested course correction?

To analyze cross-artifact impacts, review the PRD, epics, architecture, and UX documents to understand the ripple effects of the requested change. This evaluation identifies how modifications to sprint scope will affect existing product requirements, technical design, and user experience workflows.

Does sprint change management work for coordinating handoffs to Development and Product Owner roles?

Yes, sprint change management coordinates handoffs by delivering actionable plans for Development, Product Owner/Scrum Master, and Architects. The generated proposal ensures smooth implementation by structuring the detailed change proposals and handoff instructions for each specific role.

What's the best way to document impact analysis for mid-sprint epic changes?

The best way to document impact analysis for mid-sprint epic changes is a structured Sprint Change Proposal. It systematically evaluates the requested correction against PRD, epics, architecture, and UX artifacts to deliver a clear, handoff-ready implementation plan for review.