[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CVV9ZEKBGV7XEABMB3F190":3,"skill-same:01M6CVV9ZEKBGV7XEABMB3F190":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6CVV9ZEKBGV7XEABMB3F190","bmad-correct-course",null,"Manage significant changes during sprint execution. Use when the user says \"correct course\" or \"propose sprint change\"","reformlab\u002FReformLab","reformlab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264161760?v=4","01M6CVRNMTPJRX8QX0P5J8NRZ6","01M6CVRNS5KTS18YC3AZHP1BZ3",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fbmad-correct-course\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[23,24,25,26,27,28,29],"bmad correct course","correct","change","execution","user","use","manage","2026-11-10 10:12:30",false,"---\nname: bmad-correct-course\ndescription: 'Manage significant changes during sprint execution. Use when the user says \"correct course\" or \"propose sprint change\"'\n---\n\n# Correct Course - Sprint Change Management Workflow\n\n**Goal:** Manage significant changes during sprint execution by analyzing impact across all project artifacts and producing a structured Sprint Change Proposal.\n\n**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.\n\n## Conventions\n\n- Bare paths (e.g. `checklist.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, 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:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny 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.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat 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.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n\n- `project_name`, `user_name`\n- `communication_language`, `document_output_language`\n- `user_skill_level`\n- `implementation_artifacts`\n- `planning_artifacts`\n- `project_knowledge`\n- `date` as system-generated current datetime\n- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`\n- Language MUST be tailored to `{user_skill_level}`\n- Generate all documents in `{document_output_language}`\n- DOCUMENT OUTPUT: Updated epics, stories, or PRD sections. Clear, actionable changes. User skill level (`{user_skill_level}`) affects conversation style ONLY, not document updates.\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `default_output_file` = `{planning_artifacts}\u002Fsprint-change-proposal-{date}.md`\n\n## Input Files\n\n| Input | Path | Load Strategy |\n|-------|------|---------------|\n| PRD | `{planning_artifacts}\u002F*prd*.md` (whole) or `{planning_artifacts}\u002F*prd*\u002F*.md` (sharded) | FULL_LOAD |\n| Epics | `{planning_artifacts}\u002F*epic*.md` (whole) or `{planning_artifacts}\u002F*epic*\u002F*.md` (sharded) | FULL_LOAD |\n| Architecture | `{planning_artifacts}\u002F*architecture*.md` (whole) or `{planning_artifacts}\u002F*architecture*\u002F*.md` (sharded) | FULL_LOAD |\n| UX Design | `{planning_artifacts}\u002F*ux*.md` (whole) or `{planning_artifacts}\u002F*ux*\u002F*.md` (sharded) | FULL_LOAD |\n| Spec | `{planning_artifacts}\u002F*spec-*.md` (whole) | FULL_LOAD |\n| Document Project | `{project_knowledge}\u002Findex.md` (sharded) | INDEX_GUIDED |\n\n## Execution\n\n### Document Discovery - Loading Project Artifacts\n\n**Strategy**: Course correction needs broad project context to assess change impact accurately. Load all available planning artifacts.\n\n**Discovery Process for FULL_LOAD documents (PRD, Epics, Architecture, UX Design, Spec):**\n\n1. **Search for whole document first** - Look for files matching the whole-document pattern (e.g., `*prd*.md`, `*epic*.md`, `*architecture*.md`, `*ux*.md`, `*spec-*.md`)\n2. **Check for sharded version** - If whole document not found, look for a directory with `index.md` (e.g., `prd\u002Findex.md`, `epics\u002Findex.md`)\n3. **If sharded version found**:\n   - Read `index.md` to understand the document structure\n   - Read ALL section files listed in the index\n   - Process the combined content as a single document\n4. **Priority**: If both whole and sharded versions exist, use the whole document\n\n**Discovery Process for INDEX_GUIDED documents (Document Project):**\n\n1. **Search for index file** - Look for `{project_knowledge}\u002Findex.md`\n2. **If found**: Read the index to understand available documentation sections\n3. **Selectively load sections** based on relevance to the change being analyzed — do NOT load everything, only sections that relate to the impacted areas\n4. **This document is optional** — skip if `{project_knowledge}` does not exist (greenfield projects)\n\n**Fuzzy matching**: Be flexible with document names — users may use variations like `prd.md`, `bmm-prd.md`, `product-requirements.md`, etc.\n\n**Missing documents**: Not all documents may exist. PRD and Epics are essential; Architecture, UX Design, Spec, and Document Project are loaded if available. HALT if PRD or Epics cannot be found.\n\n\u003Cworkflow>\n\n\u003Cstep n=\"1\" goal=\"Initialize Change Navigation\">\n  \u003Caction>Confirm change trigger and gather user description of the issue\u003C\u002Faction>\n  \u003Caction>Ask: \"What specific issue or change has been identified that requires navigation?\"\u003C\u002Faction>\n  \u003Caction>Verify access to project documents:\u003C\u002Faction>\n    - PRD (Product Requirements Document) — required\n    - Current Epics and Stories — required\n    - Architecture documentation — optional, load if available\n    - UI\u002FUX specifications — optional, load if available\n  \u003Caction>Ask user for mode preference:\u003C\u002Faction>\n    - **Incremental** (recommended): Refine each edit collaboratively\n    - **Batch**: Present all changes at once for review\n  \u003Caction>Store mode selection for use throughout workflow\u003C\u002Faction>\n\n\u003Caction if=\"change trigger is unclear\">HALT: \"Cannot navigate change without clear understanding of the triggering issue. Please provide specific details about what needs to change and why.\"\u003C\u002Faction>\n\n\u003Caction if=\"PRD or Epics are unavailable\">HALT: \"Need access to PRD and Epics to assess change impact. Please ensure these documents are accessible. Architecture and UI\u002FUX will be used if available.\"\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"Execute Change Analysis Checklist\">\n  \u003Caction>Read fully and follow the systematic analysis from: checklist.md\u003C\u002Faction>\n  \u003Caction>Work through each checklist section interactively with the user\u003C\u002Faction>\n  \u003Caction>Record status for each checklist item:\u003C\u002Faction>\n    - [x] Done - Item completed successfully\n    - [N\u002FA] Skip - Item not applicable to this change\n    - [!] Action-needed - Item requires attention or follow-up\n  \u003Caction>Maintain running notes of findings and impacts discovered\u003C\u002Faction>\n  \u003Caction>Present checklist progress after each major section\u003C\u002Faction>\n\n\u003Caction if=\"checklist cannot be completed\">Identify blocking issues and work with user to resolve before continuing\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"Draft Specific Change Proposals\">\n\u003Caction>Based on checklist findings, create explicit edit proposals for each identified artifact\u003C\u002Faction>\n\n\u003Caction>For Story changes:\u003C\u002Faction>\n\n- Show old → new text format\n- Include story ID and section being modified\n- Provide rationale for each change\n- Example format:\n\n  ```\n  Story: [STORY-123] User Authentication\n  Section: Acceptance Criteria\n\n  OLD:\n  - User can log in with email\u002Fpassword\n\n  NEW:\n  - User can log in with email\u002Fpassword\n  - User can enable 2FA via authenticator app\n\n  Rationale: Security requirement identified during implementation\n  ```\n\n\u003Caction>For PRD modifications:\u003C\u002Faction>\n\n- Specify exact sections to update\n- Show current content and proposed changes\n- Explain impact on MVP scope and requirements\n\n\u003Caction>For Architecture changes:\u003C\u002Faction>\n\n- Identify affected components, patterns, or technology choices\n- Describe diagram updates needed\n- Note any ripple effects on other components\n\n\u003Caction>For UI\u002FUX specification updates:\u003C\u002Faction>\n\n- Reference specific screens or components\n- Show wireframe or flow changes needed\n- Connect changes to user experience impact\n\n\u003Ccheck if=\"mode is Incremental\">\n  \u003Caction>Present each edit proposal individually\u003C\u002Faction>\n  \u003Cask>Review and refine this change? Options: Approve [a], Edit [e], Skip [s]\u003C\u002Fask>\n  \u003Caction>Iterate on each proposal based on user feedback\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Caction if=\"mode is Batch\">Collect all edit proposals and present together at end of step\u003C\u002Faction>\n\n\u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"Generate Sprint Change Proposal\">\n\u003Caction>Compile comprehensive Sprint Change Proposal document with following sections:\u003C\u002Faction>\n\n\u003Caction>Section 1: Issue Summary\u003C\u002Faction>\n\n- Clear problem statement describing what triggered the change\n- Context about when\u002Fhow the issue was discovered\n- Evidence or examples demonstrating the issue\n\n\u003Caction>Section 2: Impact Analysis\u003C\u002Faction>\n\n- Epic Impact: Which epics are affected and how\n- Story Impact: Current and future stories requiring changes\n- Artifact Conflicts: PRD, Architecture, UI\u002FUX documents needing updates\n- Technical Impact: Code, infrastructure, or deployment implications\n\n\u003Caction>Section 3: Recommended Approach\u003C\u002Faction>\n\n- Present chosen path forward from checklist evaluation:\n  - Direct Adjustment: Modify\u002Fadd stories within existing plan\n  - Potential Rollback: Revert completed work to simplify resolution\n  - MVP Review: Reduce scope or modify goals\n- Provide clear rationale for recommendation\n- Include effort estimate, risk assessment, and timeline impact\n\n\u003Caction>Section 4: Detailed Change Proposals\u003C\u002Faction>\n\n- Include all refined edit proposals from Step 3\n- Group by artifact type (Stories, PRD, Architecture, UI\u002FUX)\n- Ensure each change includes before\u002Fafter and justification\n\n\u003Caction>Section 5: Implementation Handoff\u003C\u002Faction>\n\n- Categorize change scope:\n  - Minor: Direct implementation by Developer agent\n  - Moderate: Backlog reorganization needed (PO\u002FDEV)\n  - Major: Fundamental replan required (PM\u002FArchitect)\n- Specify handoff recipients and their responsibilities\n- Define success criteria for implementation\n\n\u003Caction>Present complete Sprint Change Proposal to user\u003C\u002Faction>\n\u003Caction>Write Sprint Change Proposal document to {default_output_file}\u003C\u002Faction>\n\u003Cask>Review complete proposal. Continue [c] or Edit [e]?\u003C\u002Fask>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"Finalize and Route for Implementation\">\n\u003Caction>Get explicit user approval for complete proposal\u003C\u002Faction>\n\u003Cask>Do you approve this Sprint Change Proposal for implementation? (yes\u002Fno\u002Frevise)\u003C\u002Fask>\n\n\u003Ccheck if=\"no or revise\">\n  \u003Caction>Gather specific feedback on what needs adjustment\u003C\u002Faction>\n  \u003Caction>Return to appropriate step to address concerns\u003C\u002Faction>\n  \u003Cgoto step=\"3\">If changes needed to edit proposals\u003C\u002Fgoto>\n  \u003Cgoto step=\"4\">If changes needed to overall proposal structure\u003C\u002Fgoto>\n\n\u003C\u002Fcheck>\n\n\u003Ccheck if=\"yes the proposal is approved by the user\">\n  \u003Caction>Finalize Sprint Change Proposal document\u003C\u002Faction>\n  \u003Caction>Determine change scope classification:\u003C\u002Faction>\n\n- **Minor**: Can be implemented directly by Developer agent\n- **Moderate**: Requires backlog reorganization and PO\u002FDEV coordination\n- **Major**: Needs fundamental replan with PM\u002FArchitect involvement\n\n\u003Caction>Provide appropriate handoff based on scope:\u003C\u002Faction>\n\n\u003C\u002Fcheck>\n\n\u003Ccheck if=\"Minor scope\">\n  \u003Caction>Route to: Developer agent for direct implementation\u003C\u002Faction>\n  \u003Caction>Deliverables: Finalized edit proposals and implementation tasks\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Ccheck if=\"Moderate scope\">\n  \u003Caction>Route to: Product Owner \u002F Developer agents\u003C\u002Faction>\n  \u003Caction>Deliverables: Sprint Change Proposal + backlog reorganization plan\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Ccheck if=\"Major scope\">\n  \u003Caction>Route to: Product Manager \u002F Solution Architect\u003C\u002Faction>\n  \u003Caction>Deliverables: Complete Sprint Change Proposal + escalation notice\u003C\u002Faction>\n\n\u003Caction>Confirm handoff completion and next steps with user\u003C\u002Faction>\n\u003Caction>Document handoff in workflow execution log\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003C\u002Fstep>\n\n\u003Cstep n=\"6\" goal=\"Workflow Completion\">\n\u003Caction>Summarize workflow execution:\u003C\u002Faction>\n  - Issue addressed: {{change_trigger}}\n  - Change scope: {{scope_classification}}\n  - Artifacts modified: {{list_of_artifacts}}\n  - Routed to: {{handoff_recipients}}\n\n\u003Caction>Confirm all deliverables produced:\u003C\u002Faction>\n\n- Sprint Change Proposal document\n- Specific edit proposals with before\u002Fafter\n- Implementation handoff plan\n\n\u003Caction>Report workflow completion to user with personalized message: \"Correct Course workflow complete, {user_name}!\"\u003C\u002Faction>\n\u003Caction>Remind user of success criteria and next steps for Developer agent\u003C\u002Faction>\n\u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C\u002Fworkflow>\n","# Correct Course - Sprint Change Management Workflow\n\n**Goal:** Manage significant changes during sprint execution by analyzing impact across all project artifacts and producing a structured Sprint Change Proposal.\n\n**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.\n\n## Conventions\n\n- Bare paths (e.g. `checklist.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, 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:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny 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.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat 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.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n\n- `project_name`, `user_name`\n- `communication_language`, `document_output_language`\n- `user_skill_level`\n- `implementation_artifacts`\n- `planning_artifacts`\n- `project_knowledge`\n- `date` as system-generated current datetime\n- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`\n- Language MUST be tailored to `{user_skill_level}`\n- Generate all documents in `{document_output_language}`\n- DOCUMENT OUTPUT: Updated epics, stories, or PRD sections. Clear, actionable changes. User skill level (`{user_skill_level}`) affects conversation style ONLY, not document updates.\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `default_output_file` = `{planning_artifacts}\u002Fsprint-change-proposal-{date}.md`\n\n## Input Files\n\n| Input | Path | Load Strategy |\n|-------|------|---------------|\n| PRD | `{planning_artifacts}\u002F*prd*.md` (whole) or `{planning_artifacts}\u002F*prd*\u002F*.md` (sharded) | FULL_LOAD |\n| Epics | `{planning_artifacts}\u002F*epic*.md` (whole) or `{planning_artifacts}\u002F*epic*\u002F*.md` (sharded) | FULL_LOAD |\n| Architecture | `{planning_artifacts}\u002F*architecture*.md` (whole) or `{planning_artifacts}\u002F*architecture*\u002F*.md` (sharded) | FULL_LOAD |\n| UX Design | `{planning_artifacts}\u002F*ux*.md` (whole) or `{planning_artifacts}\u002F*ux*\u002F*.md` (sharded) | FULL_LOAD |\n| Spec | `{planning_artifacts}\u002F*spec-*.md` (whole) | FULL_LOAD |\n| Document Project | `{project_knowledge}\u002Findex.md` (sharded) | INDEX_GUIDED |\n\n## Execution\n\n### Document Discovery - Loading Project Artifacts\n\n**Strategy**: Course correction needs broad project context to assess change impact accurately. Load all available planning artifacts.\n\n**Discovery Process for FULL_LOAD documents (PRD, Epics, Architecture, UX Design, Spec):**\n\n1. **Search for whole document first** - Look for files matching the whole-document pattern (e.g., `*prd*.md`, `*epic*.md`, `*architecture*.md`, `*ux*.md`, `*spec-*.md`)\n2. **Check for sharded version** - If whole document not found, look for a directory with `index.md` (e.g., `prd\u002Findex.md`, `epics\u002Findex.md`)\n3. **If sharded version found**:\n   - Read `index.md` to understand the document structure\n   - Read ALL section files listed in the index\n   - Process the combined content as a single document\n4. **Priority**: If both whole and sharded versions exist, use the whole document\n\n**Discovery Process for INDEX_GUIDED documents (Document Project):**\n\n1. **Search for index file** - Look for `{project_knowledge}\u002Findex.md`\n2. **If found**: Read the index to understand available documentation sections\n3. **Selectively load sections** based on relevance to the change being analyzed — do NOT load everything, only sections that relate to the impacted areas\n4. **This document is optional** — skip if `{project_knowledge}` does not exist (greenfield projects)\n\n**Fuzzy matching**: Be flexible with document names — users may use variations like `prd.md`, `bmm-prd.md`, `product-requirements.md`, etc.\n\n**Missing documents**: Not all documents may exist. PRD and Epics are essential; Architecture, UX Design, Spec, and Document Project are loaded if available. HALT if PRD or Epics cannot be found.\n\n\u003Cworkflow>\n\n\u003Cstep n=\"1\" goal=\"Initialize Change Navigation\">\n  \u003Caction>Confirm change trigger and gather user description of the issue\u003C\u002Faction>\n  \u003Caction>Ask: \"What specific issue or change has been identified that requires navigation?\"\u003C\u002Faction>\n  \u003Caction>Verify access to project documents:\u003C\u002Faction>\n    - PRD (Product Requirements Document) — required\n    - Current Epics and Stories — required\n    - Architecture documentation — optional, load if available\n    - UI\u002FUX specifications — optional, load if available\n  \u003Caction>Ask user for mode preference:\u003C\u002Faction>\n    - **Incremental** (recommended): Refine each edit collaboratively\n    - **Batch**: Present all changes at once for review\n  \u003Caction>Store mode selection for use throughout workflow\u003C\u002Faction>\n\n\u003Caction if=\"change trigger is unclear\">HALT: \"Cannot navigate change without clear understanding of the triggering issue. Please provide specific details about what needs to change and why.\"\u003C\u002Faction>\n\n\u003Caction if=\"PRD or Epics are unavailable\">HALT: \"Need access to PRD and Epics to assess change impact. Please ensure these documents are accessible. Architecture and UI\u002FUX will be used if available.\"\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"Execute Change Analysis Checklist\">\n  \u003Caction>Read fully and follow the systematic analysis from: checklist.md\u003C\u002Faction>\n  \u003Caction>Work through each checklist section interactively with the user\u003C\u002Faction>\n  \u003Caction>Record status for each checklist item:\u003C\u002Faction>\n    - [x] Done - Item completed successfully\n    - [N\u002FA] Skip - Item not applicable to this change\n    - [!] Action-needed - Item requires attention or follow-up\n  \u003Caction>Maintain running notes of findings and impacts discovered\u003C\u002Faction>\n  \u003Caction>Present checklist progress after each major section\u003C\u002Faction>\n\n\u003Caction if=\"checklist cannot be completed\">Identify blocking issues and work with user to resolve before continuing\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"Draft Specific Change Proposals\">\n\u003Caction>Based on checklist findings, create explicit edit proposals for each identified artifact\u003C\u002Faction>\n\n\u003Caction>For Story changes:\u003C\u002Faction>\n\n- Show old → new text format\n- Include story ID and section being modified\n- Provide rationale for each change\n- Example format:\n\n  ```\n  Story: [STORY-123] User Authentication\n  Section: Acceptance Criteria\n\n  OLD:\n  - User can log in with email\u002Fpassword\n\n  NEW:\n  - User can log in with email\u002Fpassword\n  - User can enable 2FA via authenticator app\n\n  Rationale: Security requirement identified during implementation\n  ```\n\n\u003Caction>For PRD modifications:\u003C\u002Faction>\n\n- Specify exact sections to update\n- Show current content and proposed changes\n- Explain impact on MVP scope and requirements\n\n\u003Caction>For Architecture changes:\u003C\u002Faction>\n\n- Identify affected components, patterns, or technology choices\n- Describe diagram updates needed\n- Note any ripple effects on other components\n\n\u003Caction>For UI\u002FUX specification updates:\u003C\u002Faction>\n\n- Reference specific screens or components\n- Show wireframe or flow changes needed\n- Connect changes to user experience impact\n\n\u003Ccheck if=\"mode is Incremental\">\n  \u003Caction>Present each edit proposal individually\u003C\u002Faction>\n  \u003Cask>Review and refine this change? Options: Approve [a], Edit [e], Skip [s]\u003C\u002Fask>\n  \u003Caction>Iterate on each proposal based on user feedback\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Caction if=\"mode is Batch\">Collect all edit proposals and present together at end of step\u003C\u002Faction>\n\n\u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"Generate Sprint Change Proposal\">\n\u003Caction>Compile comprehensive Sprint Change Proposal document with following sections:\u003C\u002Faction>\n\n\u003Caction>Section 1: Issue Summary\u003C\u002Faction>\n\n- Clear problem statement describing what triggered the change\n- Context about when\u002Fhow the issue was discovered\n- Evidence or examples demonstrating the issue\n\n\u003Caction>Section 2: Impact Analysis\u003C\u002Faction>\n\n- Epic Impact: Which epics are affected and how\n- Story Impact: Current and future stories requiring changes\n- Artifact Conflicts: PRD, Architecture, UI\u002FUX documents needing updates\n- Technical Impact: Code, infrastructure, or deployment implications\n\n\u003Caction>Section 3: Recommended Approach\u003C\u002Faction>\n\n- Present chosen path forward from checklist evaluation:\n  - Direct Adjustment: Modify\u002Fadd stories within existing plan\n  - Potential Rollback: Revert completed work to simplify resolution\n  - MVP Review: Reduce scope or modify goals\n- Provide clear rationale for recommendation\n- Include effort estimate, risk assessment, and timeline impact\n\n\u003Caction>Section 4: Detailed Change Proposals\u003C\u002Faction>\n\n- Include all refined edit proposals from Step 3\n- Group by artifact type (Stories, PRD, Architecture, UI\u002FUX)\n- Ensure each change includes before\u002Fafter and justification\n\n\u003Caction>Section 5: Implementation Handoff\u003C\u002Faction>\n\n- Categorize change scope:\n  - Minor: Direct implementation by Developer agent\n  - Moderate: Backlog reorganization needed (PO\u002FDEV)\n  - Major: Fundamental replan required (PM\u002FArchitect)\n- Specify handoff recipients and their responsibilities\n- Define success criteria for implementation\n\n\u003Caction>Present complete Sprint Change Proposal to user\u003C\u002Faction>\n\u003Caction>Write Sprint Change Proposal document to {default_output_file}\u003C\u002Faction>\n\u003Cask>Review complete proposal. Continue [c] or Edit [e]?\u003C\u002Fask>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"Finalize and Route for Implementation\">\n\u003Caction>Get explicit user approval for complete proposal\u003C\u002Faction>\n\u003Cask>Do you approve this Sprint Change Proposal for implementation? (yes\u002Fno\u002Frevise)\u003C\u002Fask>\n\n\u003Ccheck if=\"no or revise\">\n  \u003Caction>Gather specific feedback on what needs adjustment\u003C\u002Faction>\n  \u003Caction>Return to appropriate step to address concerns\u003C\u002Faction>\n  \u003Cgoto step=\"3\">If changes needed to edit proposals\u003C\u002Fgoto>\n  \u003Cgoto step=\"4\">If changes needed to overall proposal structure\u003C\u002Fgoto>\n\n\u003C\u002Fcheck>\n\n\u003Ccheck if=\"yes the proposal is approved by the user\">\n  \u003Caction>Finalize Sprint Change Proposal document\u003C\u002Faction>\n  \u003Caction>Determine change scope classification:\u003C\u002Faction>\n\n- **Minor**: Can be implemented directly by Developer agent\n- **Moderate**: Requires backlog reorganization and PO\u002FDEV coordination\n- **Major**: Needs fundamental replan with PM\u002FArchitect involvement\n\n\u003Caction>Provide appropriate handoff based on scope:\u003C\u002Faction>\n\n\u003C\u002Fcheck>\n\n\u003Ccheck if=\"Minor scope\">\n  \u003Caction>Route to: Developer agent for direct implementation\u003C\u002Faction>\n  \u003Caction>Deliverables: Finalized edit proposals and implementation tasks\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Ccheck if=\"Moderate scope\">\n  \u003Caction>Route to: Product Owner \u002F Developer agents\u003C\u002Faction>\n  \u003Caction>Deliverables: Sprint Change Proposal + backlog reorganization plan\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003Ccheck if=\"Major scope\">\n  \u003Caction>Route to: Product Manager \u002F Solution Architect\u003C\u002Faction>\n  \u003Caction>Deliverables: Complete Sprint Change Proposal + escalation notice\u003C\u002Faction>\n\n\u003Caction>Confirm handoff completion and next steps with user\u003C\u002Faction>\n\u003Caction>Document handoff in workflow execution log\u003C\u002Faction>\n\u003C\u002Fcheck>\n\n\u003C\u002Fstep>\n\n\u003Cstep n=\"6\" goal=\"Workflow Completion\">\n\u003Caction>Summarize workflow execution:\u003C\u002Faction>\n  - Issue addressed: {{change_trigger}}\n  - Change scope: {{scope_classification}}\n  - Artifacts modified: {{list_of_artifacts}}\n  - Routed to: {{handoff_recipients}}\n\n\u003Caction>Confirm all deliverables produced:\u003C\u002Faction>\n\n- Sprint Change Proposal document\n- Specific edit proposals with before\u002Fafter\n- Implementation handoff plan\n\n\u003Caction>Report workflow completion to user with personalized message: \"Correct Course workflow complete, {user_name}!\"\u003C\u002Faction>\n\u003Caction>Remind user of success criteria and next steps for Developer agent\u003C\u002Faction>\n\u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C\u002Fworkflow>\n",{"name":5,"description":7},"master","314a64e40d9abca764698290593908a736500b30",".agents\u002Fskills\u002Fbmad-correct-course",0,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab","https:\u002F\u002Fdocs.reform-lab.eu\u002F","https:\u002F\u002Fgithub.com\u002Freformlab","https:\u002F\u002Freform-lab.eu\u002F","See who your policy actually helps","2026-05-25 03:50:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add reformlab\u002FReformLab --skill bmad-correct-course",{"tool":51,"command":52},"bunx","bunx skills add reformlab\u002FReformLab --skill bmad-correct-course",{"tool":54,"command":55},"pnpm","pnpm dlx skills add reformlab\u002FReformLab --skill bmad-correct-course","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fbmad-correct-course\u002FSKILL.md",true,[59,65],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"checklist.md","REFERENCE","参考文档",11634,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fbmad-correct-course\u002Fchecklist.md",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"customize.toml","OTHER","其他",1640,"https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fbmad-correct-course\u002Fcustomize.toml",[72,97,111,135,150,165],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":30},"01M6FQK4CGE9096SN2JRE7DA8H","bmad-assist-help","Explain how bmad-assist works in this project by inspecting the local bmad-assist config, sprint status, epics, state, runs, prompts, logs, and relevant source code. Use when the user asks how bmad-assist behaves, how it reads epics and stories, why a run resumed or failed, what files are authoritative, or to investigate bmad-assist execution in the current repo.","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F_bmad\u002Fcore\u002Fskills\u002Fbmad-assist-help\u002FSKILL.md",[],[79,80,81,82,83,84,85,86,87,26,88,89,90,91,92,28,93,94,95,96],"help","bmad","bmad assist help","config","run","investigate","code","state","logs","relevant","how","why","explain","repo","files","local","project","sprint",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":30},"01M6FQK133CMP4ZT00TW6S7TB1","bmad-fix-ci","Diagnose and fix GitHub CI failures locally. Use when the user says 'fix ci' or 'fix ci failures'.","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F_bmad\u002Fbmm\u002Fskills\u002Fbmad-fix-ci\u002FSKILL.md",[],[104,80,105,106,107,27,28,108,109,110],"bmad fix ci","ci","fix ci","fix","diagnose","fix ci failures","github",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":122,"publishedAt":30},"01M6FQJW69SATT3C9741MT2KJH","bmad-workflow-builder","Builds, converts, and analyzes workflows and skills. Use when the user requests to \"build a workflow\", \"modify a workflow\", \"quality check workflow\", \"analyze skill\", or \"convert a skill\".","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-workflow-builder\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[123,124,80,125,126,127,128,129,130,131,27,28,132,133,134],"bmad workflow builder","workflow","builder","workflow builder","workflows","convert","analyze","quality","check","build","quality check","requests",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":144,"publishedAt":30},"01M6FQJQMT5GW37ANR711FCBJR","bmad-validate-prd","Validate a PRD against standards. Use when the user says \"validate this PRD\" or \"run PRD validation\"","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-validate-prd\u002FSKILL.md",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理",[80,145,146,147,27,83,148,28,149],"bmad validate prd","prd","validate","validation","standards",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":30},"01M6FQJMCSRVGCG65DAKKGW0M1","bmad-ux-designer","ux-designer agent","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-ux-designer\u002FSKILL.md",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000032","设计师",[80,160,161,162,163,164],"bmad ux designer","UX Designer","designer","bmad ux","ux",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":30},"01M6FQJDFKBXTWMBJD29FAC8TA","bmad-testarch-trace","Generate traceability matrix and quality gate decision. Use when the user says \"lets create traceability matrix\" or \"I want to analyze test coverage\"","https:\u002F\u002Fgithub.com\u002Freformlab\u002FReformLab\u002Fblob\u002Fmaster\u002F.opencode\u002Fskills\u002Fbmad-testarch-trace\u002FSKILL.md",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000008","测试与质量",[175,176,177,80,178,179,180,181,129,130,182,27,183,28,184,185,186],"trace","bmad testarch","bmad testarch trace","test","quality gate","create","generate","decision","coverage","test coverage","gate","traceability"]