fix: replace quote delimiters with output-block tags in step-04-review

Double-quote delimiters around multi-line output template blocks are
visually ambiguous to humans (opening quote on one line, closing quote
many lines later) and confuse linters and LLM code reviewers into
filing false issues (see #1434).

A/B tested across 5 models (Opus, Sonnet, Haiku, Codex 5.2, Gemini):
removing quotes entirely causes Haiku to refuse instructions in 1/3
runs, but any explicit block delimiter works equally well. XML-style
output-block tags are the best fit: visually obvious boundaries,
self-documenting, linter-clean, and consistent with existing BMAD
XML tag conventions (step, action, check, template-output).

Relates to #1433

.claude/commands/bmad-bmm-generate-project-context.md

@@ -1,14 +0,0 @@
----
-name: 'generate-project-context'
-description: 'Scan existing codebase to generate a lean LLM-optimized project-context.md with critical implementation rules and patterns for AI agents'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md
-3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.npmrc

@@ -1,5 +1 @@
-# Prevent peer dependency warnings during installation
-legacy-peer-deps=true
-
-# Improve install performance
-prefer-offline=true
+registry=https://registry.npmjs.org

README.md

@@ -65,13 +65,13 @@ Every step tells you what's next. Optional phases (brainstorming, research, UX d
 
 BMad Method extends with official modules for specialized domains. Modules are available during installation and can be added to your project at any time. After the V6 beta period these will also be available as Plugins and Granular Skills.
 
-| Module                                | GitHub                                                                                                                            | NPM                                                                                                | Purpose                                                               |
-| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
-| **BMad Method (BMM)**                 | [bmad-code-org/BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD)                                                         | [bmad-method](https://www.npmjs.com/package/bmad-method)                                           | Core framework with 34+ workflows across 4 development phases         |
-| **BMad Builder (BMB)**                | [bmad-code-org/bmad-builder](https://github.com/bmad-code-org/bmad-builder)                                                       | [bmad-builder](https://www.npmjs.com/package/bmad-builder)                                         | Create custom BMad agents, workflows, and domain-specific modules     |
-| **Test Architect (TEA)** 🆕            | [bmad-code-org/tea](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)                                    | [tea](https://www.npmjs.com/package/bmad-method-test-architecture-enterprise)                      | Risk-based test strategy, automation, and release gates (8 workflows) |
-| **Game Dev Studio (BMGD)**            | [bmad-code-org/bmad-module-game-dev-studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio)                         | [bmad-game-dev-studio](https://www.npmjs.com/package/bmad-game-dev-studio)                         | Game development workflows for Unity, Unreal, and Godot               |
-| **Creative Intelligence Suite (CIS)** | [bmad-code-org/bmad-module-creative-intelligence-suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite) | [bmad-creative-intelligence-suite](https://www.npmjs.com/package/bmad-creative-intelligence-suite) | Innovation, brainstorming, design thinking, and problem-solving       |
+| Module                                | GitHub                                                                                                                            | NPM                                                                                                                | Purpose                                                           |
+| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- |
+| **BMad Method (BMM)**                 | [bmad-code-org/BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD)                                                         | [bmad-method](https://www.npmjs.com/package/bmad-method)                                           | Core framework with 34+ workflows across 4 development phases     |
+| **BMad Builder (BMB)**                | [bmad-code-org/bmad-builder](https://github.com/bmad-code-org/bmad-builder)                                                       | [bmad-builder](https://www.npmjs.com/package/bmad-builder)                                         | Create custom BMad agents, workflows, and domain-specific modules |
+| **Test Architect (TEA)** 🆕           | [bmad-code-org/tea](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)                                    | [tea](https://www.npmjs.com/package/bmad-method-test-architecture-enterprise)                      | Risk-based test strategy, automation, and release gates (8 workflows) |
+| **Game Dev Studio (BMGD)**            | [bmad-code-org/bmad-module-game-dev-studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio)                         | [bmad-game-dev-studio](https://www.npmjs.com/package/bmad-game-dev-studio)                         | Game development workflows for Unity, Unreal, and Godot           |
+| **Creative Intelligence Suite (CIS)** | [bmad-code-org/bmad-module-creative-intelligence-suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite) | [bmad-creative-intelligence-suite](https://www.npmjs.com/package/bmad-creative-intelligence-suite) | Innovation, brainstorming, design thinking, and problem-solving   |
 
 * More modules are coming in the next 2 weeks from BMad Official, and a community marketplace for the installer also will be coming with the final V6 release!
 
@@ -116,7 +116,6 @@ BMad provides two testing options to fit your needs:
 ### For v4 Users
 
 - **[v4 Documentation](https://github.com/bmad-code-org/BMAD-METHOD/tree/V4/docs)**
-- If you need to install V4, you can do this with  `npx bmad-method@4.44.3 install` - similar for any past version.
 
 ## Community
 

package.json

@@ -39,7 +39,7 @@
     "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0",
     "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix",
     "lint:md": "markdownlint-cli2 \"**/*.md\"",
-    "prepare": "command -v husky >/dev/null 2>&1 && husky || exit 0",
+    "prepare": "husky",
     "rebundle": "node tools/cli/bundlers/bundle-web.js rebundle",
     "release:major": "gh workflow run \"Manual Release\" -f version_bump=major",
     "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor",
@@ -88,7 +88,7 @@
   },
   "devDependencies": {
     "@astrojs/sitemap": "^3.6.0",
-    "@astrojs/starlight": "^0.37.5",
+    "@astrojs/starlight": "^0.37.0",
     "@eslint/js": "^9.33.0",
     "archiver": "^7.0.1",
     "astro": "^5.16.0",
@@ -99,7 +99,7 @@
     "eslint-plugin-unicorn": "^60.0.0",
     "eslint-plugin-yml": "^1.18.0",
     "husky": "^9.1.7",
-    "jest": "^30.2.0",
+    "jest": "^30.0.4",
     "lint-staged": "^16.1.1",
     "markdownlint-cli2": "^0.19.1",
     "prettier": "^3.7.4",

src/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -16,6 +16,7 @@ agent:
     principles: |
       - Planning and execution are two sides of the same coin.
       - Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't.
+      - If `**/project-context.md` exists, follow it. If absent, proceed without.
 
   menu:
     - trigger: TS or fuzzy match on tech-spec

src/bmm/module-help.csv

@@ -1,6 +1,5 @@
 module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
 bmm,anytime,Document Project,DP,10,_bmad/bmm/workflows/document-project/workflow.yaml,bmad-bmm-document-project,false,analyst,Create Mode,"Analyze an existing project to produce useful documentation",project-knowledge,*,
-bmm,anytime,Generate Project Context,GPC,15,_bmad/bmm/workflows/generate-project-context/workflow.md,bmad-bmm-generate-project-context,false,analyst,Create Mode,"Scan existing codebase to generate a lean LLM-optimized project-context.md containing critical implementation rules patterns and conventions for AI agents. Essential for brownfield projects and quick-flow.",output_folder,"project context",
 bmm,anytime,Quick Spec,TS,20,_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md,bmad-bmm-quick-spec,false,quick-flow-solo-dev,Create Mode,"Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method. Quick one-off tasks small changes simple apps utilities without extensive planning",planning_artifacts,"tech spec",
 bmm,anytime,Quick Dev,QD,30,_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md,bmad-bmm-quick-dev,false,quick-flow-solo-dev,Create Mode,"Quick one-off tasks small changes simple apps utilities without extensive planning - Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method, unless the user is already working through the implementation phase and just requests a 1 off things not already in the plan",,,
 bmm,anytime,Correct Course,CC,40,_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml,bmad-bmm-correct-course,false,sm,Create Mode,"Anytime: Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories",planning_artifacts,"change proposal",

src/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md

@@ -137,9 +137,7 @@ Do you have any other documents you'd like me to include, or shall we continue t
 
 ### 4. Present MENU OPTIONS
 
-<output-block>
-**Proceeding to product vision discovery...**
-</output-block>
+Display: "**Proceeding to product vision discovery...**"
 
 #### Menu Handling Logic:
 

src/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md

@@ -119,11 +119,9 @@ What would be most helpful?"
 ### 6. Present MENU OPTIONS
 
 **If workflow not complete:**
-<output-block>
-Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
+Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
 
-**Select an Option:** [C] Continue to Step {nextStepNumber}
-</output-block>
+**Select an Option:** [C] Continue to Step {nextStepNumber}"
 
 #### Menu Handling Logic:
 

src/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md

@@ -37,9 +37,7 @@ Confirm domain research scope and approach for **{{research_topic}}** with the u
 ### 1. Begin Scope Confirmation
 
 Start with domain scope understanding:
-
-<output-block>
-I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}}
+"I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}}
 
 **Domain Research Scope:**
 
@@ -55,14 +53,11 @@ I understand you want to conduct **domain research** for **{{research_topic}}**
 - Multi-source validation for critical domain claims
 - Confidence levels for uncertain domain information
 - Comprehensive domain coverage with industry-specific insights
-</output-block>
 
 ### 2. Scope Confirmation
 
 Present clear scope confirmation:
-
-<output-block>
-**Domain Research Scope Confirmation:**
+"**Domain Research Scope Confirmation:**
 
 For **{{research_topic}}**, I will research:
 
@@ -76,7 +71,6 @@ For **{{research_topic}}**, I will research:
 
 **Does this domain research scope and approach align with your goals?**
 [C] Continue - Begin domain research with this scope
-</output-block>
 
 ### 3. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md

@@ -41,9 +41,7 @@ Conduct industry analysis focusing on market size, growth, and industry dynamics
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly.
 
 Start with industry research approach:
-
-<output-block>
-Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics.
+"Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics.
 
 **Industry Analysis Focus:**
 
@@ -53,8 +51,7 @@ Now I'll conduct **industry analysis** for **{{research_topic}}** to understand
 - Industry trends and evolution patterns
 - Economic impact and value creation
 
-**Let me search for current industry insights.**
-</output-block>
+**Let me search for current industry insights.**"
 
 ### 2. Parallel Industry Research Execution
 
@@ -77,8 +74,7 @@ Search the web: "{{research_topic}} industry trends evolution"
 
 **Collect and analyze findings from all parallel searches:**
 
-<output-block>
-After executing comprehensive parallel web searches, let me analyze and aggregate industry findings:
+"After executing comprehensive parallel web searches, let me analyze and aggregate industry findings:
 
 **Research Coverage:**
 
@@ -91,8 +87,7 @@ After executing comprehensive parallel web searches, let me analyze and aggregat
 [Identify patterns connecting market dynamics, segmentation, and trends]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]
-</output-block>
+[Overall confidence levels and research gaps identified]"
 
 ### 4. Generate Industry Analysis Content
 
@@ -157,8 +152,7 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-<output-block>
-I've completed **industry analysis** for {{research_topic}}.
+"I've completed **industry analysis** for {{research_topic}}.
 
 **Key Industry Findings:**
 
@@ -170,7 +164,6 @@ I've completed **industry analysis** for {{research_topic}}.
 
 **Ready to proceed to competitive landscape analysis?**
 [C] Continue - Save this to document and proceed to competitive landscape
-</output-block>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md

@@ -41,9 +41,7 @@ Conduct competitive landscape analysis focusing on key players, market share, an
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different competitive areas simultaneously and thoroughly.
 
 Start with competitive research approach:
-
-<output-block>
-Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** to understand the competitive ecosystem.
+"Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** to understand the competitive ecosystem.
 
 **Competitive Landscape Focus:**
 
@@ -53,8 +51,7 @@ Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** t
 - Business models and value propositions
 - Entry barriers and competitive dynamics
 
-**Let me search for current competitive insights.**
-</output-block>
+**Let me search for current competitive insights.**"
 
 ### 2. Parallel Competitive Research Execution
 
@@ -77,8 +74,7 @@ Search the web: "{{research_topic}} entry barriers competitive dynamics"
 
 **Collect and analyze findings from all parallel searches:**
 
-<output-block>
-After executing comprehensive parallel web searches, let me analyze and aggregate competitive findings:
+"After executing comprehensive parallel web searches, let me analyze and aggregate competitive findings:
 
 **Research Coverage:**
 
@@ -91,8 +87,7 @@ After executing comprehensive parallel web searches, let me analyze and aggregat
 [Identify patterns connecting players, strategies, and market dynamics]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]
-</output-block>
+[Overall confidence levels and research gaps identified]"
 
 ### 4. Generate Competitive Landscape Content
 
@@ -166,8 +161,7 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-<output-block>
-I've completed **competitive landscape analysis** for {{research_topic}}.
+"I've completed **competitive landscape analysis** for {{research_topic}}.
 
 **Key Competitive Findings:**
 
@@ -179,7 +173,6 @@ I've completed **competitive landscape analysis** for {{research_topic}}.
 
 **Ready to proceed to regulatory focus analysis?**
 [C] Continue - Save this to document and proceed to regulatory focus
-</output-block>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md

@@ -39,9 +39,7 @@ Conduct focused regulatory and compliance analysis with emphasis on requirements
 ### 1. Begin Regulatory Analysis
 
 Start with regulatory research approach:
-
-<output-block>
-Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}**.
+"Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}**.
 
 **Regulatory Focus Areas:**
 
@@ -51,8 +49,7 @@ Now I'll focus on **regulatory and compliance requirements** that impact **{{res
 - Data protection and privacy regulations
 - Environmental and safety requirements
 
-**Let me search for current regulatory requirements.**
-</output-block>
+**Let me search for current regulatory requirements.**"
 
 ### 2. Web Search for Specific Regulations
 
@@ -139,9 +136,7 @@ _Source: [URL]_
 ### 6. Present Analysis and Continue Option
 
 Show the generated regulatory analysis and present continue option:
-
-<output-block>
-I've completed **regulatory requirements analysis** for {{research_topic}}.
+"I've completed **regulatory requirements analysis** for {{research_topic}}.
 
 **Key Regulatory Findings:**
 
@@ -153,7 +148,6 @@ I've completed **regulatory requirements analysis** for {{research_topic}}.
 
 **Ready to proceed to technical trends?**
 [C] Continue - Save this to the document and move to technical trends
-</output-block>
 
 ### 7. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md

@@ -39,9 +39,7 @@ Conduct comprehensive technical trends analysis using current web data with emph
 ### 1. Begin Technical Trends Analysis
 
 Start with technology research approach:
-
-<output-block>
-Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current data.
+"Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current data.
 
 **Technical Trends Focus:**
 
@@ -51,8 +49,7 @@ Now I'll conduct **technical trends and emerging technologies** analysis for **{
 - New business models enabled by technology
 - Future technology projections and roadmaps
 
-**Let me search for current technology developments.**
-</output-block>
+**Let me search for current technology developments.**"
 
 ### 2. Web Search for Emerging Technologies
 
@@ -151,9 +148,7 @@ _Source: [URL]_
 ### 6. Present Analysis and Complete Option
 
 Show the generated technical analysis and present complete option:
-
-<output-block>
-I've completed **technical trends and innovation analysis** for {{research_topic}}.
+"I've completed **technical trends and innovation analysis** for {{research_topic}}.
 
 **Technical Highlights:**
 
@@ -172,7 +167,6 @@ I've completed **technical trends and innovation analysis** for {{research_topic
 
 **Ready to proceed to research synthesis and recommendations?**
 [C] Continue - Save this to document and proceed to synthesis
-</output-block>
 
 ### 7. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md

@@ -339,8 +339,7 @@ _This comprehensive research document serves as an authoritative reference on {{
 
 **Document Completion Presentation:**
 
-<output-block>
-I've completed the **comprehensive research document synthesis** for **{{research_topic}}**, producing an authoritative research document with:
+"I've completed the **comprehensive research document synthesis** for **{{research_topic}}**, producing an authoritative research document with:
 
 **Document Features:**
 
@@ -369,7 +368,6 @@ I've completed the **comprehensive research document synthesis** for **{{researc
 
 **Ready to complete this comprehensive research document?**
 [C] Complete Research - Save final comprehensive document
-</output-block>
 
 ### 6. Handle Final Completion
 

src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md

@@ -39,9 +39,7 @@ Initialize market research by confirming understanding of {{research_topic}} and
 **INITIALIZE - DO NOT RESEARCH YET**
 
 Start with research confirmation:
-
-<output-block>
-I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
+"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
 
 **My Understanding of Your Research Needs:**
 
@@ -57,8 +55,7 @@ I understand you want to conduct **market research** for **{{research_topic}}**
 - Competitive landscape and positioning
 - Strategic recommendations and implementation guidance
 
-**Does this accurately capture what you're looking for?**
-</output-block>
+**Does this accurately capture what you're looking for?**"
 
 ### 2. Refine Research Scope
 
@@ -120,9 +117,7 @@ Write initial research scope to document:
 ### 4. Present Confirmation and Continue Option
 
 Show initial scope document and present continue option:
-
-<output-block>
-I've documented our understanding and initial scope for **{{research_topic}}** market research.
+"I've documented our understanding and initial scope for **{{research_topic}}** market research.
 
 **What I've established:**
 
@@ -136,7 +131,6 @@ I've documented our understanding and initial scope for **{{research_topic}}** m
 **Ready to begin detailed market research?**
 [C] Continue - Confirm scope and proceed to customer insights analysis
 [Modify] Suggest changes to research scope before proceeding
-</output-block>
 
 ### 5. Handle User Response
 

src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md

@@ -41,9 +41,7 @@ Conduct customer behavior and segment analysis with emphasis on patterns and dem
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly.
 
 Start with customer behavior research approach:
-
-<output-block>
-Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns.
+"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns.
 
 **Customer Behavior Focus:**
 
@@ -53,8 +51,7 @@ Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to un
 - Behavior drivers and influences
 - Customer interaction patterns and engagement
 
-**Let me search for current customer behavior insights.**
-</output-block>
+**Let me search for current customer behavior insights.**"
 
 ### 2. Parallel Customer Behavior Research Execution
 
@@ -77,8 +74,7 @@ Search the web: "{{research_topic}} customer behavior drivers"
 
 **Collect and analyze findings from all parallel searches:**
 
-<output-block>
-After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
 
 **Research Coverage:**
 
@@ -92,8 +88,7 @@ After executing comprehensive parallel web searches, let me analyze and aggregat
 [Identify patterns connecting demographics, psychographics, and behaviors]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]
-</output-block>
+[Overall confidence levels and research gaps identified]"
 
 ### 4. Generate Customer Behavior Content
 
@@ -165,8 +160,7 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-<output-block>
-I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
+"I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
 
 **Key Customer Behavior Findings:**
 
@@ -178,7 +172,6 @@ I've completed **customer behavior analysis** for {{research_topic}}, focusing o
 
 **Ready to proceed to customer pain points?**
 [C] Continue - Save this to document and proceed to pain points analysis
-</output-block>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md

@@ -38,9 +38,7 @@ Conduct comprehensive customer insights analysis with emphasis on behavior patte
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer areas simultaneously and thoroughly
 
 Start with customer research approach:
-
-<output-block>
-Now I'll conduct **customer insights analysis** to understand customer behavior and needs.
+"Now I'll conduct **customer insights analysis** to understand customer behavior and needs.
 
 **Customer Insights Focus:**
 
@@ -51,8 +49,7 @@ Now I'll conduct **customer insights analysis** to understand customer behavior
 - Customer satisfaction drivers
 - Demographic and psychographic profiles
 
-**Let me search for current customer insights using parallel web searches for comprehensive coverage.**
-</output-block>
+**Let me search for current customer insights using parallel web searches for comprehensive coverage.**"
 
 ### 2. Parallel Customer Research Execution
 
@@ -75,8 +72,7 @@ Search the web: "[product/service/market] customer decision process"
 
 **Collect and analyze findings from all parallel searches:**
 
-<output-block>
-After executing comprehensive parallel web searches, let me analyze and aggregate the customer insights:
+"After executing comprehensive parallel web searches, let me analyze and aggregate the customer insights:
 
 **Research Coverage:**
 
@@ -88,8 +84,7 @@ After executing comprehensive parallel web searches, let me analyze and aggregat
 [Identify patterns connecting behavior, pain points, and decisions]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]
-</output-block>
+[Overall confidence levels and research gaps identified]"
 
 ### 4. Generate Customer Insights Content
 
@@ -141,9 +136,7 @@ _Source: [URL]_
 ### 5. Present Analysis and Continue Option
 
 Show the generated customer insights and present continue option:
-
-<output-block>
-I've completed the **customer insights analysis** for customer behavior and needs.
+"I've completed the **customer insights analysis** for customer behavior and needs.
 
 **Key Customer Findings:**
 
@@ -155,7 +148,6 @@ I've completed the **customer insights analysis** for customer behavior and need
 
 **Ready to proceed to competitive analysis?**
 [C] Continue - Save this to the document and proceed to competitive analysis
-</output-block>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md

@@ -42,9 +42,7 @@ Conduct customer pain points and needs analysis with emphasis on challenges and
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer pain point areas simultaneously and thoroughly.
 
 Start with customer pain points research approach:
-
-<output-block>
-Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to understand customer challenges.
+"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to understand customer challenges.
 
 **Customer Pain Points Focus:**
 
@@ -54,8 +52,7 @@ Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to
 - Service and support pain points
 - Customer satisfaction gaps
 
-**Let me search for current customer pain points insights.**
-</output-block>
+**Let me search for current customer pain points insights.**"
 
 ### 2. Parallel Pain Points Research Execution
 
@@ -78,8 +75,7 @@ Search the web: "{{research_topic}} customer barriers to adoption"
 
 **Collect and analyze findings from all parallel searches:**
 
-<output-block>
-After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings:
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings:
 
 **Research Coverage:**
 
@@ -92,8 +88,7 @@ After executing comprehensive parallel web searches, let me analyze and aggregat
 [Identify patterns connecting different types of pain points]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]
-</output-block>
+[Overall confidence levels and research gaps identified]"
 
 ### 4. Generate Customer Pain Points Content
 
@@ -176,8 +171,7 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-<output-block>
-I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges.
+"I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges.
 
 **Key Pain Points Findings:**
 
@@ -189,7 +183,6 @@ I've completed **customer pain points analysis** for {{research_topic}}, focusin
 
 **Ready to proceed to customer decision processes?**
 [C] Continue - Save this to document and proceed to decision processes analysis
-</output-block>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md

@@ -42,9 +42,7 @@ Conduct customer decision processes and journey analysis with emphasis on decisi
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer decision areas simultaneously and thoroughly.
 
 Start with customer decisions research approach:
-
-<output-block>
-Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** to understand customer decision-making.
+"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** to understand customer decision-making.
 
 **Customer Decisions Focus:**
 
@@ -54,8 +52,7 @@ Now I'll conduct **customer decision processes analysis** for **{{research_topic
 - Purchase decision influencers
 - Information gathering patterns
 
-**Let me search for current customer decision insights.**
-</output-block>
+**Let me search for current customer decision insights.**"
 
 ### 2. Parallel Decisions Research Execution
 
@@ -78,8 +75,7 @@ Search the web: "{{research_topic}} decision influencing factors"
 
 **Collect and analyze findings from all parallel searches:**
 
-<output-block>
-After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings:
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings:
 
 **Research Coverage:**
 
@@ -92,8 +88,7 @@ After executing comprehensive parallel web searches, let me analyze and aggregat
 [Identify patterns connecting decision factors and journey stages]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]
-</output-block>
+[Overall confidence levels and research gaps identified]"
 
 ### 4. Generate Customer Decisions Content
 
@@ -186,8 +181,7 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-<output-block>
-I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making.
+"I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making.
 
 **Key Decision Findings:**
 
@@ -199,7 +193,6 @@ I've completed **customer decision processes analysis** for {{research_topic}},
 
 **Ready to proceed to competitive analysis?**
 [C] Continue - Save this to document and proceed to competitive analysis
-</output-block>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md

@@ -36,9 +36,7 @@ Conduct comprehensive competitive analysis with emphasis on market positioning.
 ### 1. Begin Competitive Analysis
 
 Start with competitive research approach:
-
-<output-block>
-Now I'll conduct **competitive analysis** to understand the competitive landscape.
+"Now I'll conduct **competitive analysis** to understand the competitive landscape.
 
 **Competitive Analysis Focus:**
 
@@ -48,8 +46,7 @@ Now I'll conduct **competitive analysis** to understand the competitive landscap
 - Market differentiation opportunities
 - Competitive threats and challenges
 
-**Let me search for current competitive information.**
-</output-block>
+**Let me search for current competitive information.**"
 
 ### 2. Generate Competitive Analysis Content
 
@@ -101,9 +98,7 @@ _Source: [URL]_
 ### 3. Present Analysis and Complete Option
 
 Show the generated competitive analysis and present complete option:
-
-<output-block>
-I've completed the **competitive analysis** for the competitive landscape.
+"I've completed the **competitive analysis** for the competitive landscape.
 
 **Key Competitive Findings:**
 
@@ -115,7 +110,6 @@ I've completed the **competitive analysis** for the competitive landscape.
 
 **Ready to complete the market research?**
 [C] Complete Research - Save final document and conclude
-</output-block>
 
 ### 4. Handle Complete Selection
 

src/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md

@@ -39,9 +39,7 @@ Produce a comprehensive, authoritative market research document on **{{research_
 ### 1. Begin Strategic Synthesis
 
 Start with strategic synthesis approach:
-
-<output-block>
-Now I'll complete our market research with **strategic synthesis and recommendations** .
+"Now I'll complete our market research with **strategic synthesis and recommendations** .
 
 **Strategic Synthesis Focus:**
 
@@ -51,8 +49,7 @@ Now I'll complete our market research with **strategic synthesis and recommendat
 - Risk assessment and mitigation approaches
 - Actionable next steps and implementation guidance
 
-**Let me search for current strategic insights and best practices.**
-</output-block>
+**Let me search for current strategic insights and best practices.**"
 
 ### 2. Web Search for Market Entry Strategies
 
@@ -359,8 +356,7 @@ _This comprehensive market research document serves as an authoritative market r
 
 **Market Research Document Completion Presentation:**
 
-<output-block>
-I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with:
+"I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with:
 
 **Document Features:**
 
@@ -388,7 +384,6 @@ I've completed the **comprehensive market research document synthesis** for **{{
 
 **Ready to complete this comprehensive market research document?**
 [C] Complete Research - Save final comprehensive market research document
-</output-block>
 
 ### 6. Handle Complete Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md

@@ -37,9 +37,7 @@ Confirm technical research scope and approach for **{{research_topic}}** with th
 ### 1. Begin Scope Confirmation
 
 Start with technical scope understanding:
-
-<output-block>
-I understand you want to conduct **technical research** for **{{research_topic}}** with these goals: {{research_goals}}
+"I understand you want to conduct **technical research** for **{{research_topic}}** with these goals: {{research_goals}}
 
 **Technical Research Scope:**
 
@@ -55,14 +53,11 @@ I understand you want to conduct **technical research** for **{{research_topic}}
 - Multi-source validation for critical technical claims
 - Confidence levels for uncertain technical information
 - Comprehensive technical coverage with architecture-specific insights
-</output-block>
 
 ### 2. Scope Confirmation
 
 Present clear scope confirmation:
-
-<output-block>
-**Technical Research Scope Confirmation:**
+"**Technical Research Scope Confirmation:**
 
 For **{{research_topic}}**, I will research:
 
@@ -76,7 +71,6 @@ For **{{research_topic}}**, I will research:
 
 **Does this technical research scope and approach align with your goals?**
 [C] Continue - Begin technical research with this scope
-</output-block>
 
 ### 3. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md

@@ -41,9 +41,7 @@ Conduct technology stack analysis focusing on languages, frameworks, tools, and
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technology stack areas simultaneously and thoroughly.
 
 Start with technology stack research approach:
-
-<output-block>
-Now I'll conduct **technology stack analysis** for **{{research_topic}}** to understand the technology landscape.
+"Now I'll conduct **technology stack analysis** for **{{research_topic}}** to understand the technology landscape.
 
 **Technology Stack Focus:**
 
@@ -53,8 +51,7 @@ Now I'll conduct **technology stack analysis** for **{{research_topic}}** to und
 - Development tools and platforms
 - Cloud infrastructure and deployment platforms
 
-**Let me search for current technology stack insights.**
-</output-block>
+**Let me search for current technology stack insights.**"
 
 ### 2. Parallel Technology Stack Research Execution
 
@@ -77,8 +74,7 @@ Search the web: "{{research_topic}} cloud infrastructure platforms"
 
 **Collect and analyze findings from all parallel searches:**
 
-<output-block>
-After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings:
+"After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings:
 
 **Research Coverage:**
 
@@ -91,8 +87,7 @@ After executing comprehensive parallel web searches, let me analyze and aggregat
 [Identify patterns connecting language choices, frameworks, and platform decisions]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]
-</output-block>
+[Overall confidence levels and research gaps identified]"
 
 ### 4. Generate Technology Stack Content
 
@@ -166,8 +161,7 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-<output-block>
-I've completed **technology stack analysis** of the technology landscape for {{research_topic}}.
+"I've completed **technology stack analysis** of the technology landscape for {{research_topic}}.
 
 **Key Technology Stack Findings:**
 
@@ -179,7 +173,6 @@ I've completed **technology stack analysis** of the technology landscape for {{r
 
 **Ready to proceed to integration patterns analysis?**
 [C] Continue - Save this to document and proceed to integration patterns
-</output-block>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md

@@ -41,9 +41,7 @@ Conduct integration patterns analysis focusing on APIs, communication protocols,
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different integration areas simultaneously and thoroughly.
 
 Start with integration patterns research approach:
-
-<output-block>
-Now I'll conduct **integration patterns analysis** for **{{research_topic}}** to understand system integration approaches.
+"Now I'll conduct **integration patterns analysis** for **{{research_topic}}** to understand system integration approaches.
 
 **Integration Patterns Focus:**
 
@@ -53,8 +51,7 @@ Now I'll conduct **integration patterns analysis** for **{{research_topic}}** to
 - Microservices integration patterns
 - Event-driven architectures and messaging
 
-**Let me search for current integration patterns insights.**
-</output-block>
+**Let me search for current integration patterns insights.**"
 
 ### 2. Parallel Integration Patterns Research Execution
 
@@ -77,8 +74,7 @@ Search the web: "{{research_topic}} microservices integration patterns"
 
 **Collect and analyze findings from all parallel searches:**
 
-<output-block>
-After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings:
+"After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings:
 
 **Research Coverage:**
 
@@ -91,8 +87,7 @@ After executing comprehensive parallel web searches, let me analyze and aggregat
 [Identify patterns connecting API choices, communication protocols, and system design]
 
 **Quality Assessment:**
-[Overall confidence levels and research gaps identified]
-</output-block>
+[Overall confidence levels and research gaps identified]"
 
 ### 4. Generate Integration Patterns Content
 
@@ -175,8 +170,7 @@ _Source: [URL]_
 
 **Show analysis and present continue option:**
 
-<output-block>
-I've completed **integration patterns analysis** of system integration approaches for {{research_topic}}.
+"I've completed **integration patterns analysis** of system integration approaches for {{research_topic}}.
 
 **Key Integration Patterns Findings:**
 
@@ -188,7 +182,6 @@ I've completed **integration patterns analysis** of system integration approache
 
 **Ready to proceed to architectural patterns analysis?**
 [C] Continue - Save this to document and proceed to architectural patterns
-</output-block>
 
 ### 6. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md

@@ -39,9 +39,7 @@ Conduct comprehensive architectural patterns analysis with emphasis on design de
 ### 1. Begin Architectural Patterns Analysis
 
 Start with architectural research approach:
-
-<output-block>
-Now I'll focus on **architectural patterns and design decisions** for effective architecture approaches for [technology/domain].
+"Now I'll focus on **architectural patterns and design decisions** for effective architecture approaches for [technology/domain].
 
 **Architectural Patterns Focus:**
 
@@ -51,8 +49,7 @@ Now I'll focus on **architectural patterns and design decisions** for effective
 - Integration and communication patterns
 - Security and performance architectural considerations
 
-**Let me search for current architectural patterns and approaches.**
-</output-block>
+**Let me search for current architectural patterns and approaches.**"
 
 ### 2. Web Search for System Architecture Patterns
 
@@ -140,9 +137,7 @@ _Source: [URL]_
 ### 6. Present Analysis and Continue Option
 
 Show the generated architectural patterns and present continue option:
-
-<output-block>
-I've completed the **architectural patterns analysis** for effective architecture approaches.
+"I've completed the **architectural patterns analysis** for effective architecture approaches.
 
 **Key Architectural Findings:**
 
@@ -154,7 +149,6 @@ I've completed the **architectural patterns analysis** for effective architectur
 
 **Ready to proceed to implementation research?**
 [C] Continue - Save this to the document and move to implementation research
-</output-block>
 
 ### 7. Handle Continue Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md

@@ -36,9 +36,7 @@ Conduct comprehensive implementation research with emphasis on practical impleme
 ### 1. Begin Implementation Research
 
 Start with implementation research approach:
-
-<output-block>
-Now I'll complete our technical research with **implementation approaches and technology adoption** analysis.
+"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis.
 
 **Implementation Research Focus:**
 
@@ -48,8 +46,7 @@ Now I'll complete our technical research with **implementation approaches and te
 - Team organization and skill requirements
 - Cost optimization and resource management
 
-**Let me search for current implementation and adoption strategies.**
-</output-block>
+**Let me search for current implementation and adoption strategies.**"
 
 ### 2. Web Search for Technology Adoption
 
@@ -155,9 +152,7 @@ _Source: [URL]_
 ### 6. Present Analysis and Complete Option
 
 Show the generated implementation research and present complete option:
-
-<output-block>
-I've completed the **implementation research and technology adoption** analysis, finalizing our comprehensive technical research.
+"I've completed the **implementation research and technology adoption** analysis, finalizing our comprehensive technical research.
 
 **Implementation Highlights:**
 
@@ -176,7 +171,6 @@ I've completed the **implementation research and technology adoption** analysis,
 
 **Ready to complete the technical research report?**
 [C] Complete Research - Save final document and conclude
-</output-block>
 
 ### 7. Handle Complete Selection
 

src/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md

@@ -382,8 +382,7 @@ _This comprehensive technical research document serves as an authoritative techn
 
 **Technical Document Completion Presentation:**
 
-<output-block>
-I've completed the **comprehensive technical research document synthesis** for **{{research_topic}}**, producing an authoritative technical research document with:
+"I've completed the **comprehensive technical research document synthesis** for **{{research_topic}}**, producing an authoritative technical research document with:
 
 **Technical Document Features:**
 
@@ -412,7 +411,6 @@ I've completed the **comprehensive technical research document synthesis** for *
 
 **Ready to complete this comprehensive technical research document?**
 [C] Complete Research - Save final comprehensive technical document
-</output-block>
 
 ### 6. Handle Final Technical Completion
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01-init.md

@@ -121,8 +121,7 @@ Try to discover the following:
 
 **Setup Report to User:**
 
-<output-block>
-Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
+"Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
 
 **Document Setup:**
 
@@ -142,8 +141,7 @@ Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
 📋 **Note:** This is a **brownfield project**. Your existing project documentation has been loaded. In the next step, I'll ask specifically about what new features or changes you want to add to your existing system.
 {/if}
 
-Do you have any other documents you'd like me to include, or shall we continue to the next step?
-</output-block>
+Do you have any other documents you'd like me to include, or shall we continue to the next step?"
 
 ### 4. Present MENU OPTIONS
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-01b-continue.md

@@ -86,9 +86,7 @@ Review the frontmatter to understand:
 ### 4. Handle Workflow Completion
 
 **If `stepsCompleted` array contains `"step-11-complete.md"`:**
-
-<output-block>
-Great news! It looks like we've already completed the PRD workflow for {{project_name}}.
+"Great news! It looks like we've already completed the PRD workflow for {{project_name}}.
 
 The final document is ready at `{outputFile}` with all sections completed.
 
@@ -98,15 +96,12 @@ Would you like me to:
 - Suggest next workflow steps (like architecture or epic creation)
 - Start a new PRD revision
 
-What would be most helpful?
-</output-block>
+What would be most helpful?"
 
 ### 5. Present Current Progress
 
 **If workflow not complete:**
-
-<output-block>
-Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.
+"Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.
 
 **Current Progress:**
 - Last completed: {last step filename from stepsCompleted array}
@@ -117,8 +112,7 @@ Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_nam
 - Current PRD document is ready with all completed sections
 - Ready to continue from where we left off
 
-Does this look right, or do you want to make any adjustments before we proceed?
-</output-block>
+Does this look right, or do you want to make any adjustments before we proceed?"
 
 ### 6. Present MENU OPTIONS
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-02-discovery.md

@@ -83,24 +83,20 @@ Read the frontmatter from `{outputFile}` to get document counts:
 
 **Announce your understanding:**
 
-<output-block>
-From step 1, I have loaded:
+"From step 1, I have loaded:
 - Product briefs: {{briefCount}}
 - Research: {{researchCount}}
 - Brainstorming: {{brainstormingCount}}
 - Project docs: {{projectDocsCount}}
 
-{{if projectDocsCount > 0}}This is a brownfield project - I'll focus on understanding what you want to add or change.{{else}}This is a greenfield project - I'll help you define the full product vision.{{/if}}
-</output-block>
+{{if projectDocsCount > 0}}This is a brownfield project - I'll focus on understanding what you want to add or change.{{else}}This is a greenfield project - I'll help you define the full product vision.{{/if}}"
 
 ### 2. Load Classification Data
 
 **Attempt subprocess data lookup:**
 
 **Project Type Lookup:**
-
-<output-block>
-Your task: Lookup data in {projectTypesCSV}
+"Your task: Lookup data in {projectTypesCSV}
 
 **Search criteria:**
 - Find row where project_type matches {{detectedProjectType}}
@@ -109,13 +105,10 @@ Your task: Lookup data in {projectTypesCSV}
 Return ONLY the matching row as a YAML-formatted object with these fields:
 project_type, detection_signals
 
-**Do NOT return the entire CSV - only the matching row.**
-</output-block>
+**Do NOT return the entire CSV - only the matching row.**"
 
 **Domain Complexity Lookup:**
-
-<output-block>
-Your task: Lookup data in {domainComplexityCSV}
+"Your task: Lookup data in {domainComplexityCSV}
 
 **Search criteria:**
 - Find row where domain matches {{detectedDomain}}
@@ -124,8 +117,7 @@ Your task: Lookup data in {domainComplexityCSV}
 Return ONLY the matching row as a YAML-formatted object with these fields:
 domain, complexity, typical_concerns, compliance_requirements
 
-**Do NOT return the entire CSV - only the matching row.**
-</output-block>
+**Do NOT return the entire CSV - only the matching row.**"
 
 **Graceful degradation (if Task tool unavailable):**
 - Load the CSV files directly
@@ -155,14 +147,12 @@ As the user describes their product, match against:
 
 Once you have enough understanding, share your classification:
 
-<output-block>
-I'm hearing this as:
+"I'm hearing this as:
 - **Project Type:** {{detectedType}}
 - **Domain:** {{detectedDomain}}
 - **Complexity:** {{complexityLevel}}
 
-Does this sound right to you?
-</output-block>
+Does this sound right to you?"
 
 Let the user confirm or refine your classification.
 
@@ -181,8 +171,7 @@ classification:
 
 Present the project classification for review, then display menu:
 
-<output-block>
-Based on our conversation, I've discovered and classified your project.
+"Based on our conversation, I've discovered and classified your project.
 
 **Here's the classification:**
 
@@ -191,8 +180,7 @@ Based on our conversation, I've discovered and classified your project.
 **Complexity:** {{complexityLevel}}
 **Project Context:** {{greenfield|brownfield}}
 
-**What would you like to do?**
-</output-block>
+**What would you like to do?**"
 
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Product Vision (Step 2b of 13)"
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-05-domain.md

@@ -80,12 +80,9 @@ For complex domains, explore what makes this domain special:
 **If complexity is LOW:**
 
 Offer to skip:
-
-<output-block>
-The domain complexity from our discovery is low. We may not need deep domain-specific requirements. Would you like to:
+"The domain complexity from our discovery is low. We may not need deep domain-specific requirements. Would you like to:
 - [C] Skip this step and move to Innovation
-- [D] Do domain exploration anyway
-</output-block>
+- [D] Do domain exploration anyway"
 
 **If complexity is MEDIUM or HIGH:**
 
@@ -95,8 +92,7 @@ Proceed with domain exploration.
 
 **Attempt subprocess data lookup:**
 
-<output-block>
-Your task: Lookup data in {domainComplexityCSV}
+"Your task: Lookup data in {domainComplexityCSV}
 
 **Search criteria:**
 - Find row where domain matches {{domainFromStep02}}
@@ -105,8 +101,7 @@ Your task: Lookup data in {domainComplexityCSV}
 Return ONLY the matching row as a YAML-formatted object with these fields:
 domain, complexity, typical_concerns, compliance_requirements
 
-**Do NOT return the entire CSV - only the matching row.**
-</output-block>
+**Do NOT return the entire CSV - only the matching row.**"
 
 **Graceful degradation (if Task tool unavailable):**
 - Load the CSV file directly
@@ -152,9 +147,7 @@ Acknowledge the domain and explore what makes it complex:
 
 **Check with the user:**
 
-<output-block>
-Are there other domain-specific concerns we should consider? For [this domain], what typically gets overlooked?
-</output-block>
+"Are there other domain-specific concerns we should consider? For [this domain], what typically gets overlooked?"
 
 ### N. Present MENU OPTIONS
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-07-project-type.md

@@ -55,8 +55,7 @@ Conduct project-type specific discovery using CSV-driven guidance to define tech
 
 **Attempt subprocess data lookup:**
 
-<output-block>
-Your task: Lookup data in {projectTypesCSV}
+"Your task: Lookup data in {projectTypesCSV}
 
 **Search criteria:**
 - Find row where project_type matches {{projectTypeFromStep02}}
@@ -65,8 +64,7 @@ Your task: Lookup data in {projectTypesCSV}
 Return ONLY the matching row as a YAML-formatted object with these fields:
 project_type, key_questions, required_sections, skip_sections, innovation_signals
 
-**Do NOT return the entire CSV - only the matching row.**
-</output-block>
+**Do NOT return the entire CSV - only the matching row.**"
 
 **Graceful degradation (if Task tool unavailable):**
 - Load the CSV file directly
@@ -163,15 +161,13 @@ When saving to document, append these Level 2 and Level 3 sections:
 
 Present the project-type content for review, then display menu:
 
-<output-block>
-Based on our conversation and best practices for this product type, I've documented the {project_type}-specific requirements for {{project_name}}.
+"Based on our conversation and best practices for this product type, I've documented the {project_type}-specific requirements for {{project_name}}.
 
 **Here's what I'll add to the document:**
 
 [Show the complete markdown content from section 5]
 
-**What would you like to do?**
-</output-block>
+**What would you like to do?**"
 
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Scoping (Step 8 of 11)"
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-08-scoping.md

@@ -117,14 +117,11 @@ Create phased development approach:
 Identify and mitigate scoping risks:
 
 **Technical Risks:**
-
-<output-block>
-Looking at your innovation and domain requirements:
+"Looking at your innovation and domain requirements:
 
 - What's the most technically challenging aspect?
 - Could we simplify the initial implementation?
-- What's the riskiest assumption about technology feasibility?
-</output-block>
+- What's the riskiest assumption about technology feasibility?"
 
 **Market Risks:**
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01-discovery.md

@@ -70,13 +70,11 @@ This file defines what makes a great BMAD PRD. Internalize this understanding -
 
 ### 2. Discover PRD to Edit
 
-<output-block>
-**PRD Edit Workflow**
+"**PRD Edit Workflow**
 
 Which PRD would you like to edit?
 
-Please provide the path to the PRD file you want to edit.
-</output-block>
+Please provide the path to the PRD file you want to edit."
 
 **Wait for user to provide PRD path.**
 
@@ -99,8 +97,7 @@ ls -t {prd_folder_path}/validation-report-*.md 2>/dev/null | head -1
 **If validation report found:**
 
 Display:
-<output-block>
-**📋 Found Validation Report**
+"**📋 Found Validation Report**
 
 I found a validation report from {validation_date} in the PRD folder.
 
@@ -108,8 +105,7 @@ This report contains findings from previous validation checks and can help guide
 
 **Would you like to:**
 - **[U] Use validation report** - Load it to guide and prioritize edits
-- **[S] Skip** - Proceed with manual edit discovery
-</output-block>
+- **[S] Skip** - Proceed with manual edit discovery"
 
 **Wait for user input.**
 
@@ -129,13 +125,11 @@ This report contains findings from previous validation checks and can help guide
 
 ### 5. Ask About Validation Report
 
-<output-block>
-**Do you have a validation report to guide edits?**
+"**Do you have a validation report to guide edits?**
 
 If you've run the validation workflow on this PRD, I can use that report to guide improvements and prioritize changes.
 
-Validation report path (or type 'none'):
-</output-block>
+Validation report path (or type 'none'):"
 
 **Wait for user input.**
 
@@ -150,8 +144,7 @@ Validation report path (or type 'none'):
 
 ### 6. Discover Edit Requirements
 
-<output-block>
-**What would you like to edit in this PRD?**
+"**What would you like to edit in this PRD?**
 
 Please describe the changes you want to make. For example:
 - Fix specific issues (information density, implementation leakage, etc.)
@@ -161,8 +154,7 @@ Please describe the changes you want to make. For example:
 - General improvements
 - Other changes
 
-**Describe your edit goals:**
-</output-block>
+**Describe your edit goals:**"
 
 **Wait for user to describe their requirements.**
 
@@ -189,31 +181,25 @@ Analyze the loaded PRD:
 
 **IF validation report provided OR PRD is BMAD Standard/Variant:**
 
-Display:
-<output-block>
-**Edit Requirements Understood**
+Display: "**Edit Requirements Understood**
 
 **PRD Format:** {classification}
 {If validation report: "**Validation Guide:** Yes - will use validation report findings"}
 **Edit Goals:** {summary of user's requirements}
 
-**Proceeding to deep review and analysis...**
-</output-block>
+**Proceeding to deep review and analysis...**"
 
 Read fully and follow: next step (step-e-02-review.md)
 
 **IF PRD is Legacy (Non-Standard) AND no validation report:**
 
-Display:
-<output-block>
-**Format Detected:** Legacy PRD
+Display: "**Format Detected:** Legacy PRD
 
 This PRD does not follow BMAD standard structure (only {count}/6 core sections present).
 
 **Your edit goals:** {user's requirements}
 
-**How would you like to proceed?**
-</output-block>
+**How would you like to proceed?**"
 
 Present MENU OPTIONS below for user selection
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-01b-legacy-conversion.md

@@ -128,8 +128,7 @@ Return conversion assessment with gap analysis and effort estimate."
 
 Display:
 
-<output-block>
-**Legacy PRD Conversion Assessment**
+"**Legacy PRD Conversion Assessment**
 
 **Current PRD Structure:**
 - Core sections present: {count}/6
@@ -147,8 +146,7 @@ Display:
 **Recommendation:**
 {Based on effort and user goals, recommend best approach}
 
-**How would you like to proceed?**
-</output-block>
+**How would you like to proceed?**"
 
 ### 4. Present MENU OPTIONS
 
@@ -177,15 +175,12 @@ Store conversion decision for next step:
 - **Edit requirements:** [user's requirements from step e-01]
 - **Gap analysis:** [summary of gaps identified]
 
-Display:
-<output-block>
-**Conversion Strategy Documented**
+Display: "**Conversion Strategy Documented**
 
 Mode: {conversion mode}
 Edit goals: {summary}
 
-**Proceeding to deep review...**
-</output-block>
+**Proceeding to deep review...**"
 
 Read fully and follow: {nextStepFile} (step-e-02-review.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-02-review.md

@@ -146,8 +146,7 @@ Return detailed change plan with section breakdown."
 
 Display:
 
-<output-block>
-**Deep Review Complete - Change Plan**
+"**Deep Review Complete - Change Plan**
 
 **PRD Analysis:**
 {Brief summary of PRD current state}
@@ -176,8 +175,7 @@ Display:
 2. Any sections I should add/remove/reprioritize?
 3. Any concerns before I proceed with edits?
 
-**Review the plan and let me know if you'd like any adjustments.**
-</output-block>
+**Review the plan and let me know if you'd like any adjustments.**"
 
 ### 5. Get User Confirmation
 
@@ -200,14 +198,11 @@ Store approved change plan for next step:
 - **Priority order:** Sequence to apply changes
 - **User confirmed:** Yes
 
-Display:
-<output-block>
-**Change Plan Approved**
+Display: "**Change Plan Approved**
 
 {Brief summary of approved plan}
 
-**Proceeding to edit step...**
-</output-block>
+**Proceeding to edit step...**"
 
 Read fully and follow: {nextStepFile} (step-e-03-edit.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-03-edit.md

@@ -64,16 +64,13 @@ From step e-02, retrieve:
 - **Priority order:** Sequence to apply changes
 - **User requirements:** Edit goals from step e-01
 
-Display:
-<output-block>
-**Starting PRD Edits**
+Display: "**Starting PRD Edits**
 
 **Change Plan:** {summary}
 **Total Changes:** {count}
 **Estimated Effort:** {effort level}
 
-**Proceeding with edits section by section...**
-</output-block>
+**Proceeding with edits section by section...**"
 
 ### 2. Attempt Sub-Process Edits (For Complex Changes)
 
@@ -123,11 +120,9 @@ Apply changes and return updated section."
 - Verify changes applied correctly
 
 **Display progress after each section:**
-<output-block>
-**Section Updated:** {section_name}
+"**Section Updated:** {section_name}
 Changes: {brief summary}
-{More sections remaining...}
-</output-block>
+{More sections remaining...}"
 
 ### 4. Handle Restructuring (If Needed)
 
@@ -150,12 +145,9 @@ Changes: {brief summary}
 8. Functional Requirements
 9. Non-Functional Requirements
 
-Display:
-<output-block>
-**PRD Restructured**
+Display: "**PRD Restructured**
 BMAD standard structure applied.
-{Sections added/reordered}
-</output-block>
+{Sections added/reordered}"
 
 ### 5. Update PRD Frontmatter
 
@@ -202,8 +194,7 @@ editHistory:
 
 Display:
 
-<output-block>
-**PRD Edits Complete**
+"**PRD Edits Complete**
 
 **Changes Applied:** {count} sections modified
 **PRD Updated:** {prd_file_path}
@@ -215,8 +206,7 @@ Display:
 - Use in downstream workflows (UX, Architecture)
 - Validation (if not yet validated)
 
-**What would you like to do next?**
-</output-block>
+**What would you like to do next?**"
 
 ### 8. Present MENU OPTIONS
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md

@@ -80,8 +80,7 @@ From step e-03 change execution, compile:
 
 Display:
 
-<output-block>
-**✓ PRD Edit Complete**
+"**✓ PRD Edit Complete**
 
 **Updated PRD:** {prd_file_path}
 
@@ -98,8 +97,7 @@ Display:
 - Validation to ensure quality
 - Production use
 
-**What would you like to do next?**
-</output-block>
+**What would you like to do next?**"
 
 ### 3. Present MENU OPTIONS
 
@@ -118,16 +116,10 @@ Display:
 #### Menu Handling Logic:
 
 - **IF V (Run Full Validation):**
-  - Display:
-    <output-block>
-    **Starting Validation Workflow**
-
-    This will run all 13 validation checks on the updated PRD.
-
-    Preparing to validate: {prd_file_path}
-
-    **Proceeding to validation...**
-    </output-block>
+  - Display: "**Starting Validation Workflow**"
+  - Display: "This will run all 13 validation checks on the updated PRD."
+  - Display: "Preparing to validate: {prd_file_path}"
+  - Display: "**Proceeding to validation...**"
   - Read fully and follow: {validationWorkflow} (steps-v/step-v-01-discovery.md)
   - Note: This hands off to the validation workflow which will run its complete 13-step process
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md

@@ -71,14 +71,11 @@ This file contains the BMAD PRD philosophy, standards, and validation criteria t
 - Use provided path
 
 **If no PRD path provided:**
-
-<output-block>
-**PRD Validation Workflow**
+"**PRD Validation Workflow**
 
 Which PRD would you like to validate?
 
-Please provide the path to the PRD file you want to validate.
-</output-block>
+Please provide the path to the PRD file you want to validate."
 
 **Wait for user to provide PRD path.**
 
@@ -115,8 +112,7 @@ For each document listed in `inputDocuments`:
 
 ### 6. Ask About Additional Reference Documents
 
-<output-block>
-**I've loaded the following documents from your PRD frontmatter:**
+"**I've loaded the following documents from your PRD frontmatter:**
 
 {list loaded documents with file names}
 
@@ -128,8 +124,7 @@ These could include:
 - Standards or compliance documents
 - Competitive analysis or benchmarks
 
-Please provide paths to any additional documents, or type 'none' to proceed.
-</output-block>
+Please provide paths to any additional documents, or type 'none' to proceed."
 
 **Load any additional documents provided by user.**
 
@@ -166,8 +161,7 @@ validationStatus: IN_PROGRESS
 
 ### 8. Present Discovery Summary
 
-<output-block>
-**Setup Complete!**
+"**Setup Complete!**
 
 **PRD to Validate:** {prd_path}
 
@@ -179,16 +173,11 @@ validationStatus: IN_PROGRESS
 
 **Validation Report:** {validationReportPath}
 
-**Ready to begin validation.**
-</output-block>
+**Ready to begin validation.**"
 
 ### 9. Present MENU OPTIONS
 
-Display:
-
-<output-block>
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Format Detection
-</output-block>
+Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Format Detection
 
 #### EXECUTION RULES:
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02-format-detection.md

@@ -132,27 +132,19 @@ Append to validation report:
 
 **IF format is BMAD Standard or BMAD Variant:**
 
-Display:
+Display: "**Format Detected:** {classification}
 
-<output-block>
-**Format Detected:** {classification}
-
-Proceeding to systematic validation checks...
-</output-block>
+Proceeding to systematic validation checks..."
 
 Without delay, read fully and follow: {nextStepFile} (step-v-03-density-validation.md)
 
 **IF format is Non-Standard (< 3 core sections):**
 
-Display:
-
-<output-block>
-**Format Detected:** Non-Standard PRD
+Display: "**Format Detected:** Non-Standard PRD
 
 This PRD does not follow BMAD standard structure (only {count}/6 core sections present).
 
-You have options:
-</output-block>
+You have options:"
 
 Present MENU OPTIONS below for user selection
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-02b-parity-check.md

@@ -155,8 +155,7 @@ Append to validation report:
 
 Display:
 
-<output-block>
-**Parity Analysis Complete**
+"**Parity Analysis Complete**
 
 Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to reach BMAD standard is: **{effort level}**
 
@@ -166,8 +165,7 @@ Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to r
 **Recommendation:**
 {recommendation from analysis}
 
-**How would you like to proceed?**
-</output-block>
+**How would you like to proceed?**"
 
 ### 5. Present MENU OPTIONS
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-03-density-validation.md

@@ -142,15 +142,11 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**Information Density Validation Complete**
+Display: "**Information Density Validation Complete**
 
 Severity: {Critical/Warning/Pass}
 
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-04-brief-coverage-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-04-brief-coverage-validation.md

@@ -72,13 +72,9 @@ Append to validation report:
 **Status:** N/A - No Product Brief was provided as input
 ```
 
-Display:
+Display: "**Product Brief Coverage: Skipped** (No Product Brief provided)
 
-<output-block>
-**Product Brief Coverage: Skipped** (No Product Brief provided)
-
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile}
 
@@ -184,15 +180,11 @@ Append to validation report:
 
 ### 6. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**Product Brief Coverage Validation Complete**
+Display: "**Product Brief Coverage Validation Complete**
 
 Overall Coverage: {assessment}
 
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-05-measurability-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-05-measurability-validation.md

@@ -195,15 +195,11 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**Measurability Validation Complete**
+Display: "**Measurability Validation Complete**
 
 Total Violations: {count} ({severity})
 
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-06-traceability-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-06-traceability-validation.md

@@ -183,15 +183,11 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**Traceability Validation Complete**
+Display: "**Traceability Validation Complete**
 
 Total Issues: {count} ({severity})
 
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-07-implementation-leakage-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-07-implementation-leakage-validation.md

@@ -172,15 +172,11 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**Implementation Leakage Validation Complete**
+Display: "**Implementation Leakage Validation Complete**
 
 Total Violations: {count} ({severity})
 
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-08-domain-compliance-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-08-domain-compliance-validation.md

@@ -155,15 +155,11 @@ Append to validation report:
 **Note:** This PRD is for a standard domain without regulatory compliance requirements.
 ```
 
-Display:
-
-<output-block>
-**Domain Compliance Validation Skipped**
+Display: "**Domain Compliance Validation Skipped**
 
 Domain: {domain} (low complexity)
 
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile}
 
@@ -210,16 +206,12 @@ Append to validation report:
 
 ### 7. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**Domain Compliance Validation Complete**
+Display: "**Domain Compliance Validation Complete**
 
 Domain: {domain} ({complexity})
 Compliance Status: {status}
 
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-09-project-type-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-09-project-type-validation.md

@@ -227,16 +227,12 @@ Append to validation report:
 
 ### 7. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**Project-Type Compliance Validation Complete**
+Display: "**Project-Type Compliance Validation Complete**
 
 Project Type: {projectType}
 Compliance: {score}%
 
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-10-smart-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md

@@ -173,15 +173,11 @@ Append to validation report:
 
 ### 5. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**SMART Requirements Validation Complete**
+Display: "**SMART Requirements Validation Complete**
 
 FR Quality: {percentage}% with acceptable scores ({severity})
 
-**Proceeding to next validation check...**
-</output-block>
+**Proceeding to next validation check...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-11-holistic-quality-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md

@@ -226,15 +226,11 @@ Append to validation report:
 
 ### 4. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**Holistic Quality Assessment Complete**
+Display: "**Holistic Quality Assessment Complete**
 
 Overall Rating: {rating}/5 - {label}
 
-**Proceeding to final validation checks...**
-</output-block>
+**Proceeding to final validation checks...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-12-completeness-validation.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-12-completeness-validation.md

@@ -206,15 +206,11 @@ Append to validation report:
 
 ### 4. Display Progress and Auto-Proceed
 
-Display:
-
-<output-block>
-**Completeness Validation Complete**
+Display: "**Completeness Validation Complete**
 
 Overall Completeness: {percentage}% ({severity})
 
-**Proceeding to final step...**
-</output-block>
+**Proceeding to final step...**"
 
 Without delay, read fully and follow: {nextStepFile} (step-v-13-report-complete.md)
 

src/bmm/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md

@@ -125,8 +125,7 @@ overallStatus: '{Pass/Warning/Critical based on all findings}'
 
 Display:
 
-<output-block>
-**✓ PRD Validation Complete**
+"**✓ PRD Validation Complete**
 
 **Overall Status:** {Pass/Warning/Critical}
 
@@ -155,8 +154,7 @@ Display:
 - Warning: "PRD is usable but has issues that should be addressed. Review warnings and improve where needed."
 - Critical: "PRD has significant issues that should be fixed before use. Focus on critical issues above."}
 
-**What would you like to do next?**
-</output-block>
+**What would you like to do next?**"
 
 ### 5. Present MENU OPTIONS
 
@@ -197,12 +195,8 @@ Display:
   - Return to menu
 
 - **IF X (Exit):**
-  - Display:
-    <output-block>
-    **Validation Report Saved:** {validationReportPath}
-
-    **Summary:** {overall status} - {recommendation}
-    </output-block>
+  - Display: "**Validation Report Saved:** {validationReportPath}"
+  - Display: "**Summary:** {overall status} - {recommendation}"
   - PRD Validation complete. Read fully and follow: `_bmad/core/tasks/bmad-help.md` with argument `Validate PRD`.
 
 - **IF Any other:** Help user, then redisplay menu

src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md

@@ -8,7 +8,7 @@ validationStatus: COMPLETE - PRODUCTION READY
 
 # PRD Workflow Validation Report
 
-**Workflow Being Validated:** _bmad/bmm/workflows/2-plan-workflows/create-prd
+**Workflow Being Validated:** /Users/brianmadison/dev/BMAD-METHOD/src/bmm/workflows/2-plan-workflows/create-prd
 **Validation Date:** 2026-01-08
 **Validator:** BMAD Workflow Validation System
 

src/bmm/workflows/2-plan-workflows/create-prd/workflow.md

@@ -40,53 +40,30 @@ Determine which mode to invoke based on:
 3. **Menu Selection (if unclear):**
 
 If mode cannot be determined from invocation:
-
-<output-block>
-**PRD Workflow - Select Mode:**
+"**PRD Workflow - Select Mode:**
 
 **[C] Create** - Create a new PRD from scratch
 **[V] Validate** - Validate an existing PRD against BMAD standards
 **[E] Edit** - Improve an existing PRD
 
-Which mode would you like?
-</output-block>
+Which mode would you like?"
 
 Wait for user selection.
 
 ### Route to Appropriate Workflow
 
 **IF Create Mode:**
-
-<output-block>
-**Create Mode: Creating a new PRD from scratch.**
-</output-block>
-
+"**Create Mode: Creating a new PRD from scratch.**"
 Read fully and follow: `{nextStep}` (steps-c/step-01-init.md)
 
 **IF Validate Mode:**
-
-<output-block>
-**Validate Mode: Validating an existing PRD against BMAD standards.**
-</output-block>
-
-Prompt for PRD path:
-
-<output-block>
-Which PRD would you like to validate? Please provide the path to the PRD.md file.
-</output-block>
+"**Validate Mode: Validating an existing PRD against BMAD standards.**"
+Prompt for PRD path: "Which PRD would you like to validate? Please provide the path to the PRD.md file."
 Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
 
 **IF Edit Mode:**
-
-<output-block>
-**Edit Mode: Improving an existing PRD.**
-</output-block>
-
-Prompt for PRD path:
-
-<output-block>
-Which PRD would you like to edit? Please provide the path to the PRD.md file.
-</output-block>
+"**Edit Mode: Improving an existing PRD.**"
+Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
 Then read fully and follow: `{editWorkflow}` (steps-e/step-e-01-discovery.md)
 
 ---
@@ -136,15 +113,13 @@ This uses **step-file architecture** for disciplined execution:
 
 **If mode is still unclear, ask user:**
 
-<output-block>
-**PRD Workflow - Select Mode:**
+"**PRD Workflow - Select Mode:**
 
 **[C] Create** - Create a new PRD from scratch
 **[V] Validate** - Validate an existing PRD against BMAD standards
 **[E] Edit** - Improve an existing PRD
 
-Which mode would you like?
-</output-block>
+Which mode would you like?"
 
 Wait for user selection.
 
@@ -161,37 +136,15 @@ Load and read full config from {main_config} and resolve:
 ### 3. Route to Appropriate Workflow
 
 **IF mode == create:**
-
-<output-block>
-**Create Mode: Creating a new PRD from scratch.**
-</output-block>
-
+"**Create Mode: Creating a new PRD from scratch.**"
 Read fully and follow: `{nextStep}` (steps-c/step-01-init.md)
 
 **IF mode == validate:**
-
-<output-block>
-**Validate Mode: Validating an existing PRD against BMAD standards.**
-</output-block>
-
-Prompt for PRD path:
-
-<output-block>
-Which PRD would you like to validate? Please provide the path to the PRD.md file.
-</output-block>
-
+"**Validate Mode: Validating an existing PRD against BMAD standards.**"
+Prompt for PRD path: "Which PRD would you like to validate? Please provide the path to the PRD.md file."
 Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
 
 **IF mode == edit:**
-
-<output-block>
-**Edit Mode: Improving an existing PRD.**
-</output-block>
-
-Prompt for PRD path:
-
-<output-block>
-Which PRD would you like to edit? Please provide the path to the PRD.md file.
-</output-block>
-
+"**Edit Mode: Improving an existing PRD.**"
+Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
 Then read fully and follow: `{editWorkflow}` (steps-e/step-e-01-discovery.md)

src/bmm/workflows/generate-project-context/project-context-template.md

@@ -1,21 +0,0 @@
----
-project_name: '{{project_name}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
-sections_completed: ['technology_stack']
-existing_patterns_found: { { number_of_patterns_discovered } }
----
-
-# Project Context for AI Agents
-
-_This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._
-
----
-
-## Technology Stack & Versions
-
-_Documented after discovery phase_
-
-## Critical Implementation Rules
-
-_Documented after discovery phase_

src/bmm/workflows/generate-project-context/steps/step-01-discover.md

@@ -1,184 +0,0 @@
-# Step 1: Context Discovery & Initialization
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user input
-- ✅ ALWAYS treat this as collaborative discovery between technical peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on discovering existing project context and technology stack
-- 🎯 IDENTIFY critical implementation rules that AI agents need
-- ⚠️ 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}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 📖 Read existing project files to understand current context
-- 💾 Initialize document and update frontmatter
-- 🚫 FORBIDDEN to load next step until discovery is complete
-
-## CONTEXT BOUNDARIES:
-
-- Variables from workflow.md are available in memory
-- Focus on existing project files and architecture decisions
-- Look for patterns, conventions, and unique requirements
-- Prioritize rules that prevent implementation mistakes
-
-## YOUR TASK:
-
-Discover the project's technology stack, existing patterns, and critical implementation rules that AI agents must follow when writing code.
-
-## DISCOVERY SEQUENCE:
-
-### 1. Check for Existing Project Context
-
-First, check if project context already exists:
-
-- Look for file at `{project_knowledge}/project-context.md or {project-root}/**/project-context.md`
-- If exists: Read complete file to understand existing rules
-- Present to user: "Found existing project context with {number_of_sections} sections. Would you like to update this or create a new one?"
-
-### 2. Discover Project Technology Stack
-
-Load and analyze project files to identify technologies:
-
-**Architecture Document:**
-
-- Look for `{planning_artifacts}/architecture.md`
-- Extract technology choices with specific versions
-- Note architectural decisions that affect implementation
-
-**Package Files:**
-
-- Check for `package.json`, `requirements.txt`, `Cargo.toml`, etc.
-- Extract exact versions of all dependencies
-- Note development vs production dependencies
-
-**Configuration Files:**
-
-- Look for project language specific configs ( example: `tsconfig.json`)
-- Build tool configs (webpack, vite, next.config.js, etc.)
-- Linting and formatting configs (.eslintrc, .prettierrc, etc.)
-- Testing configurations (jest.config.js, vitest.config.ts, etc.)
-
-### 3. Identify Existing Code Patterns
-
-Search through existing codebase for patterns:
-
-**Naming Conventions:**
-
-- File naming patterns (PascalCase, kebab-case, etc.)
-- Component/function naming conventions
-- Variable naming patterns
-- Test file naming patterns
-
-**Code Organization:**
-
-- How components are structured
-- Where utilities and helpers are placed
-- How services are organized
-- Test organization patterns
-
-**Documentation Patterns:**
-
-- Comment styles and conventions
-- Documentation requirements
-- README and API doc patterns
-
-### 4. Extract Critical Implementation Rules
-
-Look for rules that AI agents might miss:
-
-**Language-Specific Rules:**
-
-- TypeScript strict mode requirements
-- Import/export conventions
-- Async/await vs Promise usage patterns
-- Error handling patterns specific to the language
-
-**Framework-Specific Rules:**
-
-- React hooks usage patterns
-- API route conventions
-- Middleware usage patterns
-- State management patterns
-
-**Testing Rules:**
-
-- Test structure requirements
-- Mock usage conventions
-- Integration vs unit test boundaries
-- Coverage requirements
-
-**Development Workflow Rules:**
-
-- Branch naming conventions
-- Commit message patterns
-- PR review requirements
-- Deployment procedures
-
-### 5. Initialize Project Context Document
-
-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`
-Initialize frontmatter fields.
-
-#### B. Existing Document Update
-
-Load existing context and prepare for updates
-Set frontmatter `sections_completed` to track what will be updated
-
-### 6. Present Discovery Summary
-
-Report findings to user:
-
-"Welcome {{user_name}}! I've analyzed your project for {{project_name}} to discover the context that AI agents need.
-
-**Technology Stack Discovered:**
-{{list_of_technologies_with_versions}}
-
-**Existing Patterns Found:**
-
-- {{number_of_patterns}} implementation patterns
-- {{number_of_conventions}} coding conventions
-- {{number_of_rules}} critical rules
-
-**Key Areas for Context Rules:**
-
-- {{area_1}} (e.g., TypeScript configuration)
-- {{area_2}} (e.g., Testing patterns)
-- {{area_3}} (e.g., Code organization)
-
-{if_existing_context}
-**Existing Context:** Found {{sections}} sections already defined. We can update or add to these.
-{/if_existing_context}
-
-Ready to create/update your project context. This will help AI agents implement code consistently with your project's standards.
-
-[C] Continue to context generation"
-
-## SUCCESS METRICS:
-
-✅ Existing project context properly detected and handled
-✅ Technology stack accurately identified with versions
-✅ Critical implementation patterns discovered
-✅ Project context document properly initialized
-✅ Discovery findings clearly presented to user
-✅ User ready to proceed with context generation
-
-## FAILURE MODES:
-
-❌ Not checking for existing project context before creating new one
-❌ Missing critical technology versions or configurations
-❌ Overlooking important coding patterns or conventions
-❌ Not initializing frontmatter properly
-❌ Not presenting clear discovery summary to user
-
-## NEXT STEP:
-
-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!

src/bmm/workflows/generate-project-context/steps/step-02-generate.md

@@ -1,318 +0,0 @@
-# Step 2: Context Rules Generation
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user input
-- ✅ ALWAYS treat this as collaborative discovery between technical peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on unobvious rules that AI agents need to be reminded of
-- 🎯 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}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 📝 Focus on specific, actionable rules rather than general advice
-- ⚠️ Present A/P/C menu after each major rule category
-- 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter with completed sections
-- 🚫 FORBIDDEN to load next step until all sections are complete
-
-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices for each rule category:
-
-- **A (Advanced Elicitation)**: Use discovery protocols to explore nuanced implementation rules
-- **P (Party Mode)**: Bring multiple perspectives to identify critical edge cases
-- **C (Continue)**: Save the current rules and proceed to next category
-
-## PROTOCOL INTEGRATION:
-
-- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
-- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode
-- 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
-
-## CONTEXT BOUNDARIES:
-
-- Discovery results from step-1 are available
-- Technology stack and existing patterns are identified
-- Focus on rules that prevent implementation mistakes
-- Prioritize unobvious details that AI agents might miss
-
-## YOUR TASK:
-
-Collaboratively generate specific, critical rules that AI agents must follow when implementing code in this project.
-
-## CONTEXT GENERATION SEQUENCE:
-
-### 1. Technology Stack & Versions
-
-Document the exact technology stack from discovery:
-
-**Core Technologies:**
-Based on user skill level, present findings:
-
-**Expert Mode:**
-"Technology stack from your architecture and package files:
-{{exact_technologies_with_versions}}
-
-Any critical version constraints I should document for agents?"
-
-**Intermediate Mode:**
-"I found your technology stack:
-
-**Core Technologies:**
-{{main_technologies_with_versions}}
-
-**Key Dependencies:**
-{{important_dependencies_with_versions}}
-
-Are there any version constraints or compatibility notes agents should know about?"
-
-**Beginner Mode:**
-"Here are the technologies you're using:
-
-**Main Technologies:**
-{{friendly_description_of_tech_stack}}
-
-**Important Notes:**
-{{key_things_agents_need_to_know_about_versions}}
-
-Should I document any special version rules or compatibility requirements?"
-
-### 2. Language-Specific Rules
-
-Focus on unobvious language patterns agents might miss:
-
-**TypeScript/JavaScript Rules:**
-"Based on your codebase, I notice some specific patterns:
-
-**Configuration Requirements:**
-{{typescript_config_rules}}
-
-**Import/Export Patterns:**
-{{import_export_conventions}}
-
-**Error Handling Patterns:**
-{{error_handling_requirements}}
-
-Are these patterns correct? Any other language-specific rules agents should follow?"
-
-**Python/Ruby/Other Language Rules:**
-Adapt to the actual language in use with similar focused questions.
-
-### 3. Framework-Specific Rules
-
-Document framework-specific patterns:
-
-**React Rules (if applicable):**
-"For React development, I see these patterns:
-
-**Hooks Usage:**
-{{hooks_usage_patterns}}
-
-**Component Structure:**
-{{component_organization_rules}}
-
-**State Management:**
-{{state_management_patterns}}
-
-**Performance Rules:**
-{{performance_optimization_requirements}}
-
-Should I add any other React-specific rules?"
-
-**Other Framework Rules:**
-Adapt for Vue, Angular, Next.js, Express, etc.
-
-### 4. Testing Rules
-
-Focus on testing patterns that ensure consistency:
-
-**Test Structure Rules:**
-"Your testing setup shows these patterns:
-
-**Test Organization:**
-{{test_file_organization}}
-
-**Mock Usage:**
-{{mock_patterns_and_conventions}}
-
-**Test Coverage Requirements:**
-{{coverage_expectations}}
-
-**Integration vs Unit Test Rules:**
-{{test_boundary_patterns}}
-
-Are there testing rules agents should always follow?"
-
-### 5. Code Quality & Style Rules
-
-Document critical style and quality rules:
-
-**Linting/Formatting:**
-"Your code style configuration requires:
-
-**ESLint/Prettier Rules:**
-{{specific_linting_rules}}
-
-**Code Organization:**
-{{file_and_folder_structure_rules}}
-
-**Naming Conventions:**
-{{naming_patterns_agents_must_follow}}
-
-**Documentation Requirements:**
-{{comment_and_documentation_patterns}}
-
-Any additional code quality rules?"
-
-### 6. Development Workflow Rules
-
-Document workflow patterns that affect implementation:
-
-**Git/Repository Rules:**
-"Your project uses these patterns:
-
-**Branch Naming:**
-{{branch_naming_conventions}}
-
-**Commit Message Format:**
-{{commit_message_patterns}}
-
-**PR Requirements:**
-{{pull_request_checklist}}
-
-**Deployment Patterns:**
-{{deployment_considerations}}
-
-Should I document any other workflow rules?"
-
-### 7. Critical Don't-Miss Rules
-
-Identify rules that prevent common mistakes:
-
-**Anti-Patterns to Avoid:**
-"Based on your codebase, here are critical things agents must NOT do:
-
-{{critical_anti_patterns_with_examples}}
-
-**Edge Cases:**
-{{specific_edge_cases_agents_should_handle}}
-
-**Security Rules:**
-{{security_considerations_agents_must_follow}}
-
-**Performance Gotchas:**
-{{performance_patterns_to_avoid}}
-
-Are there other 'gotchas' agents should know about?"
-
-### 8. Generate Context Content
-
-For each category, prepare lean content for the project context file:
-
-#### Content Structure:
-
-```markdown
-## Technology Stack & Versions
-
-{{concise_technology_list_with_exact_versions}}
-
-## Critical Implementation Rules
-
-### Language-Specific Rules
-
-{{bullet_points_of_critical_language_rules}}
-
-### Framework-Specific Rules
-
-{{bullet_points_of_framework_patterns}}
-
-### Testing Rules
-
-{{bullet_points_of_testing_requirements}}
-
-### Code Quality & Style Rules
-
-{{bullet_points_of_style_and_quality_rules}}
-
-### Development Workflow Rules
-
-{{bullet_points_of_workflow_patterns}}
-
-### Critical Don't-Miss Rules
-
-{{bullet_points_of_anti_patterns_and_edge_cases}}
-```
-
-### 9. Present Content and Menu
-
-After each category, show the generated rules and present choices:
-
-"I've drafted the {{category_name}} rules for your project context.
-
-**Here's what I'll add:**
-
-[Show the complete markdown content for this category]
-
-**What would you like to do?**
-[A] Advanced Elicitation - Explore nuanced rules for this category
-[P] Party Mode - Review from different implementation perspectives
-[C] Continue - Save these rules and move to next category"
-
-### 10. Handle Menu Selection
-
-#### If 'A' (Advanced Elicitation):
-
-- Execute advanced-elicitation.xml 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
-- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
-- Execute party-mode workflow 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
-- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
-- Save the current category content to project context file
-- Update frontmatter: `sections_completed: [...]`
-- Proceed to next category or step-03 if complete
-
-## APPEND TO PROJECT CONTEXT:
-
-When user selects 'C' for a category, append the content directly to `{output_folder}/project-context.md` using the structure from step 8.
-
-## SUCCESS METRICS:
-
-✅ All critical technology versions accurately documented
-✅ Language-specific rules cover unobvious patterns
-✅ Framework rules capture project-specific conventions
-✅ Testing rules ensure consistent test quality
-✅ Code quality rules maintain project standards
-✅ Workflow rules prevent implementation conflicts
-✅ Content is lean and optimized for LLM context
-✅ A/P/C menu presented and handled correctly for each category
-
-## FAILURE MODES:
-
-❌ Including obvious rules that agents already know
-❌ Making content too verbose for LLM context efficiency
-❌ Missing critical anti-patterns or edge cases
-❌ Not getting user validation for each rule category
-❌ Not documenting exact versions and configurations
-❌ Not presenting A/P/C menu after content generation
-
-## NEXT STEP:
-
-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!

src/bmm/workflows/generate-project-context/steps/step-03-complete.md

@@ -1,278 +0,0 @@
-# Step 3: Context Completion & Finalization
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user input
-- ✅ ALWAYS treat this as collaborative completion between technical peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on finalizing a lean, LLM-optimized project context
-- 🎯 ENSURE all critical rules are captured and actionable
-- ⚠️ 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}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 📝 Review and optimize content for LLM context efficiency
-- 📖 Update frontmatter with completion status
-- 🚫 NO MORE STEPS - this is the final step
-
-## CONTEXT BOUNDARIES:
-
-- All rule categories from step-2 are complete
-- Technology stack and versions are documented
-- Focus on final review, optimization, and completion
-- Ensure the context file is ready for AI agent consumption
-
-## YOUR TASK:
-
-Complete the project context file, optimize it for LLM efficiency, and provide guidance for usage and maintenance.
-
-## COMPLETION SEQUENCE:
-
-### 1. Review Complete Context File
-
-Read the entire project context file and analyze:
-
-**Content Analysis:**
-
-- Total length and readability for LLMs
-- Clarity and specificity of rules
-- Coverage of all critical areas
-- Actionability of each rule
-
-**Structure Analysis:**
-
-- Logical organization of sections
-- Consistency of formatting
-- Absence of redundant or obvious information
-- Optimization for quick scanning
-
-### 2. Optimize for LLM Context
-
-Ensure the file is lean and efficient:
-
-**Content Optimization:**
-
-- Remove any redundant rules or obvious information
-- Combine related rules into concise bullet points
-- Use specific, actionable language
-- Ensure each rule provides unique value
-
-**Formatting Optimization:**
-
-- Use consistent markdown formatting
-- Implement clear section hierarchy
-- Ensure scannability with strategic use of bolding
-- Maintain readability while maximizing information density
-
-### 3. Final Content Structure
-
-Ensure the final structure follows this optimized format:
-
-```markdown
-# Project Context for AI Agents
-
-_This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._
-
----
-
-## Technology Stack & Versions
-
-{{concise_technology_list}}
-
-## Critical Implementation Rules
-
-### Language-Specific Rules
-
-{{specific_language_rules}}
-
-### Framework-Specific Rules
-
-{{framework_patterns}}
-
-### Testing Rules
-
-{{testing_requirements}}
-
-### Code Quality & Style Rules
-
-{{style_and_quality_patterns}}
-
-### Development Workflow Rules
-
-{{workflow_patterns}}
-
-### Critical Don't-Miss Rules
-
-{{anti_patterns_and_edge_cases}}
-
----
-
-## Usage Guidelines
-
-**For AI Agents:**
-
-- Read this file before implementing any code
-- Follow ALL rules exactly as documented
-- When in doubt, prefer the more restrictive option
-- Update this file if new patterns emerge
-
-**For Humans:**
-
-- Keep this file lean and focused on agent needs
-- Update when technology stack changes
-- Review quarterly for outdated rules
-- Remove rules that become obvious over time
-
-Last Updated: {{date}}
-```
-
-### 4. Present Completion Summary
-
-Based on user skill level, present the completion:
-
-**Expert Mode:**
-"Project context complete. Optimized for LLM consumption with {{rule_count}} critical rules across {{section_count}} sections.
-
-File saved to: `{output_folder}/project-context.md`
-
-Ready for AI agent integration."
-
-**Intermediate Mode:**
-"Your project context is complete and optimized for AI agents!
-
-**What we created:**
-
-- {{rule_count}} critical implementation rules
-- Technology stack with exact versions
-- Framework-specific patterns and conventions
-- Testing and quality guidelines
-- Workflow and anti-pattern rules
-
-**Key benefits:**
-
-- AI agents will implement consistently with your standards
-- Reduced context switching and implementation errors
-- Clear guidance for unobvious project requirements
-
-**Next steps:**
-
-- AI agents should read this file before implementing
-- Update as your project evolves
-- Review periodically for optimization"
-
-**Beginner Mode:**
-"Excellent! Your project context guide is ready! 🎉
-
-**What this does:**
-Think of this as a 'rules of the road' guide for AI agents working on your project. It ensures they all follow the same patterns and avoid common mistakes.
-
-**What's included:**
-
-- Exact technology versions to use
-- Critical coding rules they might miss
-- Testing and quality standards
-- Workflow patterns to follow
-
-**How AI agents use it:**
-They read this file before writing any code, ensuring everything they create follows your project's standards perfectly.
-
-Your project context is saved and ready to help agents implement consistently!"
-
-### 5. Final File Updates
-
-Update the project context file with completion information:
-
-**Frontmatter Update:**
-
-```yaml
----
-project_name: '{{project_name}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
-sections_completed:
-  ['technology_stack', 'language_rules', 'framework_rules', 'testing_rules', 'quality_rules', 'workflow_rules', 'anti_patterns']
-status: 'complete'
-rule_count: { { total_rules } }
-optimized_for_llm: true
----
-```
-
-**Add Usage Section:**
-Append the usage guidelines from step 3 to complete the document.
-
-### 6. Completion Validation
-
-Final checks before completion:
-
-**Content Validation:**
-✅ All critical technology versions documented
-✅ Language-specific rules are specific and actionable
-✅ Framework rules cover project conventions
-✅ Testing rules ensure consistency
-✅ Code quality rules maintain standards
-✅ Workflow rules prevent conflicts
-✅ Anti-pattern rules prevent common mistakes
-
-**Format Validation:**
-✅ Content is lean and optimized for LLMs
-✅ Structure is logical and scannable
-✅ No redundant or obvious information
-✅ Consistent formatting throughout
-
-### 7. Completion Message
-
-Present final completion to user:
-
-"✅ **Project Context Generation Complete!**
-
-Your optimized project context file is ready at:
-`{output_folder}/project-context.md`
-
-**📊 Context Summary:**
-
-- {{rule_count}} critical rules for AI agents
-- {{section_count}} comprehensive sections
-- Optimized for LLM context efficiency
-- Ready for immediate agent integration
-
-**🎯 Key Benefits:**
-
-- Consistent implementation across all AI agents
-- Reduced common mistakes and edge cases
-- Clear guidance for project-specific patterns
-- Minimal LLM context usage
-
-**📋 Next Steps:**
-
-1. AI agents will automatically read this file when implementing
-2. Update this file when your technology stack or patterns evolve
-3. Review quarterly to optimize and remove outdated rules
-
-Your project context will help ensure high-quality, consistent implementation across all development work. Great work capturing your project's critical implementation requirements!"
-
-## SUCCESS METRICS:
-
-✅ Complete project context file with all critical rules
-✅ Content optimized for LLM context efficiency
-✅ All technology versions and patterns documented
-✅ File structure is logical and scannable
-✅ Usage guidelines included for agents and humans
-✅ Frontmatter properly updated with completion status
-✅ User provided with clear next steps and benefits
-
-## FAILURE MODES:
-
-❌ Final content is too verbose for LLM consumption
-❌ Missing critical implementation rules or patterns
-❌ Not optimizing content for agent readability
-❌ Not providing clear usage guidelines
-❌ Frontmatter not properly updated
-❌ Not validating file completion before ending
-
-## WORKFLOW COMPLETE:
-
-This is the final step of the Generate Project Context workflow. The user now has a comprehensive, optimized project context file that will ensure consistent, high-quality implementation across all AI agents working on the project.
-
-The project context file serves as the critical "rules of the road" that agents need to implement code consistently with the project's standards and patterns.

src/bmm/workflows/generate-project-context/workflow.md

@@ -1,49 +0,0 @@
----
-name: generate-project-context
-description: Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.
----
-
-# 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.
-
-**Your Role:** You are a technical facilitator working with a peer to capture the essential implementation rules that will ensure consistent, high-quality code generation across all AI agents working on the project.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **micro-file architecture** for disciplined execution:
-
-- Each step is a self-contained file with embedded rules
-- Sequential progression with user control at each step
-- Document state tracked in frontmatter
-- Focus on lean, LLM-optimized content generation
-- You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation.
-
----
-
-## INITIALIZATION
-
-### Configuration Loading
-
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
-
-- `project_name`, `output_folder`, `user_name`
-- `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}`
-
-### 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 `steps/step-01-discover.md` to begin the workflow.
-
-**Note:** Input document discovery and initialization protocols are handled in step-01-discover.md.

src/core/workflows/brainstorming/steps/step-01-session-setup.md

@@ -72,8 +72,7 @@ cp "{template_path}" "{output_folder}/brainstorming/brainstorming-session-{{date
 
 #### C. Session Context Gathering
 
-<output-block>
-Welcome {{user_name}}! I'm excited to facilitate your brainstorming session. I'll guide you through proven creativity techniques to generate innovative ideas and breakthrough solutions.
+"Welcome {{user_name}}! I'm excited to facilitate your brainstorming session. I'll guide you through proven creativity techniques to generate innovative ideas and breakthrough solutions.
 
 **Context Loading:** [If context_file provided, indicate context is loaded]
 **Context-Based Guidance:** [If context available, briefly mention focus areas]
@@ -83,25 +82,21 @@ Welcome {{user_name}}! I'm excited to facilitate your brainstorming session. I'l
 **Session Discovery Questions:**
 
 1. **What are we brainstorming about?** (The central topic or challenge)
-2. **What specific outcomes are you hoping for?** (Types of ideas, solutions, or insights)
-</output-block>
+2. **What specific outcomes are you hoping for?** (Types of ideas, solutions, or insights)"
 
 #### D. Process User Responses
 
 Wait for user responses, then:
 
 **Session Analysis:**
-
-<output-block>
-Based on your responses, I understand we're focusing on **[summarized topic]** with goals around **[summarized objectives]**.
+"Based on your responses, I understand we're focusing on **[summarized topic]** with goals around **[summarized objectives]**.
 
 **Session Parameters:**
 
 - **Topic Focus:** [Clear topic articulation]
 - **Primary Goals:** [Specific outcome objectives]
 
-**Does this accurately capture what you want to achieve?**
-</output-block>
+**Does this accurately capture what you want to achieve?**"
 
 #### E. Update Frontmatter and Document
 
@@ -143,8 +138,7 @@ When user selects approach, append the session overview content directly to `{ou
 
 ### E. Continue to Technique Selection
 
-<output-block>
-**Session setup complete!** I have a clear understanding of your goals and can select the perfect techniques for your brainstorming needs.
+"**Session setup complete!** I have a clear understanding of your goals and can select the perfect techniques for your brainstorming needs.
 
 **Ready to explore technique approaches?**
 [1] User-Selected Techniques - Browse our complete technique library
@@ -152,8 +146,7 @@ When user selects approach, append the session overview content directly to `{ou
 [3] Random Technique Selection - Discover unexpected creative methods
 [4] Progressive Technique Flow - Start broad, then systematically narrow focus
 
-Which approach appeals to you most? (Enter 1-4)
-</output-block>
+Which approach appeals to you most? (Enter 1-4)"
 
 ### 4. Handle User Selection and Initial Document Append
 

src/core/workflows/brainstorming/steps/step-01b-continue.md

@@ -41,9 +41,7 @@ Load existing document and analyze current state:
 - Identify current stage and next logical steps
 
 **Session Status Assessment:**
-
-<output-block>
-Welcome back {{user_name}}! I can see your brainstorming session on **[session_topic]** from **[date]**.
+"Welcome back {{user_name}}! I can see your brainstorming session on **[session_topic]** from **[date]**.
 
 **Current Session Status:**
 
@@ -53,35 +51,28 @@ Welcome back {{user_name}}! I can see your brainstorming session on **[session_t
 - **Current Stage:** [Assess where they left off]
 
 **Session Progress:**
-[Brief summary of what was accomplished and what remains]
-</output-block>
+[Brief summary of what was accomplished and what remains]"
 
 ### 2. Present Continuation Options
 
 Based on session analysis, provide appropriate options:
 
 **If Session Completed:**
-
-<output-block>
-Your brainstorming session appears to be complete!
+"Your brainstorming session appears to be complete!
 
 **Options:**
 [1] Review Results - Go through your documented ideas and insights
 [2] Start New Session - Begin brainstorming on a new topic
-[3) Extend Session - Add more techniques or explore new angles
-</output-block>
+[3) Extend Session - Add more techniques or explore new angles"
 
 **If Session In Progress:**
-
-<output-block>
-Let's continue where we left off!
+"Let's continue where we left off!
 
 **Current Progress:**
 [Description of current stage and accomplishments]
 
 **Next Steps:**
-[Continue with appropriate next step based on workflow state]
-</output-block>
+[Continue with appropriate next step based on workflow state]"
 
 ### 3. Handle User Choice
 

src/core/workflows/brainstorming/steps/step-02a-user-selected.md

@@ -34,11 +34,9 @@ Load and present brainstorming techniques from CSV, allowing user to browse and
 
 Load techniques from CSV on-demand:
 
-<output-block>
-Perfect! Let's explore our complete brainstorming techniques library. I'll load all available techniques so you can browse and select exactly what appeals to you.
+"Perfect! Let's explore our complete brainstorming techniques library. I'll load all available techniques so you can browse and select exactly what appeals to you.
 
-**Loading Brain Techniques Library...**
-</output-block>
+**Loading Brain Techniques Library...**"
 
 **Load CSV and parse:**
 
@@ -50,8 +48,7 @@ Perfect! Let's explore our complete brainstorming techniques library. I'll load
 
 Show available categories with brief descriptions:
 
-<output-block>
-**Our Brainstorming Technique Library - 36+ Techniques Across 7 Categories:**
+"**Our Brainstorming Technique Library - 36+ Techniques Across 7 Categories:**
 
 **[1] Structured Thinking** (6 techniques)
 
@@ -88,8 +85,7 @@ Show available categories with brief descriptions:
 - Inner wisdom and authentic exploration approaches
 - Includes: Inner Child Conference, Shadow Work Mining, Values Archaeology
 
-**Which category interests you most? Enter 1-7, or tell me what type of thinking you're drawn to.**
-</output-block>
+**Which category interests you most? Enter 1-7, or tell me what type of thinking you're drawn to.**"
 
 ### 3. Handle Category Selection
 
@@ -97,11 +93,9 @@ After user selects category:
 
 #### Load Category Techniques:
 
-<output-block>
-**[Selected Category] Techniques:**
+"**[Selected Category] Techniques:**
 
-**Loading specific techniques from this category...**
-</output-block>
+**Loading specific techniques from this category...**"
 
 **Present 3-5 techniques from selected category:**
 For each technique:
@@ -112,9 +106,7 @@ For each technique:
 - Example prompt: [Sample facilitation prompt]
 
 **Example presentation format:**
-
-<output-block>
-**1. SCAMPER Method** (Duration: 20-30 min, Energy: Moderate)
+"**1. SCAMPER Method** (Duration: 20-30 min, Energy: Moderate)
 
 - Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse)
 - Best for: Product improvement, innovation challenges, systematic idea generation
@@ -125,12 +117,10 @@ For each technique:
 - Explore problems through six distinct perspectives for comprehensive analysis
 - Best for: Complex decisions, team alignment, thorough exploration
 - Example prompt: "White hat thinking: What facts do we know for certain about this challenge?"
-</output-block>
 
 ### 4. Allow Technique Selection
 
-<output-block>
-**Which techniques from this category appeal to you?**
+"**Which techniques from this category appeal to you?**
 
 You can:
 
@@ -145,16 +135,13 @@ You can:
 - [Details] for more information about any technique
 - [Categories] to return to category list
 - [Back] to return to approach selection
-</output-block>
 
 ### 5. Handle Technique Confirmation
 
 When user selects techniques:
 
 **Confirmation Process:**
-
-<output-block>
-**Your Selected Techniques:**
+"**Your Selected Techniques:**
 
 - [Technique 1]: [Why this matches their session goals]
 - [Technique 2]: [Why this complements the first]
@@ -165,8 +152,7 @@ This combination will take approximately [total_time] and focus on [expected out
 
 **Confirm these choices?**
 [C] Continue - Begin technique execution
-[Back] - Modify technique selection
-</output-block>
+[Back] - Modify technique selection"
 
 ### 6. Update Frontmatter and Continue
 

src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md

@@ -34,8 +34,7 @@ Analyze session context and recommend optimal brainstorming techniques based on
 
 Load techniques from CSV for analysis:
 
-<output-block>
-Great choice! Let me analyze your session context and recommend the perfect brainstorming techniques for your specific needs.
+"Great choice! Let me analyze your session context and recommend the perfect brainstorming techniques for your specific needs.
 
 **Analyzing Your Session Goals:**
 
@@ -44,8 +43,7 @@ Great choice! Let me analyze your session context and recommend the perfect brai
 - Constraints: [constraints]
 - Session Type: [session_type]
 
-**Loading Brain Techniques Library for AI Analysis...**
-</output-block>
+**Loading Brain Techniques Library for AI Analysis...**"
 
 **Load CSV and parse:**
 
@@ -88,8 +86,7 @@ Analyze user's session context across multiple dimensions:
 
 Based on context analysis, create tailored recommendations:
 
-<output-block>
-**My AI Analysis Results:**
+"**My AI Analysis Results:**
 
 Based on your session context, I recommend this customized technique sequence:
 
@@ -112,8 +109,7 @@ Based on your session context, I recommend this customized technique sequence:
 - **Expected outcome:** [How this leads to actionable results]
 
 **Total Estimated Time:** [Sum of durations]
-**Session Focus:** [Primary benefit and outcome description]
-</output-block>
+**Session Focus:** [Primary benefit and outcome description]"
 
 ### 4. Present Recommendation Details
 
@@ -121,8 +117,7 @@ Provide deeper insight into each recommended technique:
 
 **Detailed Technique Explanations:**
 
-<output-block>
-For each recommended technique, here's what makes it perfect for your session:
+"For each recommended technique, here's what makes it perfect for your session:
 
 **1. [Technique 1]:**
 
@@ -143,13 +138,11 @@ For each recommended technique, here's what makes it perfect for your session:
 - **Description:** [Detailed explanation]
 - **Best for:** [Why this completes the sequence effectively]
 - **Sample facilitation:** [Example of how we'll use this]
-- **Your role:** [What you'll do during this technique]
-</output-block>
+- **Your role:** [What you'll do during this technique]"
 
 ### 5. Get User Confirmation
 
-<output-block>
-This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
+"This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
 
 **Does this approach sound perfect for your session?**
 
@@ -158,7 +151,6 @@ This AI-recommended sequence is designed specifically for your [session_topic] g
 [Modify] - I'd like to adjust the technique selection
 [Details] - Tell me more about any specific technique
 [Back] - Return to approach selection
-</output-block>
 
 ### 6. Handle User Response
 

src/core/workflows/brainstorming/steps/step-02c-random-selection.md

@@ -34,8 +34,7 @@ Use random selection to discover unexpected brainstorming techniques that will b
 
 Create anticipation for serendipitous technique discovery:
 
-<output-block>
-Exciting choice! You've chosen the path of creative serendipity. Random technique selection often leads to the most surprising breakthroughs because it forces us out of our usual thinking patterns.
+"Exciting choice! You've chosen the path of creative serendipity. Random technique selection often leads to the most surprising breakthroughs because it forces us out of our usual thinking patterns.
 
 **The Magic of Random Selection:**
 
@@ -44,8 +43,7 @@ Exciting choice! You've chosen the path of creative serendipity. Random techniqu
 - Find unexpected connections between different creativity methods
 - Experience the joy of genuine creative surprise
 
-**Loading our complete Brain Techniques Library for Random Discovery...**
-</output-block>
+**Loading our complete Brain Techniques Library for Random Discovery...**"
 
 **Load CSV and parse:**
 
@@ -58,12 +56,9 @@ Exciting choice! You've chosen the path of creative serendipity. Random techniqu
 Perform random selection with basic intelligence for good combinations:
 
 **Selection Process:**
+"I'm now randomly selecting 3 complementary techniques from our library of 36+ methods. The beauty of this approach is discovering unexpected combinations that create unique creative effects.
 
-<output-block>
-I'm now randomly selecting 3 complementary techniques from our library of 36+ methods. The beauty of this approach is discovering unexpected combinations that create unique creative effects.
-
-**Randomizing Technique Selection...**
-</output-block>
+**Randomizing Technique Selection...**"
 
 **Selection Logic:**
 
@@ -76,8 +71,7 @@ I'm now randomly selecting 3 complementary techniques from our library of 36+ me
 
 Reveal the randomly selected techniques with enthusiasm:
 
-<output-block>
-**🎲 Your Randomly Selected Creative Techniques! 🎲**
+"**🎲 Your Randomly Selected Creative Techniques! 🎲**
 
 **Phase 1: Exploration**
 **[Random Technique 1]** from [Category] (Duration: [time], Energy: [level])
@@ -101,15 +95,13 @@ Reveal the randomly selected techniques with enthusiasm:
 - **Random discovery bonus:** [Unexpected insight about the overall flow]
 
 **Total Random Session Time:** [Combined duration]
-**Serendipity Factor:** [Enthusiastic description of creative potential]
-</output-block>
+**Serendipity Factor:** [Enthusiastic description of creative potential]"
 
 ### 4. Highlight the Creative Potential
 
 Emphasize the unique value of this random combination:
 
-<output-block>
-**Why This Random Combination is Perfect:**
+"**Why This Random Combination is Perfect:**
 
 **Unexpected Synergy:**
 These three techniques might seem unrelated, but that's exactly where the magic happens! [Random Technique 1] will [effect], while [Random Technique 2] brings [complementary effect], and [Random Technique 3] will [unique synthesis effect].
@@ -131,7 +123,6 @@ You're about to experience brainstorming in a completely new way. These unexpect
 [Shuffle] - Randomize another combination for different adventure
 [Details] - Tell me more about any specific technique
 [Back] - Return to approach selection
-</output-block>
 
 ### 5. Handle User Response
 

src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md

@@ -34,8 +34,7 @@ Design a progressive technique flow that takes users from expansive exploration
 
 Explain the value of systematic creative progression:
 
-<output-block>
-Excellent choice! Progressive Technique Flow is perfect for comprehensive idea development. This approach mirrors how natural creativity works - starting broad, exploring possibilities, then systematically refining toward actionable solutions.
+"Excellent choice! Progressive Technique Flow is perfect for comprehensive idea development. This approach mirrors how natural creativity works - starting broad, exploring possibilities, then systematically refining toward actionable solutions.
 
 **The Creative Journey We'll Take:**
 
@@ -63,8 +62,7 @@ Excellent choice! Progressive Technique Flow is perfect for comprehensive idea d
 - Identify resources, timelines, and success metrics
 - Transform ideas into actionable plans
 
-**Loading Brain Techniques Library for Journey Design...**
-</output-block>
+**Loading Brain Techniques Library for Journey Design...**"
 
 **Load CSV and parse:**
 
@@ -78,8 +76,7 @@ Select optimal techniques for each progressive phase:
 
 **Phase 1: Expansive Exploration Techniques**
 
-<output-block>
-For **Expansive Exploration**, I'm selecting techniques that maximize creative breadth and wild thinking:
+"For **Expansive Exploration**, I'm selecting techniques that maximize creative breadth and wild thinking:
 
 **Recommended Technique: [Exploration Technique]**
 
@@ -88,13 +85,11 @@ For **Expansive Exploration**, I'm selecting techniques that maximize creative b
 - **Expected Outcome:** [Number]+ raw ideas across diverse categories
 - **Creative Energy:** High energy, expansive thinking
 
-**Alternative if time-constrained:** [Simpler exploration technique]
-</output-block>
+**Alternative if time-constrained:** [Simpler exploration technique]"
 
 **Phase 2: Pattern Recognition Techniques**
 
-<output-block>
-For **Pattern Recognition**, we need techniques that help organize and find meaning in the creative abundance:
+"For **Pattern Recognition**, we need techniques that help organize and find meaning in the creative abundance:
 
 **Recommended Technique: [Analysis Technique]**
 
@@ -103,41 +98,35 @@ For **Pattern Recognition**, we need techniques that help organize and find mean
 - **Expected Outcome:** Clear patterns and priority insights
 - **Analytical Focus:** Organized thinking and pattern discovery
 
-**Alternative for different session type:** [Alternative analysis technique]
-</output-block>
+**Alternative for different session type:** [Alternative analysis technique]"
 
 **Phase 3: Idea Development Techniques**
 
-<output-block>
-For **Idea Development**, we select techniques that refine and elaborate promising concepts:
+"For **Idea Development**, we select techniques that refine and elaborate promising concepts:
 
 **Recommended Technique: [Development Technique]**
 
 - **Category:** Structured/Collaborative techniques
 - **Why for Phase 3:** Perfect for building depth and detail around strong concepts
 - **Expected Outcome:** Well-developed solutions with implementation considerations
-- **Refinement Focus:** Practical enhancement and feasibility exploration
-</output-block>
+- **Refinement Focus:** Practical enhancement and feasibility exploration"
 
 **Phase 4: Action Planning Techniques**
 
-<output-block>
-For **Action Planning**, we choose techniques that create concrete implementation pathways:
+"For **Action Planning**, we choose techniques that create concrete implementation pathways:
 
 **Recommended Technique: [Planning Technique]**
 
 - **Category:** Structured/Analytical techniques
 - **Why for Phase 4:** Ideal for transforming ideas into actionable steps
 - **Expected Outcome:** Clear implementation plan with timelines and resources
-- **Implementation Focus:** Practical next steps and success metrics
-</output-block>
+- **Implementation Focus:** Practical next steps and success metrics"
 
 ### 3. Present Complete Journey Map
 
 Show the full progressive flow with timing and transitions:
 
-<output-block>
-**Your Complete Creative Journey Map:**
+"**Your Complete Creative Journey Map:**
 
 **⏰ Total Journey Time:** [Combined duration]
 **🎯 Session Focus:** Systematic development from ideas to action
@@ -186,14 +175,12 @@ Show the full progressive flow with timing and transitions:
 [Customize] - I'd like to modify any phase techniques
 [Details] - Tell me more about any specific phase or technique
 [Back] - Return to approach selection
-</output-block>
 
 ### 4. Handle Customization Requests
 
 If user wants customization:
 
-<output-block>
-**Customization Options:**
+"**Customization Options:**
 
 **Phase Modifications:**
 
@@ -208,8 +195,7 @@ If user wants customization:
 - **Extended Journey:** Add bonus technique at any phase for deeper exploration
 - **Focused Journey:** Emphasize specific phases based on your goals
 
-**Which customization would you like to make?**
-</output-block>
+**Which customization would you like to make?**"
 
 ### 5. Update Frontmatter and Document
 

src/core/workflows/brainstorming/steps/step-03-technique-execution.md

@@ -51,8 +51,7 @@ Facilitate brainstorming techniques through genuine interactive coaching, respon
 
 Set up collaborative facilitation approach:
 
-<output-block>
-**Outstanding! Let's begin our first technique with true collaborative facilitation.**
+"**Outstanding! Let's begin our first technique with true collaborative facilitation.**
 
 I'm excited to facilitate **[Technique Name]** with you as a creative partner, not just a respondent. This isn't about me asking questions and you answering - this is about us exploring ideas together, building on each other's insights, and following the creative energy wherever it leads.
 
@@ -69,8 +68,7 @@ I'm excited to facilitate **[Technique Name]** with you as a creative partner, n
 **Focus:** [Primary goal of this technique]
 **Energy:** [High/Reflective/Playful/etc.] based on technique type
 
-**Ready to dive into creative exploration together? Let's start with our first element!**
-</output-block>
+**Ready to dive into creative exploration together? Let's start with our first element!**"
 
 ### 2. Execute First Technique Element Interactively
 
@@ -78,11 +76,9 @@ Begin with genuine facilitation of the first technique component:
 
 **For Creative Techniques (What If, Analogical, etc.):**
 
-<output-block>
-**Let's start with: [First provocative question/concept]**
+"**Let's start with: [First provocative question/concept]**
 
-I'm not just looking for a quick answer - I want to explore this together. What immediately comes to mind? Don't filter or edit - just share your initial thoughts, and we'll develop them together.
-</output-block>
+I'm not just looking for a quick answer - I want to explore this together. What immediately comes to mind? Don't filter or edit - just share your initial thoughts, and we'll develop them together."
 
 **Wait for user response, then coach deeper:**
 
@@ -92,11 +88,9 @@ I'm not just looking for a quick answer - I want to explore this together. What
 
 **For Structured Techniques (SCAMPER, Six Thinking Hats, etc.):**
 
-<output-block>
-**Let's explore [Specific letter/perspective]: [Prompt]**
+"**Let's explore [Specific letter/perspective]: [Prompt]**
 
-Instead of just listing possibilities, let's really dive into one promising direction. What's the most exciting or surprising thought you have about this?
-</output-block>
+Instead of just listing possibilities, let's really dive into one promising direction. What's the most exciting or surprising thought you have about this?"
 
 **Coach the exploration:**
 
@@ -112,9 +106,7 @@ Follow the user's creative energy with genuine coaching:
 **Responsive Facilitation Patterns:**
 
 **When user shares exciting idea:**
-
-<output-block>
-That's brilliant! I can feel the creative energy there. Let's explore this more deeply:
+"That's brilliant! I can feel the creative energy there. Let's explore this more deeply:
 
 **Development Questions:**
 
@@ -123,21 +115,17 @@ That's brilliant! I can feel the creative energy there. Let's explore this more
 - What are the most innovative aspects of this approach?
 - Could this be applied in unexpected ways?
 
-**Let me build on your idea:** [Extend concept with your own creative contribution]
-</output-block>
+**Let me build on your idea:** [Extend concept with your own creative contribution]"
 
 **When user seems uncertain:**
-
-<output-block>
-Great starting point! Sometimes the most powerful ideas need space to develop. Let's try this angle:
+"Great starting point! Sometimes the most powerful ideas need space to develop. Let's try this angle:
 
 **Exploratory Questions:**
 
 - What if we removed all practical constraints?
 - How would [stakeholder] respond to this idea?
 - What's the most unexpected version of this concept?
-- Could we combine this with something completely different?
-</output-block>
+- Could we combine this with something completely different?"
 
 **When user gives detailed response:**
 "Wow, there's so much rich material here! I want to make sure we capture the full potential. Let me focus on what I'm hearing:
@@ -152,8 +140,7 @@ Before moving to next technique element:
 
 **Check Engagement and Interest:**
 
-<output-block>
-This has been incredibly productive! We've generated some fantastic ideas around [current element].
+"This has been incredibly productive! We've generated some fantastic ideas around [current element].
 
 **Before we move to the next technique element, I want to check in with you:**
 
@@ -170,8 +157,7 @@ This has been incredibly productive! We've generated some fantastic ideas around
 - **Take a different angle** on current element
 - **Jump to most exciting idea** we've discovered so far
 
-**Remember:** At any time, just say **"next technique"** or **"move on"** and I'll immediately document our current progress and start the next technique!
-</output-block>
+**Remember:** At any time, just say **"next technique"** or **"move on"** and I'll immediately document our current progress and start the next technique!"
 
 ### 4.1. Energy Checkpoint (After Every 4-5 Exchanges)
 
@@ -198,9 +184,7 @@ Remember: The goal is quantity first - we can organize later. What feels right?"
 **When user says "next technique" or "move on":**
 
 **Immediate Response:**
-
-<output-block>
-**Got it! Let's transition to the next technique.**
+"**Got it! Let's transition to the next technique.**
 
 **Documenting our progress with [Current Technique]:**
 
@@ -217,8 +201,7 @@ Remember: The goal is quantity first - we can organize later. What feels right?"
 
 This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on or contrasts with what we discovered about [key insight from current technique].
 
-**Let's begin fresh with this new approach!**
-</output-block>
+**Let's begin fresh with this new approach!**"
 
 **Then restart step 3 for the next technique:**
 
@@ -232,8 +215,7 @@ If multiple techniques selected:
 
 **Transition Between Techniques:**
 
-<output-block>
-**Fantastic work with [Previous Technique]!** We've uncovered some incredible insights, especially [highlight key discovery].
+"**Fantastic work with [Previous Technique]!** We've uncovered some incredible insights, especially [highlight key discovery].
 
 **Now let's transition to [Next Technique]:**
 
@@ -247,8 +229,7 @@ This technique will help us [what this technique adds]. I'm particularly excited
 
 **Ready to continue our creative journey with this new approach?**
 
-Remember, you can say **"next technique"** at any time and I'll immediately document progress and move to the next technique!
-</output-block>
+Remember, you can say **"next technique"** at any time and I'll immediately document progress and move to the next technique!"
 
 ### 6. Document Ideas Organically
 
@@ -264,8 +245,7 @@ This connects beautifully with what we discovered earlier about _[previous conne
 
 **After Deep Exploration:**
 
-<output-block>
-Let me summarize what we've uncovered in this exploration using our **IDEA FORMAT TEMPLATE**:
+"Let me summarize what we've uncovered in this exploration using our **IDEA FORMAT TEMPLATE**:
 
 **Key Ideas Generated:**
 
@@ -279,15 +259,13 @@ _Novelty_: [What makes this different from obvious solutions]
 
 **Energy and Engagement:** [Observation about user's creative flow]
 
-**Should I document these ideas before we continue, or keep the creative momentum going?**
-</output-block>
+**Should I document these ideas before we continue, or keep the creative momentum going?**"
 
 ### 7. Complete Technique with Integration
 
 After final technique element:
 
-<output-block>
-**Outstanding completion of [Technique Name]!**
+"**Outstanding completion of [Technique Name]!**
 
 **What We've Discovered Together:**
 
@@ -313,7 +291,6 @@ After final technique element:
 [C] **Move to organization** - Only when you feel we've thoroughly explored
 
 **Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
-</output-block>
 
 ### 8. Handle Menu Selection
 

src/core/workflows/brainstorming/steps/step-04-idea-organization.md

@@ -34,8 +34,7 @@ Organize all brainstorming ideas into coherent themes, facilitate prioritization
 
 Begin systematic review of all generated ideas:
 
-<output-block>
-**Outstanding creative work!** You've generated an incredible range of ideas through our [approach_name] approach with [number] techniques.
+"**Outstanding creative work!** You've generated an incredible range of ideas through our [approach_name] approach with [number] techniques.
 
 **Session Achievement Summary:**
 
@@ -45,17 +44,14 @@ Begin systematic review of all generated ideas:
 
 **Now let's organize these creative gems and identify your most promising opportunities for action.**
 
-**Loading all generated ideas for systematic organization...**
-</output-block>
+**Loading all generated ideas for systematic organization...**"
 
 ### 2. Theme Identification and Clustering
 
 Group related ideas into meaningful themes:
 
 **Theme Analysis Process:**
-
-<output-block>
-I'm analyzing all your generated ideas to identify natural themes and patterns. This will help us see the bigger picture and prioritize effectively.
+"I'm analyzing all your generated ideas to identify natural themes and patterns. This will help us see the bigger picture and prioritize effectively.
 
 **Emerging Themes I'm Identifying:**
 
@@ -81,8 +77,7 @@ _Focus: [Description of what this theme covers]_
 
 - **[Cross-cutting Ideas]:** [Ideas that span multiple themes]
 - **[Breakthrough Concepts]:** [Particularly innovative or surprising ideas]
-- **[Implementation-Ready Ideas]:** [Ideas that seem immediately actionable]
-</output-block>
+- **[Implementation-Ready Ideas]:** [Ideas that seem immediately actionable]"
 
 ### 3. Present Organized Idea Themes
 
@@ -90,8 +85,7 @@ Display systematically organized ideas for user review:
 
 **Organized by Theme:**
 
-<output-block>
-**Your Brainstorming Results - Organized by Theme:**
+"**Your Brainstorming Results - Organized by Theme:**
 
 **[Theme 1]: [Theme Description]**
 
@@ -114,8 +108,7 @@ Display systematically organized ideas for user review:
 - **[Innovative Idea]:** [Why this represents a significant breakthrough]
 - **[Unexpected Connection]:** [How this creates new possibilities]
 
-**Which themes or specific ideas stand out to you as most valuable?**
-</output-block>
+**Which themes or specific ideas stand out to you as most valuable?**"
 
 ### 4. Facilitate Prioritization
 
@@ -123,8 +116,7 @@ Guide user through strategic prioritization:
 
 **Prioritization Framework:**
 
-<output-block>
-Now let's identify your most promising ideas based on what matters most for your **[session_goals]**.
+"Now let's identify your most promising ideas based on what matters most for your **[session_goals]**.
 
 **Prioritization Criteria for Your Session:**
 
@@ -141,8 +133,7 @@ Review your organized ideas and identify:
 2. **Easiest Quick Wins:** Which ideas could be implemented fastest?
 3. **Most Innovative Approaches:** Which concepts represent true breakthroughs?
 
-**What stands out to you as most valuable? Share your top priorities and I'll help you develop action plans.**
-</output-block>
+**What stands out to you as most valuable? Share your top priorities and I'll help you develop action plans.**"
 
 ### 5. Develop Action Plans
 
@@ -150,8 +141,7 @@ Create concrete next steps for prioritized ideas:
 
 **Action Planning Process:**
 
-<output-block>
-**Excellent choices!** Let's develop actionable plans for your top priority ideas.
+"**Excellent choices!** Let's develop actionable plans for your top priority ideas.
 
 **For each selected idea, let's explore:**
 
@@ -172,8 +162,7 @@ Create concrete next steps for prioritized ideas:
 **Timeline:** [Implementation estimate]
 **Success Indicators:** [How to measure progress]
 
-**Would you like me to develop similar action plans for your other top ideas?**
-</output-block>
+**Would you like me to develop similar action plans for your other top ideas?**"
 
 ### 6. Create Comprehensive Session Documentation
 
@@ -181,8 +170,7 @@ Prepare final session output:
 
 **Session Documentation Structure:**
 
-<output-block>
-**Creating your comprehensive brainstorming session documentation...**
+"**Creating your comprehensive brainstorming session documentation...**
 
 This document will include:
 
@@ -192,8 +180,7 @@ This document will include:
 - **Action Plans:** Concrete next steps for implementation
 - **Session Insights:** Key learnings and creative breakthroughs
 
-**Your brainstorming session has produced [number] organized ideas across [number] themes, with [number] prioritized concepts ready for action planning.**
-</output-block>
+**Your brainstorming session has produced [number] organized ideas across [number] themes, with [number] prioritized concepts ready for action planning.**"
 
 **Append to document:**
 
@@ -230,8 +217,7 @@ Provide final session wrap-up and forward guidance:
 
 **Session Completion:**
 
-<output-block>
-**Congratulations on an incredibly productive brainstorming session!**
+"**Congratulations on an incredibly productive brainstorming session!**
 
 **Your Creative Achievements:**
 
@@ -262,7 +248,6 @@ Provide final session wrap-up and forward guidance:
 
 **Ready to complete your session documentation?**
 [C] Complete - Generate final brainstorming session document
-</output-block>
 
 ### 8. Handle Completion Selection
 

src/core/workflows/party-mode/steps/step-01-agent-loading.md

@@ -34,11 +34,9 @@ Load the complete agent roster from manifest and initialize party mode with enga
 
 Begin agent loading process:
 
-<output-block>
-Now initializing **Party Mode** with our complete BMAD agent roster! Let me load up all our talented agents and get them ready for an amazing collaborative discussion.
+"Now initializing **Party Mode** with our complete BMAD agent roster! Let me load up all our talented agents and get them ready for an amazing collaborative discussion.
 
-**Agent Manifest Loading:**
-</output-block>
+**Agent Manifest Loading:**"
 
 Load and parse the agent manifest CSV from `{project-root}/_bmad/_config/agent-manifest.csv`
 
@@ -74,8 +72,7 @@ Create complete agent roster with merged personalities:
 
 Generate enthusiastic party mode introduction:
 
-<output-block>
-🎉 PARTY MODE ACTIVATED! 🎉
+"🎉 PARTY MODE ACTIVATED! 🎉
 
 Welcome {{user_name}}! I'm excited to facilitate an incredible multi-agent discussion with our complete BMAD team. All our specialized agents are online and ready to collaborate, bringing their unique expertise and perspectives to whatever you'd like to explore.
 
@@ -89,19 +86,16 @@ Welcome {{user_name}}! I'm excited to facilitate an incredible multi-agent discu
 
 **[Total Count] agents** are ready to contribute their expertise!
 
-**What would you like to discuss with the team today?**
-</output-block>
+**What would you like to discuss with the team today?**"
 
 ### 5. Present Continue Option
 
 After agent loading and introduction:
 
-<output-block>
-**Agent roster loaded successfully!** All our BMAD experts are excited to collaborate with you.
+"**Agent roster loaded successfully!** All our BMAD experts are excited to collaborate with you.
 
 **Ready to start the discussion?**
 [C] Continue - Begin multi-agent conversation
-</output-block>
 
 ### 6. Handle Continue Selection
 

src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md

@@ -33,9 +33,7 @@ Orchestrate dynamic multi-agent conversations with intelligent agent selection,
 For each user message or topic:
 
 **Input Analysis Process:**
-<output-block>
-Analyzing your message for the perfect agent collaboration...
-</output-block>
+"Analyzing your message for the perfect agent collaboration..."
 
 **Analysis Criteria:**
 

src/core/workflows/party-mode/steps/step-03-graceful-exit.md

@@ -34,11 +34,9 @@ Provide satisfying agent farewells and conclude the party mode session with grat
 
 Begin exit process with warm acknowledgment:
 
-<output-block>
-What an incredible collaborative session! Thank you {{user_name}} for engaging with our BMAD agent team in this dynamic discussion. Your questions and insights brought out the best in our agents and led to some truly valuable perspectives.
+"What an incredible collaborative session! Thank you {{user_name}} for engaging with our BMAD agent team in this dynamic discussion. Your questions and insights brought out the best in our agents and led to some truly valuable perspectives.
 
-**Before we wrap up, let a few of our agents say goodbye...**
-</output-block>
+**Before we wrap up, let a few of our agents say goodbye...**"
 
 ### 2. Generate Agent Farewells
 
@@ -76,8 +74,7 @@ Briefly acknowledge key discussion outcomes:
 
 End with enthusiastic and appreciative closure:
 
-<output-block>
-🎊 **Party Mode Session Complete!** 🎊
+"🎊 **Party Mode Session Complete!** 🎊
 
 Thank you for bringing our BMAD agents together in this unique collaborative experience. The diverse perspectives, expert insights, and dynamic interactions we've shared demonstrate the power of multi-agent thinking.
 
@@ -85,8 +82,7 @@ Thank you for bringing our BMAD agents together in this unique collaborative exp
 
 **Ready for your next challenge**? Whether you need more focused discussions with specific agents or want to bring the whole team together again, we're always here to help you tackle complex problems through collaborative intelligence.
 
-**Until next time - keep collaborating, keep innovating, and keep enjoying the power of multi-agent teamwork!** 🚀
-</output-block>
+**Until next time - keep collaborating, keep innovating, and keep enjoying the power of multi-agent teamwork!** 🚀"
 
 ### 5. Complete Workflow Exit
 

src/core/workflows/party-mode/workflow.md

@@ -75,8 +75,7 @@ Execute party mode activation and conversation orchestration:
 
 **Welcome Activation:**
 
-<output-block>
-🎉 PARTY MODE ACTIVATED! 🎉
+"🎉 PARTY MODE ACTIVATED! 🎉
 
 Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities.
 
@@ -84,8 +83,7 @@ Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group di
 
 [Load agent roster and display 2-3 most diverse agents as examples]
 
-**What would you like to discuss with the team today?**
-</output-block>
+**What would you like to discuss with the team today?**"
 
 ### Agent Selection Intelligence
 

tools/cli/installers/lib/modules/manager.js

@@ -416,7 +416,7 @@ class ModuleManager {
       if (needsDependencyInstall || wasNewClone || nodeModulesMissing) {
         const installSpinner = ora(`Installing dependencies for ${moduleInfo.name}...`).start();
         try {
-          execSync('npm install --production --no-audit --no-fund --prefer-offline --no-progress --legacy-peer-deps', {
+          execSync('npm install --production --no-audit --no-fund --prefer-offline --no-progress', {
             cwd: moduleCacheDir,
             stdio: 'pipe',
             timeout: 120_000, // 2 minute timeout
@@ -441,7 +441,7 @@ class ModuleManager {
         if (packageJsonNewer) {
           const installSpinner = ora(`Installing dependencies for ${moduleInfo.name}...`).start();
           try {
-            execSync('npm install --production --no-audit --no-fund --prefer-offline --no-progress --legacy-peer-deps', {
+            execSync('npm install --production --no-audit --no-fund --prefer-offline --no-progress', {
               cwd: moduleCacheDir,
               stdio: 'pipe',
               timeout: 120_000, // 2 minute timeout

tools/cli/lib/activation-builder.js

@@ -121,10 +121,9 @@ class ActivationBuilder {
 
     // Calculate final step numbers
     const menuStep = currentStepNum;
-    const helpStep = currentStepNum + 1;
-    const haltStep = currentStepNum + 2;
-    const inputStep = currentStepNum + 3;
-    const executeStep = currentStepNum + 4;
+    const haltStep = currentStepNum + 1;
+    const inputStep = currentStepNum + 2;
+    const executeStep = currentStepNum + 3;
 
     // Replace placeholders
     const processed = stepsTemplate
@@ -132,7 +131,6 @@ class ActivationBuilder {
       .replace('{{module}}', metadata.module || 'core') // Fixed to use {{module}}
       .replace('{AGENT_SPECIFIC_STEPS}', agentStepsXml)
       .replace('{MENU_STEP}', menuStep.toString())
-      .replace('{HELP_STEP}', helpStep.toString())
       .replace('{HALT_STEP}', haltStep.toString())
       .replace('{INPUT_STEP}', inputStep.toString())
       .replace('{EXECUTE_STEP}', executeStep.toString());