npm - bmad-method - Versions diffs - 6.0.0-alpha.16 → 6.0.0-alpha.17 - Mend

bmad-method 6.0.0-alpha.16 → 6.0.0-alpha.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (499) hide show

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md CHANGED Viewed

@@ -3,7 +3,7 @@ name: 'step-05-domain'
 description: 'Explore domain-specific requirements for complex domains (optional step)'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
 # File References
 thisStepFile: '{workflow_path}/steps/step-05-domain.md'
@@ -15,8 +15,8 @@ outputFile: '{output_folder}/prd.md'
 domainComplexityCSV: '{workflow_path}/domain-complexity.csv'
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 5: Domain-Specific Exploration
@@ -52,8 +52,8 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
@@ -71,7 +71,7 @@ Before proceeding with this step, verify:
 - Is `complexity_level` from step-02 equal to "high" and/or does the domain have specific regulatory/compliance needs?
 - Would domain exploration significantly impact the product requirements?
-If NO to these questions, skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.
+If NO to these questions, skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.
 ## YOUR TASK:
@@ -83,7 +83,7 @@ Explore domain-specific requirements for complex domains that need specialized c
 Load domain-specific configuration for complex domains:
-- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv` completely
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/domain-complexity.csv` completely
 - Find the row where `domain` matches the detected domain from step-02
 - Extract these columns:
   - `key_concerns` (semicolon-separated list)
@@ -207,7 +207,7 @@ Show the generated domain content and present choices:
 #### If 'A' (Advanced Elicitation):
-- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current domain content
+- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current domain content
 - Process the enhanced domain insights that come back
 - Ask user: "Accept these domain requirement improvements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -215,7 +215,7 @@ Show the generated domain content and present choices:
 #### If 'P' (Party Mode):
-- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current domain requirements
+- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current domain requirements
 - Process the collaborative domain expertise and validation
 - Ask user: "Accept these changes to domain requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -225,7 +225,7 @@ Show the generated domain content and present choices:
 - Append the content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
-- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`
 ## APPEND TO DOCUMENT:
@@ -257,7 +257,7 @@ When user selects 'C', append the content directly to the document using the str
 ## SKIP CONDITIONS:
-Skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md` if:
+Skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md` if:
 - `complexity_level` from step-02 is not "high"
 - Domain has no specific regulatory/compliance requirements
@@ -265,6 +265,6 @@ Skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd
 ## NEXT STEP:
-After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.
+After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md`.
 Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved!

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md CHANGED Viewed

@@ -3,7 +3,7 @@ name: 'step-06-innovation'
 description: 'Detect and explore innovative aspects of the product (optional step)'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-innovation.md'
@@ -15,8 +15,8 @@ outputFile: '{output_folder}/prd.md'
 projectTypesCSV: '{workflow_path}/project-types.csv'
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 6: Innovation Discovery
@@ -52,8 +52,8 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
@@ -83,7 +83,7 @@ Detect and explore innovation patterns in the product, focusing on what makes it
 Load innovation signals specific to this project type:
-- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
 - Find the row where `project_type` matches detected type from step-02
 - Extract `innovation_signals` (semicolon-separated list)
 - Extract `web_search_triggers` for potential innovation research
@@ -186,7 +186,7 @@ Show the generated innovation content and present choices:
 #### If 'A' (Advanced Elicitation):
-- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current innovation content
+- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current innovation content
 - Process the enhanced innovation insights that come back
 - Ask user: "Accept these improvements to the innovation analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -194,7 +194,7 @@ Show the generated innovation content and present choices:
 #### If 'P' (Party Mode):
-- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current innovation content
+- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current innovation content
 - Process the collaborative innovation exploration and ideation
 - Ask user: "Accept these changes to the innovation analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -204,7 +204,7 @@ Show the generated innovation content and present choices:
 - Append the final content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
-- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`
 ## NO INNOVATION DETECTED:
@@ -215,7 +215,7 @@ If no genuine innovation signals are found after exploration:
 [A] Force innovation exploration - Let's try to find innovative angles
 [C] Continue - Skip innovation section and move to Project Type Analysis (Step 7 of 11)"
-If user selects 'A', proceed with content generation anyway. If 'C', skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.
+If user selects 'A', proceed with content generation anyway. If 'C', skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.
 ## APPEND TO DOCUMENT:
@@ -247,7 +247,7 @@ When user selects 'C', append the content directly to the document using the str
 ## SKIP CONDITIONS:
-Skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md` if:
+Skip this step and load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md` if:
 - No innovation signals detected in conversation
 - Product is incremental improvement rather than breakthrough
@@ -256,6 +256,6 @@ Skip this step and load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd
 ## NEXT STEP:
-After user selects 'C' and content is saved to document (or step is skipped), load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.
+After user selects 'C' and content is saved to document (or step is skipped), load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md`.
 Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu (or confirms step skip)!

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md CHANGED Viewed

@@ -3,7 +3,7 @@ name: 'step-07-project-type'
 description: 'Conduct project-type specific discovery using CSV-driven guidance'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
 # File References
 thisStepFile: '{workflow_path}/steps/step-07-project-type.md'
@@ -15,8 +15,8 @@ outputFile: '{output_folder}/prd.md'
 projectTypesCSV: '{workflow_path}/project-types.csv'
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 7: Project-Type Deep Dive
@@ -52,8 +52,8 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
@@ -74,7 +74,7 @@ Conduct project-type specific discovery using CSV-driven guidance to define tech
 Load project-type specific configuration:
-- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/project-types.csv` completely
 - Find the row where `project_type` matches detected type from step-02
 - Extract these columns:
   - `key_questions` (semicolon-separated list of discovery questions)
@@ -182,7 +182,7 @@ Show the generated project-type content and present choices:
 #### If 'A' (Advanced Elicitation):
-- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current project-type content
+- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current project-type content
 - Process the enhanced technical insights that come back
 - Ask user: "Accept these improvements to the technical requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -190,7 +190,7 @@ Show the generated project-type content and present choices:
 #### If 'P' (Party Mode):
-- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current project-type requirements
+- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current project-type requirements
 - Process the collaborative technical expertise and validation
 - Ask user: "Accept these changes to the technical requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -200,7 +200,7 @@ Show the generated project-type content and present choices:
 - Append the final content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`
-- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md`
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md`
 ## APPEND TO DOCUMENT:
@@ -252,6 +252,6 @@ When user selects 'C', append the content directly to the document using the str
 ## NEXT STEP:
-After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` to define project scope.
+After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md` to define project scope.
 Remember: Do NOT proceed to step-08 (Scoping) until user explicitly selects 'C' from the A/P/C menu and content is saved!

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md CHANGED Viewed

@@ -3,7 +3,7 @@ name: 'step-08-scoping'
 description: 'Define MVP boundaries and prioritize features across development phases'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
 # File References
 thisStepFile: '{workflow_path}/steps/step-08-scoping.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/prd.md'
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 8: Scoping Exercise - MVP & Future Features
@@ -50,8 +50,8 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
 - 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
@@ -243,7 +243,7 @@ Show the scoping decisions and present choices:
 #### If 'A' (Advanced Elicitation):
-- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current scoping analysis
+- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with current scoping analysis
 - Process enhanced scoping insights that come back
 - Ask user: "Accept these improvements to the scoping decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -251,7 +251,7 @@ Show the scoping decisions and present choices:
 #### If 'P' (Party Mode):
-- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with scoping context
+- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with scoping context
 - Process collaborative insights on MVP and roadmap decisions
 - Ask user: "Accept these changes to the scoping decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md CHANGED Viewed

@@ -3,7 +3,7 @@ name: 'step-09-functional'
 description: 'Synthesize all discovery into comprehensive functional requirements'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
 # File References
 thisStepFile: '{workflow_path}/steps/step-09-functional.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/prd.md'
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 9: Functional Requirements Synthesis
@@ -49,8 +49,8 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
@@ -209,7 +209,7 @@ Show the generated functional requirements and present choices:
 #### If 'A' (Advanced Elicitation):
-- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current FR list
+- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current FR list
 - Process the enhanced capability coverage that comes back
 - Ask user: "Accept these additions to the functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -217,7 +217,7 @@ Show the generated functional requirements and present choices:
 #### If 'P' (Party Mode):
-- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current FR list
+- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current FR list
 - Process the collaborative capability validation and additions
 - Ask user: "Accept these changes to the functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -227,7 +227,7 @@ Show the generated functional requirements and present choices:
 - Append the final content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9]`
-- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md`
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md`
 ## APPEND TO DOCUMENT:
@@ -264,6 +264,6 @@ Emphasize to user: "This FR list is now binding. Any feature not listed here wil
 ## NEXT STEP:
-After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md` to define non-functional requirements.
+After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md` to define non-functional requirements.
 Remember: Do NOT proceed to step-10 until user explicitly selects 'C' from the A/P/C menu and content is saved!

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md CHANGED Viewed

@@ -3,7 +3,7 @@ name: 'step-10-nonfunctional'
 description: 'Define quality attributes that matter for this specific product'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
 # File References
 thisStepFile: '{workflow_path}/steps/step-10-nonfunctional.md'
@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/prd.md'
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 # Step 10: Non-Functional Requirements
@@ -49,8 +49,8 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
@@ -209,7 +209,7 @@ Show the generated NFR content and present choices:
 #### If 'A' (Advanced Elicitation):
-- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current NFR content
+- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current NFR content
 - Process the enhanced quality attribute insights that come back
 - Ask user: "Accept these improvements to the non-functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -217,7 +217,7 @@ Show the generated NFR content and present choices:
 #### If 'P' (Party Mode):
-- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current NFR list
+- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current NFR list
 - Process the collaborative technical validation and additions
 - Ask user: "Accept these changes to the non-functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -227,7 +227,7 @@ Show the generated NFR content and present choices:
 - Append the final content to `{output_folder}/prd.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]`
-- Load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md`
+- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md`
 ## APPEND TO DOCUMENT:
@@ -288,6 +288,6 @@ When user selects 'C', append the content directly to the document using the str
 ## NEXT STEP:
-After user selects 'C' and content is saved to document, load `{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md` to finalize the PRD and complete the workflow.
+After user selects 'C' and content is saved to document, load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md` to finalize the PRD and complete the workflow.
 Remember: Do NOT proceed to step-11 until user explicitly selects 'C' from the A/P/C menu and content is saved!

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md CHANGED Viewed

@@ -3,7 +3,7 @@ name: 'step-11-complete'
 description: 'Complete the PRD workflow, update status files, and suggest next steps'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd'
+workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
 # File References
 thisStepFile: '{workflow_path}/steps/step-11-complete.md'

package/src/modules/bmm/workflows/2-plan-workflows/prd/workflow.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: create-prd
-description: Creates a comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.
-main_config: '{project-root}/.bmad/bmm/config.yaml'
+description: Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.
+main_config: '{project-root}/_bmad/bmm/config.yaml'
 web_bundle: true
 ---

package/src/modules/bmm/workflows/3-solutioning/{implementation-readiness → check-implementation-readiness}/steps/step-01-document-discovery.md RENAMED Viewed

@@ -3,7 +3,7 @@ name: 'step-01-document-discovery'
 description: 'Discover and inventory all project documents, handling duplicates and organizing file structure'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 # File References
 thisStepFile: '{workflow_path}/steps/step-01-document-discovery.md'

package/src/modules/bmm/workflows/3-solutioning/{implementation-readiness → check-implementation-readiness}/steps/step-02-prd-analysis.md RENAMED Viewed

@@ -3,7 +3,7 @@ name: 'step-02-prd-analysis'
 description: 'Read and analyze PRD to extract all FRs and NFRs for coverage validation'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 # File References
 thisStepFile: '{workflow_path}/steps/step-02-prd-analysis.md'

package/src/modules/bmm/workflows/3-solutioning/{implementation-readiness → check-implementation-readiness}/steps/step-03-epic-coverage-validation.md RENAMED Viewed

@@ -3,7 +3,7 @@ name: 'step-03-epic-coverage-validation'
 description: 'Validate that all PRD FRs are covered in epics and stories'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-epic-coverage-validation.md'

package/src/modules/bmm/workflows/3-solutioning/{implementation-readiness → check-implementation-readiness}/steps/step-04-ux-alignment.md RENAMED Viewed

@@ -3,7 +3,7 @@ name: 'step-04-ux-alignment'
 description: 'Check for UX document and validate alignment with PRD and Architecture'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 # File References
 thisStepFile: '{workflow_path}/steps/step-04-ux-alignment.md'

package/src/modules/bmm/workflows/3-solutioning/{implementation-readiness → check-implementation-readiness}/steps/step-05-epic-quality-review.md RENAMED Viewed

@@ -3,14 +3,14 @@ name: 'step-05-epic-quality-review'
 description: 'Validate epics and stories against create-epics-and-stories best practices'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 # File References
 thisStepFile: '{workflow_path}/steps/step-05-epic-quality-review.md'
 nextStepFile: '{workflow_path}/steps/step-06-final-assessment.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/implementation-readiness-report-{{date}}.md'
-epicsBestPractices: '{project-root}/.bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
+epicsBestPractices: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
 ---
 # Step 5: Epic Quality Review

package/src/modules/bmm/workflows/3-solutioning/{implementation-readiness → check-implementation-readiness}/steps/step-06-final-assessment.md RENAMED Viewed

@@ -3,7 +3,7 @@ name: 'step-06-final-assessment'
 description: 'Compile final assessment and polish the readiness report'
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmm/workflows/3-solutioning/implementation-readiness'
+workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-final-assessment.md'

package/src/modules/bmm/workflows/3-solutioning/{implementation-readiness → check-implementation-readiness}/workflow.md RENAMED Viewed

@@ -45,7 +45,7 @@ web_bundle: false
 ### 1. Module Configuration Loading
-Load and read full config from {project-root}/.bmad/bmm/config.yaml and resolve:
+Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve:
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`

package/src/modules/bmm/workflows/3-solutioning/{architecture → create-architecture}/steps/step-01-init.md RENAMED Viewed

@@ -94,7 +94,7 @@ Discover and load context documents using smart discovery:
 **Project Context Rules (Critical for AI Agents):**
-1. Check for project context file: `**/project_context.md`
+1. Check for project context file: `**/project-context.md`
 2. If exists: Load COMPLETE file contents - this contains critical rules for AI agents
 3. Add to frontmatter `hasProjectContext: true` and track file path
 4. Report to user: "Found existing project context with {number_of_rules} agent rules"

package/src/modules/bmm/workflows/3-solutioning/{architecture → create-architecture}/steps/step-02-context.md RENAMED Viewed

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
 - 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
@@ -169,7 +169,7 @@ Show the generated content and present choices:
 #### If 'A' (Advanced Elicitation):
-- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with the current context analysis
+- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current context analysis
 - Process the enhanced architectural insights that come back
 - Ask user: "Accept these enhancements to the project context analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -177,7 +177,7 @@ Show the generated content and present choices:
 #### If 'P' (Party Mode):
-- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with the current project context
+- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current project context
 - Process the collaborative improvements to architectural understanding
 - Ask user: "Accept these changes to the project context analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

package/src/modules/bmm/workflows/3-solutioning/{architecture → create-architecture}/steps/step-03-starter.md RENAMED Viewed

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
 - 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
@@ -276,7 +276,7 @@ Show the generated content and present choices:
 #### If 'A' (Advanced Elicitation):
-- Execute {project-root}/.bmad/core/tasks/advanced-elicitation.xml with current starter analysis
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current starter analysis
 - Process enhanced insights about starter options or custom approaches
 - Ask user: "Accept these changes to the starter template evaluation? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -284,7 +284,7 @@ Show the generated content and present choices:
 #### If 'P' (Party Mode):
-- Execute {project-root}/.bmad/core/workflows/party-mode/workflow.md with starter evaluation context
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with starter evaluation context
 - Process collaborative insights about starter trade-offs
 - Ask user: "Accept these changes to the starter template evaluation? (y/n)"
 - If yes: Update content, then return to A/P/C menu