bmad-correct-course

Coordinates sprint-change decisions and produces a formal Sprint Change Proposal.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-correct-course-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/Wizarck/iguanatrader/tree/main/skills/bmad-correct-course
Command: npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-correct-course-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage mid-sprint changes by coordinating decisions and keeping teams aligned with product goals.

Core Features & Use Cases

  • Structured sprint-change workflow that captures issue summaries, impact analyses, and handoff plans.
  • Generates a Sprint Change Proposal document ready for stakeholder review and approval.
  • Integrates with planning artifacts (PRD, Epics, Architecture, UX) to assess cross-artifact impact.

Quick Start

Follow the Correct Course workflow in workflow.md to generate and approve 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 mid-sprint scope changes without derailing the team?

To manage mid-sprint scope changes, you coordinate sprint-change decisions to realign priorities and produce a formal Sprint Change Proposal. This keeps the team aligned with product goals when new issues arise during the sprint.

What is a Sprint Change Proposal and when do I need one?

A Sprint Change Proposal is a formal document capturing issue summaries, impact analyses, and handoff plans. You need one when reviewing product requirements, architecture, or UX specs to evaluate cross-artifact impact during a sprint.

How do I assess the impact of a sprint change on existing planning artifacts?

Assess sprint change impact by integrating the proposal with existing planning artifacts like PRDs, Epics, Architecture, and UX specs. This evaluates cross-artifact impact and produces structured handoff recommendations.

Does this sprint change workflow require existing PRD and architecture documents?

Yes, the sprint change workflow integrates with existing planning artifacts such as PRDs, Epics, Architecture, and UX specs to accurately assess cross-artifact impact and produce a viable handoff plan.

What's the best way to document sprint changes for stakeholder approval?

The best way to document sprint changes is generating a Sprint Change Proposal with structured sections for issue, impact, recommendations, and handoff. This format is ready for stakeholder review and formal approval.

Where are sprint change proposals saved after generation?

Sprint change proposals are output directly to the planning artifacts directory. This ensures the formal handoff documents are stored alongside existing PRDs, Epics, and Architecture files for team access.