bmad-method 6.1.1-next.8 → 6.2.0

package/src/bmm/workflows/4-implementation/bmad-correct-course/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bmad-correct-course
+description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
+---
+
+Follow the instructions in ./workflow.md.

package/src/bmm/workflows/4-implementation/{correct-course → bmad-correct-course}/checklist.md

@@ -1,6 +1,6 @@
 # Change Navigation Checklist
 
-<critical>This checklist is executed as part of: {project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.md</critical>
+<critical>This checklist is executed as part of: ./workflow.md</critical>
 <critical>Work through each section systematically with the user, recording findings and impacts</critical>
 
 <checklist>

package/src/bmm/workflows/4-implementation/{correct-course → bmad-correct-course}/workflow.md

@@ -1,8 +1,3 @@
----
-name: correct-course
-description: 'Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"'
----
-
 # Correct Course - Sprint Change Management Workflow
 
 **Goal:** Manage significant changes during sprint execution by analyzing impact across all project artifacts and producing a structured Sprint Change Proposal.
@@ -31,8 +26,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Paths
 
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/4-implementation/correct-course`
-- `checklist` = `{installed_path}/checklist.md`
 - `default_output_file` = `{planning_artifacts}/sprint-change-proposal-{date}.md`
 
 ### Input Files
@@ -48,7 +41,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Context
 
-- `project_context` = `**/project-context.md` (load if exists)
+- Load `**/project-context.md` if it exists
 
 ---
 
@@ -82,7 +75,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 <workflow>
 
 <step n="1" goal="Initialize Change Navigation">
-  <action>Load {project_context} for coding standards and project-wide patterns (if exists)</action>
+  <action>Load **/project-context.md for coding standards and project-wide patterns (if exists)</action>
   <action>Confirm change trigger and gather user description of the issue</action>
   <action>Ask: "What specific issue or change has been identified that requires navigation?"</action>
   <action>Verify access to required project documents:</action>
@@ -101,7 +94,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 </step>
 
 <step n="2" goal="Execute Change Analysis Checklist">
-  <action>Read fully and follow the systematic analysis from: {checklist}</action>
+  <action>Read fully and follow the systematic analysis from: checklist.md</action>
   <action>Work through each checklist section interactively with the user</action>
   <action>Record status for each checklist item:</action>
     - [x] Done - Item completed successfully

package/src/bmm/workflows/4-implementation/bmad-create-story/SKILL.md

@@ -3,4 +3,4 @@ name: bmad-create-story
 description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/bmm/workflows/4-implementation/bmad-create-story/checklist.md

@@ -36,7 +36,7 @@ This is a COMPETITION to create the **ULTIMATE story context** that makes LLM de
 - The workflow framework will automatically:
   - Load this checklist file
   - Load the newly created story file (`{story_file_path}`)
-  - Load workflow variables from `{installed_path}/workflow.md`
+  - Load workflow variables from `./workflow.md`
   - Execute the validation process
 
 ### **When Running in Fresh Context:**
@@ -61,7 +61,7 @@ You will systematically re-do the entire story creation process, but with a crit
 
 ### **Step 1: Load and Understand the Target**
 
-1. **Load the workflow configuration**: `{installed_path}/workflow.md` for variable inclusion
+1. **Load the workflow configuration**: `./workflow.md` for variable inclusion
 2. **Load the story file**: `{story_file_path}` (provided by user or discovered)
 3. **Extract metadata**: epic_num, story_num, story_key, story_title from story file
 4. **Resolve all workflow variables**: implementation_artifacts, epics_file, architecture_file, etc.

package/src/bmm/workflows/4-implementation/bmad-create-story/workflow.md

@@ -1,8 +1,3 @@
----
-name: bmad-create-story
-description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"'
----
-
 # Create Story Workflow
 
 **Goal:** Create a comprehensive story file that gives the dev agent everything needed for flawless implementation.
@@ -32,9 +27,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Paths
 
-- `installed_path` = `.`
-- `template` = `./template.md`
-- `validation` = `./checklist.md`
 - `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
 - `epics_file` = `{planning_artifacts}/epics.md`
 - `prd_file` = `{planning_artifacts}/prd.md`
@@ -217,10 +209,10 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 </step>
 
 <step n="2" goal="Load and analyze core artifacts">
-  <critical>🔬 EXHAUSTIVE ARTIFACT ANALYSIS - This is where you prevent future developer fuckups!</critical>
+  <critical>🔬 EXHAUSTIVE ARTIFACT ANALYSIS - This is where you prevent future developer mistakes!</critical>
 
   <!-- Load all available content through discovery protocol -->
-  <action>Read fully and follow `{installed_path}/discover-inputs.md` to load all input files</action>
+  <action>Read fully and follow `./discover-inputs.md` to load all input files</action>
   <note>Available content: {epics_content}, {prd_content}, {architecture_content}, {ux_content},
   {project_context}</note>
 
@@ -352,7 +344,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 </step>
 
 <step n="6" goal="Update sprint status and finalize">
-  <action>Validate the newly created story file {story_file} against {installed_path}/checklist.md and apply any required fixes before finalizing</action>
+  <action>Validate the newly created story file {default_output_file} against `./checklist.md` and apply any required fixes before finalizing</action>
   <action>Save story document unconditionally</action>
 
   <!-- Update sprint status -->

package/src/bmm/workflows/4-implementation/bmad-dev-story/SKILL.md

@@ -3,4 +3,4 @@ name: bmad-dev-story
 description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/bmm/workflows/4-implementation/bmad-dev-story/workflow.md

@@ -27,7 +27,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Paths
 
-- `validation` = `./checklist.md`
 - `story_file` = `` (explicit story path; auto-discovered if empty)
 - `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
 

package/src/bmm/workflows/4-implementation/bmad-retrospective/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bmad-retrospective
+description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"'
+---
+
+Follow the instructions in ./workflow.md.

package/src/bmm/workflows/4-implementation/{retrospective → bmad-retrospective}/workflow.md

@@ -1,8 +1,3 @@
----
-name: retrospective
-description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"'
----
-
 # Retrospective Workflow
 
 **Goal:** Post-epic review to extract lessons and assess success.
@@ -42,7 +37,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Paths
 
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/4-implementation/retrospective`
 - `sprint_status_file` = `{implementation_artifacts}/sprint-status.yaml`
 
 ### Input Files

package/src/bmm/workflows/4-implementation/bmad-sprint-planning/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bmad-sprint-planning
+description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"'
+---
+
+Follow the instructions in ./workflow.md.

package/src/bmm/workflows/4-implementation/bmad-sprint-planning/bmad-skill-manifest.yaml

@@ -0,0 +1 @@
+type: skill

package/src/bmm/workflows/4-implementation/{sprint-planning → bmad-sprint-planning}/workflow.md

@@ -1,8 +1,3 @@
----
-name: sprint-planning
-description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"'
----
-
 # Sprint Planning Workflow
 
 **Goal:** Generate sprint status tracking from epics, detecting current story statuses and building a complete sprint-status.yaml file.
@@ -26,9 +21,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Paths
 
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning`
-- `template` = `{installed_path}/sprint-status-template.yaml`
-- `checklist` = `{installed_path}/checklist.md`
 - `tracking_system` = `file-system`
 - `project_key` = `NOKEY`
 - `story_location` = `{implementation_artifacts}`

package/src/bmm/workflows/4-implementation/bmad-sprint-status/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bmad-sprint-status
+description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"'
+---
+
+Follow the instructions in ./workflow.md.

package/src/bmm/workflows/4-implementation/bmad-sprint-status/bmad-skill-manifest.yaml

@@ -0,0 +1 @@
+type: skill

package/src/bmm/workflows/4-implementation/{sprint-status → bmad-sprint-status}/workflow.md

@@ -1,8 +1,3 @@
----
-name: sprint-status
-description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"'
----
-
 # Sprint Status Workflow
 
 **Goal:** Summarize sprint status, surface risks, and recommend the next workflow action.
@@ -25,7 +20,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Paths
 
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/4-implementation/sprint-status`
 - `sprint_status_file` = `{implementation_artifacts}/sprint-status.yaml`
 
 ### Input Files

package/src/bmm/workflows/bmad-document-project/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bmad-document-project
+description: 'Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"'
+---
+
+Follow the instructions in ./workflow.md.

package/src/bmm/workflows/bmad-document-project/bmad-skill-manifest.yaml

@@ -0,0 +1 @@
+type: skill

package/src/bmm/workflows/{document-project → bmad-document-project}/instructions.md

@@ -40,18 +40,18 @@
     <action>Load cached project_type_id(s) from state file</action>
 
     <critical>CONDITIONAL CSV LOADING FOR RESUME:</critical>
-    <action>For each cached project_type_id, load ONLY the corresponding row from: {documentation_requirements_csv}</action>
+    <action>For each cached project_type_id, load ONLY the corresponding row from: ./documentation-requirements.csv</action>
     <action>Skip loading project-types.csv and architecture_registry.csv (not needed on resume)</action>
     <action>Store loaded doc requirements for use in remaining steps</action>
 
     <action>Display: "Resuming {{workflow_mode}} from {{current_step}} with cached project type(s): {{cached_project_types}}"</action>
 
     <check if="workflow_mode == deep_dive">
-      <action>Read fully and follow: {installed_path}/workflows/deep-dive-workflow.md with resume context</action>
+      <action>Read fully and follow: ./workflows/deep-dive-workflow.md with resume context</action>
     </check>
 
     <check if="workflow_mode == initial_scan OR workflow_mode == full_rescan">
-      <action>Read fully and follow: {installed_path}/workflows/full-scan-workflow.md with resume context</action>
+      <action>Read fully and follow: ./workflows/full-scan-workflow.md with resume context</action>
     </check>
 
   </check>
@@ -98,7 +98,7 @@ Your choice [1/2/3]:
   <check if="user selects 1">
     <action>Set workflow_mode = "full_rescan"</action>
     <action>Display: "Starting full project rescan..."</action>
-    <action>Read fully and follow: {installed_path}/workflows/full-scan-workflow.md</action>
+    <action>Read fully and follow: ./workflows/full-scan-workflow.md</action>
     <action>After sub-workflow completes, continue to Step 4</action>
   </check>
 
@@ -106,7 +106,7 @@ Your choice [1/2/3]:
     <action>Set workflow_mode = "deep_dive"</action>
     <action>Set scan_level = "exhaustive"</action>
     <action>Display: "Starting deep-dive documentation mode..."</action>
-    <action>Read fully and follow: {installed_path}/workflows/deep-dive-workflow.md</action>
+    <action>Read fully and follow: ./workflows/deep-dive-workflow.md</action>
     <action>After sub-workflow completes, continue to Step 4</action>
   </check>
 
@@ -119,7 +119,7 @@ Your choice [1/2/3]:
 <check if="index.md does not exist">
   <action>Set workflow_mode = "initial_scan"</action>
   <action>Display: "No existing documentation found. Starting initial project scan..."</action>
-  <action>Read fully and follow: {installed_path}/workflows/full-scan-workflow.md</action>
+  <action>Read fully and follow: ./workflows/full-scan-workflow.md</action>
   <action>After sub-workflow completes, continue to Step 4</action>
 </check>
 

package/src/bmm/workflows/bmad-document-project/workflow.md

@@ -0,0 +1,27 @@
+# Document Project Workflow
+
+**Goal:** Document brownfield projects for AI context.
+
+**Your Role:** Project documentation specialist.
+- Communicate all responses in {communication_language}
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `project_knowledge`
+- `user_name`
+- `communication_language`
+- `document_output_language`
+- `user_skill_level`
+- `date` as system-generated current datetime
+
+---
+
+## EXECUTION
+
+Read fully and follow: `./instructions.md`

package/src/bmm/workflows/{document-project → bmad-document-project}/workflows/deep-dive-instructions.md

@@ -4,6 +4,8 @@
 
 <critical>This workflow performs exhaustive deep-dive documentation of specific areas</critical>
 <critical>Handles: deep_dive mode only</critical>
+<critical>YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`</critical>
+<critical>YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`</critical>
 
 <step n="13" goal="Deep-dive documentation of specific area" if="workflow_mode == deep_dive">
 <critical>Deep-dive mode requires literal full-file review. Sampling, guessing, or relying solely on tooling output is FORBIDDEN.</critical>
@@ -191,7 +193,7 @@ This will read EVERY file in this area. Proceed? [y/n]
     - Combine recommended test commands into {{suggested_tests}}
   </action>
 
-<action>Load complete deep-dive template from: {installed_path}/templates/deep-dive-template.md</action>
+<action>Load complete deep-dive template from: ../templates/deep-dive-template.md</action>
 <action>Fill template with all collected data from steps 13b-13d</action>
 <action>Write filled template to: {project_knowledge}/deep-dive-{{sanitized_target_name}}.md</action>
 <action>Validate deep-dive document completeness</action>

package/src/bmm/workflows/{document-project → bmad-document-project}/workflows/deep-dive-workflow.md

@@ -1,8 +1,3 @@
----
-name: document-project-deep-dive
-description: 'Exhaustive deep-dive documentation of specific project areas'
----
-
 # Deep-Dive Documentation Sub-Workflow
 
 **Goal:** Exhaustive deep-dive documentation of specific project areas.
@@ -20,14 +15,11 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 - `project_knowledge`
 - `user_name`
+- `communication_language`, `document_output_language`
 - `date` as system-generated current datetime
 
-### Paths
-
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/document-project/workflows`
-- `instructions` = `{installed_path}/deep-dive-instructions.md`
-- `validation` = `{project-root}/_bmad/bmm/workflows/document-project/checklist.md`
-- `deep_dive_template` = `{project-root}/_bmad/bmm/workflows/document-project/templates/deep-dive-template.md`
+✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
 
 ### Runtime Inputs
 
@@ -39,4 +31,4 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ## EXECUTION
 
-Read fully and follow: `{installed_path}/deep-dive-instructions.md`
+Read fully and follow: `./deep-dive-instructions.md`

package/src/bmm/workflows/{document-project → bmad-document-project}/workflows/full-scan-instructions.md

@@ -4,6 +4,8 @@
 
 <critical>This workflow performs complete project documentation (Steps 1-12)</critical>
 <critical>Handles: initial_scan and full_rescan modes</critical>
+<critical>YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`</critical>
+<critical>YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`</critical>
 
 <step n="0.5" goal="Load documentation requirements data for fresh starts (not needed for resume)" if="resume_mode == false">
 <critical>DATA LOADING STRATEGY - Understanding the Documentation Requirements System:</critical>
@@ -14,7 +16,7 @@
 
 This workflow uses a single comprehensive CSV file to intelligently document your project:
 
-**documentation-requirements.csv** ({documentation_requirements_csv})
+**documentation-requirements.csv** (../documentation-requirements.csv)
 
 - Contains 12 project types (web, mobile, backend, cli, library, desktop, game, data, extension, infra, embedded)
 - 24-column schema combining project type detection AND documentation requirements
@@ -34,7 +36,7 @@ This workflow uses a single comprehensive CSV file to intelligently document you
 
 <action>Now loading documentation requirements data for fresh start...</action>
 
-<action>Load documentation-requirements.csv from: {documentation_requirements_csv}</action>
+<action>Load documentation-requirements.csv from: ../documentation-requirements.csv</action>
 <action>Store all 12 rows indexed by project_type_id for project detection and requirements lookup</action>
 <action>Display: "Loaded documentation requirements for 12 project types (web, mobile, backend, cli, library, desktop, game, data, extension, infra, embedded)"</action>
 
@@ -808,7 +810,7 @@ Generated in {{project_knowledge}}/:
 {{file_list_with_sizes}}
 </action>
 
-<action>Run validation checklist from {validation}</action>
+<action>Run validation checklist from ../checklist.md</action>
 
 <critical>INCOMPLETE DOCUMENTATION DETECTION:
 

package/src/bmm/workflows/{document-project → bmad-document-project}/workflows/full-scan-workflow.md

@@ -1,8 +1,3 @@
----
-name: document-project-full-scan
-description: 'Complete project documentation workflow (initial scan or full rescan)'
----
-
 # Full Project Scan Sub-Workflow
 
 **Goal:** Complete project documentation (initial scan or full rescan).
@@ -19,14 +14,11 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 - `project_knowledge`
 - `user_name`
+- `communication_language`, `document_output_language`
 - `date` as system-generated current datetime
 
-### Paths
-
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/document-project/workflows`
-- `instructions` = `{installed_path}/full-scan-instructions.md`
-- `validation` = `{project-root}/_bmad/bmm/workflows/document-project/checklist.md`
-- `documentation_requirements_csv` = `{project-root}/_bmad/bmm/workflows/document-project/documentation-requirements.csv`
+✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
 
 ### Runtime Inputs
 
@@ -39,4 +31,4 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ## EXECUTION
 
-Read fully and follow: `{installed_path}/full-scan-instructions.md`
+Read fully and follow: `./full-scan-instructions.md`

package/src/bmm/workflows/bmad-generate-project-context/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bmad-generate-project-context
+description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"'
+---
+
+Follow the instructions in ./workflow.md.

package/src/bmm/workflows/bmad-generate-project-context/bmad-skill-manifest.yaml

@@ -0,0 +1 @@
+type: skill

package/src/bmm/workflows/{generate-project-context → bmad-generate-project-context}/steps/step-01-discover.md

@@ -123,7 +123,7 @@ Based on discovery, create or update the context document:
 
 #### A. Fresh Document Setup (if no existing context)
 
-Copy template from `{installed_path}/project-context-template.md` to `{output_folder}/project-context.md`
+Copy template from `../project-context-template.md` to `{output_folder}/project-context.md`
 Initialize frontmatter fields.
 
 #### B. Existing Document Update
@@ -160,6 +160,8 @@ Ready to create/update your project context. This will help AI agents implement
 
 [C] Continue to context generation"
 
+**HALT — wait for user selection before proceeding.**
+
 ## SUCCESS METRICS:
 
 ✅ Existing project context properly detected and handled
@@ -179,6 +181,6 @@ Ready to create/update your project context. This will help AI agents implement
 
 ## NEXT STEP:
 
-After user selects [C] to continue, load `{project-root}/_bmad/bmm/workflows/generate-project-context/steps/step-02-generate.md` to collaboratively generate the specific project context rules.
+After user selects [C] to continue, load `./step-02-generate.md` to collaboratively generate the specific project context rules.
 
 Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and discovery is confirmed and the initial file has been written as directed in this discovery step!

package/src/bmm/workflows/{generate-project-context → bmad-generate-project-context}/steps/step-02-generate.md

@@ -9,6 +9,7 @@
 - 🎯 KEEP CONTENT LEAN - optimize for LLM context efficiency
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -29,8 +30,8 @@ This step will generate content and present choices for each rule category:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute skill:bmad-advanced-elicitation
-- When 'P' selected: Execute {project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md
+- When 'A' selected: Invoke the `bmad-advanced-elicitation` skill
+- When 'P' selected: Invoke the `bmad-party-mode` skill
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -263,11 +264,13 @@ After each category, show the generated rules and present choices:
 [P] Party Mode - Review from different implementation perspectives
 [C] Continue - Save these rules and move to next category"
 
+**HALT — wait for user selection before proceeding.**
+
 ### 10. Handle Menu Selection
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute skill:bmad-advanced-elicitation with current category rules
+- Invoke the `bmad-advanced-elicitation` skill with current category rules
 - Process enhanced rules that come back
 - Ask user: "Accept these enhanced rules for {{category}}? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -275,7 +278,7 @@ After each category, show the generated rules and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute party-mode workflow with category rules context
+- Invoke the `bmad-party-mode` skill with category rules context
 - Process collaborative insights on implementation patterns
 - Ask user: "Accept these changes to {{category}} rules? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -313,6 +316,6 @@ When user selects 'C' for a category, append the content directly to `{output_fo
 
 ## NEXT STEP:
 
-After completing all rule categories and user selects 'C' for the final category, load `{project-root}/_bmad/bmm/workflows/generate-project-context/steps/step-03-complete.md` to finalize the project context file.
+After completing all rule categories and user selects 'C' for the final category, load `./step-03-complete.md` to finalize the project context file.
 
 Remember: Do NOT proceed to step-03 until all categories are complete and user explicitly selects 'C' for each!

package/src/bmm/workflows/{generate-project-context → bmad-generate-project-context}/workflow.md

@@ -1,8 +1,3 @@
----
-name: generate-project-context
-description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"'
----
-
 # Generate Project Context Workflow
 
 **Goal:** Create a concise, optimized `project-context.md` file containing critical rules, patterns, and guidelines that AI agents must follow when implementing code. This file focuses on unobvious details that LLMs need to be reminded of.
@@ -33,17 +28,16 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Paths
 
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/generate-project-context`
-- `template_path` = `{installed_path}/project-context-template.md`
 - `output_file` = `{output_folder}/project-context.md`
 
 ---
 
 ## EXECUTION
 
-Load and execute `{project-root}/_bmad/bmm/workflows/generate-project-context/steps/step-01-discover.md` to begin the workflow.
+Load and execute `./steps/step-01-discover.md` to begin the workflow.
 
 **Note:** Input document discovery and initialization protocols are handled in step-01-discover.md.

package/src/bmm/workflows/bmad-qa-generate-e2e-tests/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bmad-qa-generate-e2e-tests
+description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
+---
+
+Follow the instructions in ./workflow.md.

package/src/bmm/workflows/bmad-qa-generate-e2e-tests/bmad-skill-manifest.yaml

@@ -0,0 +1 @@
+type: skill

package/src/bmm/workflows/{qa-generate-e2e-tests → bmad-qa-generate-e2e-tests}/workflow.md

@@ -1,13 +1,8 @@
----
-name: qa-generate-e2e-tests
-description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
----
-
 # QA Generate E2E Tests Workflow
 
 **Goal:** Generate automated API and E2E tests for implemented code.
 
-**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use Code Review `CR` for that).
+**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use the `bmad-code-review` skill for that).
 
 ---
 
@@ -25,8 +20,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Paths
 
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests`
-- `checklist` = `{installed_path}/checklist.md`
 - `test_dir` = `{project-root}/tests`
 - `source_dir` = `{project-root}`
 - `default_output_file` = `{implementation_artifacts}/tests/test-summary.md`
@@ -140,4 +133,4 @@ If the project needs:
 
 Save summary to: `{default_output_file}`
 
-**Done!** Tests generated and verified. Validate against `{checklist}`.
+**Done!** Tests generated and verified. Validate against `./checklist.md`.

package/src/bmm/workflows/bmad-quick-flow/bmad-quick-dev/SKILL.md

@@ -3,4 +3,4 @@ name: bmad-quick-dev
 description: 'Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.