bmad-correct-course
Assess the impact of a significant change during sprint execution across the PRD, epics, architecture, and UX documents, and produce a sprint change proposal. Use when the user says "correct course" or "propose sprint change"
alvin-reyes · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add alvin-reyes/better-agentic-ide --skill bmad-correct-course技能说明
name: bmad-correct-course description: 'Assess the impact of a significant change during sprint execution across the PRD, epics, architecture, and UX documents, and produce a sprint change proposal. Use when the user says "correct course" or "propose sprint change"'
Correct Course - Sprint Change Management Workflow
Goal: Manage significant changes during sprint execution by analyzing impact across all project artifacts and producing a structured Sprint Change Proposal.
Your Role: You are a Developer navigating change management. Analyze the triggering issue, assess impact across PRD, epics, architecture, and UX artifacts, and produce an actionable Sprint Change Proposal with clear handoff.
Conventions
- Bare paths (e.g.
checklist.md) resolve from the skill root. {skill-root}resolves to this skill's installed directory (wherecustomize.tomllives).{project-root}is the nearest folder containing_bmad/, starting at the project working directory and moving up through its parents.{skill-name}resolves to the skill directory's basename.
On Activation
Step 1: Resolve the Workflow Block
Run: node {project-root}/_bmad/ade-runtime.mjs resolve_customization --skill {skill-root} --project-root {project-root} --key workflow
If the script is not found, BMad is not set up here. Offer to run the bmad skill's setup, installing bmad first if you do not have it (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run the command again.
If it fails for any other reason, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
{skill-root}/customize.toml— defaults{project-root}/_bmad/custom/{skill-name}.toml— team overrides{project-root}/_bmad/custom/{skill-name}.user.toml— personal overrides
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.
Step 2: Execute Prepend Steps
Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.
Step 3: Load Persistent Facts
Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.
Step 4: Load Config
Run: node {project-root}/_bmad/ade-runtime.mjs resolve_config --project-root {project-root} --key core.output_folder --key core.active_initiative
-
Script not found, or no
output_folder: BMad is not set up here. Offer to run thebmadskill's setup, installingbmadfirst if you do not have it (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run the command again. -
No
active_initiative: hand off to thebmadskill to set or create one, then run the command again and continue. -
dateas system-generated current datetime -
YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style
-
DOCUMENT OUTPUT: A Sprint Change Proposal with clear, actionable changes.
Step 5: Greet the User
Greet the user.
Step 6: Execute Append Steps
Execute each entry in {workflow.activation_steps_append} in order.
Activation is complete. If activation_steps_prepend or activation_steps_append were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
Paths
default_output_file={output_folder}/{active_initiative}/change-{slug}/change-{slug}.md,{slug}the change's title in kebab-case
Input Files
Look in {output_folder}/{active_initiative}/ first, then {output_folder}/.
| Input | Path | Load Strategy |
|---|---|---|
| PRD | prd-*/prd-*.md | FULL_LOAD |
| Architecture | architecture-*/architecture-*.md | FULL_LOAD |
| UX Design | ux-*/: DESIGN.md and EXPERIENCE.md | FULL_LOAD |
| Spec | spec-*/spec-*.md and the companions it lists | FULL_LOAD |
| Project Context | AGENTS.md in the affected repo (the bmad:context block) | FULL_LOAD |
Execution
Document Discovery - Loading Project Artifacts
Strategy: Course correction needs broad project context to assess change impact accurately. Load all available planning artifacts.
Discovery Process for FULL_LOAD documents (PRD, Architecture, UX Design, Spec):
- Find each document by type - the folder and main file patterns in Input Files
- If the main file is an index of section files beside it:
- Read ALL section files listed in the index
- Process the combined content as a single document
Discovery Process for Project Context:
- Read
AGENTS.mdin the repo the change affects — the block between thebmad:contextmarkers carries the policy, frozen paths, and conventions a course correction must respect. - Follow only the pointers that relate to the impacted areas — nested component files or linked rule files listed under "Where things are". Do not load them all.
- This document is optional — skip if the repo has no
AGENTS.md(greenfield projects).
Fuzzy matching: Be flexible with document names — users may use variations like prd.md, bmm-prd.md, product-requirements.md, etc.
Missing documents: Not all documents may exist. A PRD or a spec is essential; Architecture, UX Design, and Project Context are loaded if available. HALT if neither a PRD nor a spec can be found.
阅读完整来源 ↗