bmad-correct-course

Analyze sprint change impact across PRD, epics, and architecture to produce a Sprint Change Proposal.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-correct-course-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-correct-course
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-correct-course-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a significant issue emerges mid-sprint, teams lack a structured way to assess its impact across planning artifacts and decide how to respond. This Skill guides a systematic change analysis and produces an actionable Sprint Change Proposal with clear handoff routing. ## Core Features & Use Cases - Impact Analysis Checklist: Works through a six-section checklist covering trigger context, epic impact, artifact conflicts (PRD, architecture, UX), and path-forward evaluation. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, PRD sections, architecture, and UX artifacts in incremental or batch review mode. - Scope-Based Handoff: Classifies the change as Minor, Moderate, or Major and routes it to the Developer, Product Owner, or PM/Architect accordingly. - Use Case: During implementation you discover a security requirement that invalidates planned stories. Run this workflow to assess the blast radius across epics and the PRD, then generate an approved Sprint Change Proposal document. ## Quick Start Ask the agent to correct course and analyze the impact of the issue you discovered during the current sprint.

Frequently Asked Questions about bmad-correct-course

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

FAQPage Schema
How do I handle a major requirement change mid-sprint in agile?

Run a structured change navigation workflow that confirms the trigger, assesses impact on epics and artifacts, evaluates path-forward options, and produces a Sprint Change Proposal. The proposal is then routed to the appropriate role based on change scope.

What documents are needed to assess sprint change impact?

A PRD and current epics/stories are required; the workflow halts without them. Architecture documents, UX specifications, specs, and a project knowledge index are loaded when available to broaden the impact analysis.

Can I review proposed story changes one at a time?

Yes, the workflow supports an Incremental mode where each edit proposal is presented individually for approve, edit, or skip decisions. A Batch mode presents all proposals together at the end for teams preferring a single review.

When should a sprint change be escalated to a Product Manager or Architect?

Escalation happens when the change is classified as Major scope, meaning it requires fundamental replanning rather than direct story edits or backlog reorganization. Minor changes go to the Developer agent and Moderate changes to PO/DEV coordination.

What happens if the PRD or epics cannot be found?

The workflow halts with a message explaining that PRD and Epics are required to assess change impact. It supports fuzzy filename matching and both whole-document and sharded directory layouts before giving up.