bmad-correct-course

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

4|1|Updated Sep 30, 2024
One-click install
npx skills add https://github.com/co-cddo/ndx --skill bmad-correct-course-co-cddo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/co-cddo/ndx/tree/main/_bmad/bmm/workflows/4-implementation/bmad-correct-course
Command: npx skills add https://github.com/co-cddo/ndx --skill bmad-correct-course-co-cddo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps Scrum Masters coordinate significant mid-sprint changes by analyzing impacts across PRD, epics, architecture, and UX artifacts, then producing a concrete Sprint Change Proposal that guides execution and alignment.

Core Features & Use Cases

  • Cross-artifact impact analysis across PRD, Epics, Architecture, and UX documents
  • Structured decision framework with actionable handoff plans
  • Automated generation of Sprint Change Proposal and clear stakeholder responsibilities

Quick Start

Describe the triggering issue to start the Correct Course workflow and generate the Sprint Change Proposal.

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 disrupting agile epics?

Manage mid-sprint changes by analyzing impact across PRD, epics, architecture, and UX documents, then generating a Sprint Change Proposal to guide execution and stakeholder alignment.

What is a Sprint Change Proposal and when do I need one?

A Sprint Change Proposal is a structured document for coordinating significant sprint changes triggered by evolving requirements, providing impact analysis, artifact updates, and clear handoff plans.

How do I analyze the impact of a sprint change on PRD and architecture documents?

Analyze sprint change impact by triggering the Correct Course workflow, which cross-references PRD, epics, architecture, and UX artifacts to produce actionable handoff plans and stakeholder responsibilities.

Can I use this for agile change management with evolving stakeholder requirements?

Yes, this workflow is designed for agile teams during mid-sprint changes triggered by evolving requirements or new stakeholder inputs, producing structured decisions and clear handoff plans.

What's the best way to handle sprint handoff plans after introducing new requirements?

Handle sprint handoffs by generating a structured Sprint Change Proposal that defines artifact updates and clear stakeholder responsibilities, ensuring alignment across the agile team.