skills.rest
jgabriellima
jgabriellimaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bmad-correct-course

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

Updated May 7, 2026
Search Tags:#epics#impact analysis#agile#backlog#prd#change proposal#sprint change
One-click install
npx skills add https://github.com/jgabriellima/deep-agent-skill --skill bmad-correct-course-jgabriellima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/bmad-correct-course
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill bmad-correct-course-jgabriellima

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 requirements, epics, architecture, and UX artifacts, leading to ad-hoc decisions and misaligned documents. ## Core Features & Use Cases - Impact Analysis Checklist: Systematically evaluates the change trigger, epic impact, and conflicts across PRD, architecture, and UX artifacts. - Structured Change Proposals: Drafts explicit before/after edit proposals for stories, PRD sections, and architecture components with rationale. - Scoped Handoff Routing: Classifies changes as Minor, Moderate, or Major and routes them to Developer, Product Owner, or Product Manager/Architect roles. - Use Case: A developer discovers a technical limitation invalidating a planned story; the workflow analyzes affected epics, proposes story and PRD edits, and produces a Sprint Change Proposal document for approval. ## Quick Start Ask the agent to correct course and propose a sprint change for the issue discovered in the current story.

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 change during an active sprint?▼

Run the correct course workflow to analyze the triggering issue, assess impact across PRD, epics, architecture, and UX artifacts, then generate a Sprint Change Proposal. The proposal includes before/after edit proposals and a recommended path forward for approval.

What documents are required to run a sprint change analysis?▼

The workflow requires a PRD and current epics/stories; it halts if these are missing. Architecture documents, UX specifications, specs, and a project knowledge index are loaded when available but are optional.

What is a Sprint Change Proposal and what does it contain?▼

A Sprint Change Proposal is a structured document containing an issue summary, impact analysis, recommended approach with effort and risk estimates, detailed edit proposals, and an implementation handoff plan. It is written to the planning artifacts directory.

Can I review proposed changes one at a time instead of all at once?▼

Yes, the workflow supports an Incremental mode where each edit proposal is presented individually for approval, editing, or skipping. A Batch mode presents all proposals together at the end of the drafting step.

When should I use correct course instead of just editing a story?▼

Use it for significant changes affecting project direction, such as invalidated epics, MVP scope changes, or architecture conflicts. Minor story-level fixes that do not affect other artifacts can be handled directly without the full impact analysis.

Related Skills

Explore More Product & Management Skills→
b566776b566776

bmad-correct-course

Analyze sprint change impacts across PRD, epics, architecture, and UX documents.

Community
Advanced
diegosanchespereira1diegosanchespereira1

bmad-dev-story

Execute story implementation workflows with test-first validation and status updates.

Community
Advanced
alex-tgkalex-tgk

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from epics.

Community
Intermediate
EricJamesCrowEricJamesCrow

avoid-feature-creep

Apply a 5-step decision framework to prevent feature creep in software projects.

Community
Intermediate