bmad-correct-course

Analyze mid-sprint change impact and generate a structured Sprint Change Proposal.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-correct-course-marcmontecalvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-correct-course
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-correct-course-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the chaos of mid-sprint pivots by providing a rigorous, artifact-aware framework to assess the impact of changes on project requirements, architecture, and design.

Core Features & Use Cases

  • Impact Assessment: Automatically evaluates how a proposed change affects PRDs, epics, stories, and architectural documentation.
  • Sprint Change Proposal: Generates a comprehensive, actionable document detailing the problem, impact, recommended approach, and implementation handoff.
  • Use Case: When a technical limitation is discovered during development, use this Skill to analyze whether to adjust the current story, rollback recent work, or redefine the MVP, ensuring all project artifacts remain synchronized.

Quick Start

Activate the bmad-correct-course skill to begin a guided sprint change analysis for the current project.

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 changes without derailing the project?

Mid-sprint changes require structured impact analysis to evaluate effects on PRDs, epics, and architecture. This Skill generates a comprehensive Sprint Change Proposal detailing the problem, recommended approach, and implementation handoff to keep artifacts synchronized.

What is a sprint change proposal and when do I need one?

A sprint change proposal is a structured document assessing how mid-sprint pivots impact project artifacts. You need one when technical limitations or scope changes occur during development, ensuring rigorous evaluation before adjusting stories or redefining an MVP.

How do I assess the impact of a technical limitation discovered during development?

Assess technical limitations by analyzing their impact across project requirements, architecture, and design. This Skill evaluates whether to adjust the current story, rollback recent work, or redefine the MVP while keeping all artifacts synchronized.

Can I use this for agile epic re-planning and artifact synchronization?

Yes, it applies to agile workflows requiring rigorous change management, epic re-planning, and artifact synchronization. It provides an artifact-aware framework to navigate sprint changes across PRDs, stories, and architectural documentation.

Do I need specific project planning documents to perform sprint impact analysis?

Yes, you need access to existing project planning documents. The Skill requires these artifacts to accurately evaluate the impact of proposed changes and produce a structured Sprint Change Proposal for implementation handoff.

What is the best way to evaluate whether to rollback work or redefine an MVP?

The best way is using an artifact-aware framework that analyzes the impact of changes on PRDs, epics, and architecture. This generates a comprehensive proposal detailing the problem and recommended approach for implementation handoff.