bmad-correct-course

Analyze sprint changes and generate a structured Sprint Change Proposal.

Updated May 23, 2026
One-click install
npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-correct-course-diegosanchespereira1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-correct-course
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-correct-course-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage significant mid-sprint changes without losing track of product goals, delivery plans, or cross-functional dependencies. It turns a vague issue into a structured change process that can be reviewed and approved.

Core Features & Use Cases

  • Change Trigger Analysis: Identifies what sparked the course correction and captures the core problem clearly.
  • Impact Assessment: Reviews epics, stories, PRD content, architecture, UX, and related artifacts for downstream effects.
  • Proposal Generation: Produces a detailed Sprint Change Proposal with recommended actions, revised artifact edits, and handoff guidance.
  • Use Case: A stakeholder asks for a new workflow in the middle of a sprint, and this Skill helps determine whether to adjust scope, revise artifacts, or replan the work.

Quick Start

Ask the skill to evaluate the change request, analyze the affected project artifacts, and draft a Sprint Change Proposal for review.

Frequently Asked Questions about bmad-correct-course

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

FAQPage Schema
How do I analyze the impact of a mid-sprint change request on existing epics and architecture?

To analyze mid-sprint change impact, review epics, stories, PRD content, architecture, and UX artifacts for downstream effects to identify cross-functional dependencies before adjusting delivery plans.

What is the best way to document a sprint change proposal for stakeholder approval?

The best way to document a sprint change proposal is to generate a structured artifact capturing the change trigger, impact assessment, recommended actions, revised artifact edits, and implementation handoff guidance for review.

How do I manage scope adjustments when a stakeholder requests a new workflow mid-sprint?

Manage mid-sprint scope adjustments by evaluating the change request against current product goals, performing an impact assessment on related artifacts, and drafting a structured proposal to determine whether to revise scope or replan work.

Can I use this process to track approval status and handoff for revised PRD edits?

Yes, the change proposal process includes approval tracking and implementation handoff guidance, ensuring that revised PRD edits and architecture changes are reviewed, approved, and transitioned effectively to the development team.

When should I trigger a formal sprint change proposal instead of informal scope adjustment?

Trigger a formal sprint change proposal for significant mid-sprint issues affecting PRD, epics, architecture, or UX artifacts, where structured impact assessment and approval tracking are required to prevent losing track of delivery plans.

Does mid-sprint impact analysis handle downstream effects across both UX artifacts and architecture documents?

Yes, mid-sprint impact analysis reviews UX artifacts and architecture documents alongside epics and PRD content to capture all downstream effects, ensuring the change proposal accounts for cross-functional dependencies.