skills.rest
clovernguyen1010-ship-it
clovernguyen1010-ship-itCOMMUNITY
Explore all skills by this author →
GitHub

bmad-correct-course

Analyze sprint changes and produce a structured Sprint Change Proposal.

Updated Apr 12, 2026
Search Tags:#backlog#handoff#sprint#epic#product-management#change-management#sprint-change
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-correct-course-clovernguyen1010-ship-it
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/_bmad/bmm/workflows/4-implementation/bmad-correct-course
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-correct-course-clovernguyen1010-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Scrum Masters and product teams manage significant changes that arise during sprint execution, ensuring clear guidance and structured handling.

Core Features & Use Cases

  • Guided sprint-change workflow: analyze triggers, assess impact across PRD, epics, architecture, and UX, and craft a formal Sprint Change Proposal.
  • Cross-artifact impact assessment: identify affected artifacts, dependencies, and required adjustments.
  • Handoff-ready outputs: produce actionable recommendations with clear ownership and next steps.

Quick Start

Analyze the triggering issue and generate a Sprint Change Proposal that documents impact and recommended actions.

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 backlog dependencies?▼

To manage sprint changes effectively, analyze the triggering issue to identify cross-artifact impact across epics, PRD, and architecture, then generate a structured Sprint Change Proposal with clear handoff and success criteria.

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

A Sprint Change Proposal is a structured document detailing the impact of sprint changes on artifacts like UX and architecture, required adjustments, and actionable next steps for product teams to ensure clear handoff.

How do I assess cross-artifact impact when a sprint change occurs?▼

Assess cross-artifact impact by analyzing the sprint change trigger and determining how it affects interconnected artifacts such as epics, PRD, architecture, and UX to identify required adjustments and dependencies.

Can I use this workflow for product-management handoff during sprint execution?▼

Yes, this workflow is designed for product-management handoff during sprint execution, producing actionable recommendations with clear ownership and next steps to guide Scrum Masters and product teams through change management.

What is the best way to document epic and PRD adjustments during a sprint change?▼

The best way to document epic and PRD adjustments is to analyze the sprint change triggers, evaluate the cross-artifact impact, and formalize the required adjustments into a structured Sprint Change Proposal.

Related Skills

Explore More Product & Management Skills→
Cbanzaime23Cbanzaime23

bmad-correct-course

Analyze sprint changes to produce a structured Sprint Change Proposal.

Community
Advanced
diegosanchespereira1diegosanchespereira1

bmad-correct-course

Analyze sprint changes and generate a structured Sprint Change Proposal.

Community
Advanced
I-OnlabsI-Onlabs
3

agile-product-owner

Generate INVEST-compliant user stories and plan sprints with a Python script.

Community
Intermediate
MazenMradMazenMrad
1

bmad-correct-course

Produce a formal Sprint Change Proposal for approving significant sprint changes.

Community
Advanced