bmad-correct-course

Generate a Sprint Change Proposal with cross-artifact impact analysis and handoff details.

3|2|Updated Mar 29, 2024
One-click install
npx skills add https://github.com/josemariafs/MVTools --skill bmad-correct-course-josemariafs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/josemariafs/MVTools/tree/main/.cursor/skills/bmad-correct-course
Command: npx skills add https://github.com/josemariafs/MVTools --skill bmad-correct-course-josemariafs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage significant changes during sprint execution by analyzing impact across all project artifacts and producing a structured Sprint Change Proposal.

Core Features & Use Cases

  • End-to-end workflow for change navigation from trigger to handoff.
  • Generates explicit edit proposals for Stories, PRD, Architecture, and UI/UX, with rationale.
  • Produces a complete Sprint Change Proposal document and an implementation handoff plan.

Quick Start

Describe the triggering issue clearly to start the workflow.

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 sprint changes without losing track of impact across PRD and epics?

To manage sprint changes effectively, you need a structured Sprint Change Proposal that analyzes cross-artifact impact. This workflow assesses changes across PRD, epics, architecture, and UX artifacts to ensure comprehensive traceability and explicit stakeholder handoff readiness.

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

A sprint change proposal is a structured document detailing the ripple effects of mid-sprint adjustments. You need one when significant execution changes occur, requiring explicit edit proposals for Stories, PRD, Architecture, and UI/UX artifacts to maintain project alignment.

How to analyze the impact of a sprint change on architecture and UX artifacts?

To analyze sprint change impact on architecture and UX artifacts, trigger the change navigation workflow with a clear issue description. It generates explicit edit proposals and rationale, producing a complete cross-artifact impact analysis document for the team.

What is the best way to document stakeholder handoffs during a sprint change?

The best way to document stakeholder handoffs during a sprint change is to generate a structured handoff plan. This workflow produces an implementation handoff plan alongside the Sprint Change Proposal, detailing explicit edit proposals and rationale for all affected artifacts.

Do I need existing PRD and epic documents to use a sprint change workflow?

Yes, you need existing PRD, epics, architecture, and UX artifacts to use this sprint change workflow effectively. The process relies on evaluating and proposing explicit edits to these existing project artifacts to generate a complete impact analysis.