Correct Course
Scannednpx machina-cli add skill PabloLION/bmad-plugin/correct-course --openclawCorrect Course Workflow
Goal: Manage significant changes during sprint execution.
Agent: Scrum Master (Bob) Module: CORE
Execution
Read and follow: ./instructions.md
Validation
After completion, verify against: ./checklist.md
Source
git clone https://github.com/PabloLION/bmad-plugin/blob/main/plugins/bmad/skills/correct-course/SKILL.mdView on GitHub Overview
Correct Course helps Scrum Masters manage significant changes during sprint execution. It keeps the team aligned with updated priorities while preserving sprint cadence. Triggered by phrases like 'correct course' or 'propose sprint change', it guides execution and validation.
How This Skill Works
When invoked, the skill recognizes trigger phrases and engages the Scrum Master (Bob) via the CORE module to implement changes. It follows the documented process in instructions.md for execution and validates results against checklist.md, updating the sprint backlog and goals as needed.
When to Use It
- The user explicitly says 'correct course' to adjust sprint scope mid-sprint.
- A significant impediment or risk requires back- log re-prioritization.
- New information necessitates adjusting sprint goals or deliverables.
- External deadlines or dependencies shift priorities during the sprint.
- Requirements become clearer and prompt re-estimation and backlog updates.
Quick Start
- Step 1: Listen for trigger phrases like 'correct course' or 'propose sprint change'.
- Step 2: Read and follow ./instructions.md to perform the changes via the CORE module.
- Step 3: Validate the outcome by checking against ./checklist.md and updating the sprint backlog and goals.
Best Practices
- Confirm intent and impact with the team before acting.
- Follow the steps outlined in ./instructions.md for execution.
- Communicate proposed changes clearly to the team and stakeholders.
- Update the sprint backlog, sprint goal, and acceptance criteria accordingly.
- Validate outcomes against the checklist in ./checklist.md after changes.
Example Use Cases
- Stakeholder requests removal of a non-critical feature to meet the sprint deadline.
- Discovery of a blocking integration requires re-prioritizing backlog items.
- An external deadline prompts earlier delivery of a subset of backlog items.
- Clarified requirements lead to re-estimation and backlog reordering.
- A critical bug fix takes precedence, prompting backlog reprioritization.