One-click install
npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-correct-course-devalexanderdaza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-correct-course
Source: https://github.com/devalexanderdaza/bmad-any/tree/main/.agents/skills/bmad-correct-course
Command: npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-correct-course-devalexanderdaza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unplanned changes during active sprint execution often create misalignment across project artifacts, waste completed work, and derail timelines if not managed with a consistent, structured process.

Core Features & Use Cases

  • Systematic Impact Analysis: Guides you through evaluating change impact across PRDs, epics, architecture, UX, and other project artifacts using a structured checklist.
  • Collaborative Edit Drafting: Supports both incremental (step-by-step review) and batch (full review at once) modes to draft precise, justified edits for all affected artifacts.
  • Formal Proposal Generation: Compiles all findings into a comprehensive Sprint Change Proposal with clear implementation handoff instructions based on change scope. Use case: For example, if a critical security requirement emerges mid-sprint, this skill helps you assess which epics are affected, update relevant user stories and PRD sections, and route the change to the correct team members for implementation.

Quick Start

Use the bmad-correct-course skill to analyze the impact of the identified sprint change and generate a formal, approved 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 active development timelines?

Manage mid-sprint changes by performing systematic impact analysis across project artifacts to produce structured sprint change proposals, ensuring unplanned requirements are evaluated and formally approved before implementation.

What is the best way to assess the impact of unplanned sprint requirements on existing project artifacts?

Assess impact of unplanned requirements using a structured checklist to evaluate changes across PRDs, epics, architecture, and UX documentation, identifying all affected components before drafting collaborative edits.

How do I draft collaborative edit proposals for product requirements during sprint execution?

Draft collaborative edit proposals for product requirements using incremental or batch review modes to generate precise, justified updates for all affected artifacts during active sprint execution.

When should I use a formal sprint change proposal instead of direct epic updates?

Use a formal sprint change proposal when unplanned requirements, technical limitations, or strategic pivots require mid-sprint updates, ensuring systematic change impact assessment and clear implementation handoff to appropriate team roles.

Can I generate implementation handoff instructions based on the scope of a sprint change?

Generate implementation handoff instructions by compiling impact analysis findings and collaborative edit drafts into a comprehensive sprint change proposal, routing specific change scope details to the correct project team members for execution.