[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79PHDW9PRN7JSVAJ80PJP4Z":3,"skill-same:01M79PHDW9PRN7JSVAJ80PJP4Z":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79PHDW9PRN7JSVAJ80PJP4Z","bmad-correct-course",null,"Manage significant changes during sprint execution. Use when the user says \"correct course\" or \"propose sprint change\"","OrigoStudio\u002Forigo-design","OrigoStudio","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F256943203?v=4","01M79P1MQHVZ4PTXBQVM11Q00S","Origo Studio","01M79P1MR8S30QEEM0Z6MGX1MA",1,"MIT","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-correct-course\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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. 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.\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. 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.\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},"main","5d8b301b16a0b47e4c97f8c6d68ad82e0f86be2c",".agents\u002Fskills\u002Fbmad-correct-course",0,"https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design","https:\u002F\u002Fgithub.com\u002FOrigoStudio","Engineering ideas into products","2026-10-23 00:02:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add OrigoStudio\u002Forigo-design --skill bmad-correct-course",{"tool":38,"command":39},"bunx","bunx skills add OrigoStudio\u002Forigo-design --skill bmad-correct-course",{"tool":41,"command":42},"pnpm","pnpm dlx skills add OrigoStudio\u002Forigo-design --skill bmad-correct-course","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-correct-course\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"checklist.md","REFERENCE","参考文档",11634,"https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-correct-course\u002Fchecklist.md",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"customize.toml","OTHER","其他",1640,"https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-correct-course\u002Fcustomize.toml",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79PWH7HW9TE5FTCHJ1W968C","wds-agent-saga-analyst","Strategic business analyst and product discovery partner for WDS. Use when the user asks to talk to Saga or requests the WDS analyst.","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-agent-saga-analyst\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79PWF5EAQTMC3XZBEFGP3HW","wds-agent-mimir-builder","Implementation agent. Owns the tech audit, the PRD, and the build. Reads Freya's Work Orders and turns them into working code — one verified task at a time.","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-agent-mimir-builder\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79PWCR1845ETM01V6SKVDMN","wds-agent-freya-ux","Strategic UX designer and design thinking partner for WDS. Use when the user asks to talk to Freya or requests the WDS designer.","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-agent-freya-ux\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79PW9MEM3299WHP4DN0AS46","wds-8-product-evolution","Brownfield improvements — the full WDS pipeline in miniature for existing products","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-8-product-evolution\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79PW81V0VQJJP0A9A47WR8N","wds-7-design-system","Create, import, browse, and maintain design system components and tokens","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-7-design-system\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79PW550F0KPHSWF5Z8Z529B","wds-6-asset-generation","Generate visual and text assets from specifications through AI-powered creative production","https:\u002F\u002Fgithub.com\u002FOrigoStudio\u002Forigo-design\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwds-6-asset-generation\u002FSKILL.md",[],[]]