[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DNCJHQ7J57HZP45CETE4B4":3,"skill-same:01M6DNCJHQ7J57HZP45CETE4B4":70},{"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":23,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6DNCJHQ7J57HZP45CETE4B4","aac-correct-course",null,"Manage significant changes during sprint execution. Use when the user says \"correct course\" or \"propose sprint change\"","msayedshokry\u002FAgileAgentCanvasExt","msayedshokry","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35009459?v=4","01M6DN5RZZ297CGWTNJ6ERZQ8W","Mohamed Sayed","01M6DN5S4XS7SVCSXZRW2XR0XF",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-correct-course\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[24,25,26,27,28,29,30,31],"correct","aac correct course","change","execution","user","use","manage","sprint","2026-11-10 10:12:30",false,"---\nname: aac-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},"main","473351382920a74eb8f353f979a06f6f05bb5f59","resources\u002F_aac\u002Fskills\u002Faac-correct-course",0,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt","https:\u002F\u002Fgithub.com\u002Fmsayedshokry","2026-08-29 02:00:07",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-correct-course",{"tool":50,"command":51},"bunx","bunx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-correct-course",{"tool":53,"command":54},"pnpm","pnpm dlx skills add msayedshokry\u002FAgileAgentCanvasExt --skill aac-correct-course","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-correct-course\u002FSKILL.md",true,[58,64],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"checklist.md","REFERENCE","参考文档",11634,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-correct-course\u002Fchecklist.md",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"customize.toml","OTHER","其他",1639,"https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Fskills\u002Faac-correct-course\u002Fcustomize.toml",[71,95,114,127,150,166],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":83,"publishedAt":32},"01M6DNRTHE3M1XG3KDJTEF6BG6","bmad-teach-me-testing","Teach testing progressively through structured sessions. Use when user says \"lets learn testing\" or \"I want to study test practices\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Fbmad-teach-me-testing\u002FSKILL.md",[77,82],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[84,85,86,87,88,89,90,91,92,28,29,93,94],"bmad","me","bmad teach me testing","teach me","teach","testing","test","sessions","learn","study","structured",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":102,"publishedAt":32},"01M6DNRG27V77JEGMPMJVRY0Q5","aac-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\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-trace\u002FSKILL.md",[101],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[103,104,90,105,106,107,108,109,110,28,111,29,112,113],"aac testarch trace","trace","quality gate","create","generate","analyze","quality","decision","coverage","test coverage","gate",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":32},"01M6DNR70G1S0DGDSHRWT1S1DD","aac-testarch-test-review","Review test quality using best practices validation. Use when user says \"lets review tests\" or \"I want to evaluate test quality\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-test-review\u002FSKILL.md",[120],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[122,123,90,124,125,109,28,29,126],"review","aac testarch test review","best practices","validation","tests",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":140,"publishedAt":32},"01M6DNQXV8F40EE78ZMWGWRPJM","aac-testarch-test-design","Create system-level or epic-level test plans. Use when the user says \"lets design test plan\" or \"I want to create test strategy\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-test-design\u002FSKILL.md",[133,134,137],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":135,"categoryName":136,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[141,142,90,143,28,106,144,145,146,147,29,148,149],"aac testarch test design","test design","design","test plan","plan","system","strategy","test strategy","plans",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":32},"01M6DNQNG0T7Q5DKV3C03RY35D","aac-testarch-nfr","Audit NFR evidence for performance, security, reliability, and scalability. Use when implementation evidence exists and the user says \"audit NFR evidence\", \"audit NFRs\", or \"evaluate non-functional requirements\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-nfr\u002FSKILL.md",[],[157,158,159,160,161,162,28,163,164,29,165],"aac testarch nfr","reliability","evidence","implementation","scalability","requirements","audit","performance","security",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":32},"01M6DNQDPTGB49D8AAJV4GN2H8","aac-testarch-framework","Initialize test framework with Playwright or Cypress. Use when the user says \"lets setup test framework\" or \"I want to initialize testing framework\"","https:\u002F\u002Fgithub.com\u002Fmsayedshokry\u002FAgileAgentCanvasExt\u002Fblob\u002Fmain\u002Fresources\u002F_aac\u002Ftea\u002Fworkflows\u002Ftestarch\u002Faac-testarch-framework\u002FSKILL.md",[172],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[174,175,176,28,29,177,178,179,90,180,89,181],"aac testarch framework","framework","initialize","testing framework","setup","test framework","playwright","cypress"]