skills.rest
skyoxu
skyoxuCOMMUNITY
Explore all skills by this author →
GitHub

bmad-correct-course

Analyze sprint change impact across project artifacts and generate a Sprint Change Proposal.

Updated Nov 6, 2025
Search Tags:#workflow#epics#handoff#prd#sprint#change-management
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill bmad-correct-course-skyoxu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/bmad-correct-course
Command: npx skills add https://github.com/skyoxu/godotgame --skill bmad-correct-course-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage significant changes during sprint execution by analyzing impact across PRD, epics, architecture, UX artifacts, and producing a structured Sprint Change Proposal that guides handoffs.

Core Features & Use Cases

  • Analyze triggering issues and map impact across project artifacts
  • Generate actionable change proposals with traceable rationale
  • Provide structured handoffs to enable implementation across roles (Dev, PO, PM, Architect)

Quick Start

Describe the triggering sprint change in detail and initiate the Sprint Change Proposal 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 disrupting the current workflow?▼

To manage sprint changes, you need a structured change management process that analyzes the triggering issue across PRDs, epics, architecture, and UX artifacts to produce an actionable Sprint Change Proposal. This ensures traceable rationale and structured handoffs.

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

A Sprint Change Proposal is a structured document generated to navigate significant changes during sprint execution. You need one when a triggering issue arises that impacts project artifacts like PRDs, epics, architecture, or UX designs.

How do I analyze the impact of a sprint change across PRD and epics?▼

Analyzing sprint change impact involves mapping the triggering issue against existing PRDs, epics, architecture, and UX artifacts. This process identifies affected areas and generates clear recommendations for implementation handoffs across roles like Dev, PO, PM, and Architect.

Can I use this workflow for handoffs across different project roles?▼

Yes, the workflow provides structured handoffs specifically designed to enable implementation across various roles including Dev, PO, PM, and Architect. It translates impact analysis into actionable change proposals with traceable rationale for each team member.

What is the best way to document project artifacts affected by a mid-sprint change?▼

The best way to document affected project artifacts is to generate a Sprint Change Proposal that scopes PRDs, epics, architecture, and UX designs. This ensures thorough impact analysis and clear recommendations for structured implementation handoffs.

Related Skills

Explore More Product & Management Skills→
Cbanzaime23Cbanzaime23

bmad-correct-course

Analyze sprint changes to produce a structured Sprint Change Proposal.

Community
Advanced
ChoiHyunjinChoiHyunjin

agile-cycle-trading

Execute agile development cycles for trading applications with risk validation.

Community
Advanced
mschuerigmschuerig

bmad-correct-course

Analyze cross-artifact impacts to generate a Sprint Change Proposal.

Community
Advanced
geekdesign27geekdesign27

bmad-correct-course

Analyze change impacts across project artifacts and generate a Sprint Change Proposal.

Community
Advanced