fix: update masonry grid sizing logic and notebook list padding

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

@@ -141,7 +141,7 @@ Display: "**Proceeding to product vision discovery...**"
 
 #### Menu Handling Logic:
 
-- After setup report is presented, immediately load, read entire file, then execute {nextStepFile}
+- After setup report is presented, without delay, read fully and follow: {nextStepFile}
 
 #### EXECUTION RULES:
 
@@ -150,7 +150,7 @@ Display: "**Proceeding to product vision discovery...**"
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then load and read fully `{nextStepFile}` to execute and begin product vision discovery.
+ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then read fully and follow: `{nextStepFile}` to begin product vision discovery.
 
 ---
 

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

@@ -125,7 +125,7 @@ Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
 
 #### Menu Handling Logic:
 
-- IF C: Load, read entire file, then execute the appropriate next step file based on `lastStep`
+- IF C: Read fully and follow the appropriate next step file based on `lastStep`
 - IF Any other comments or queries: respond and redisplay menu
 
 #### EXECUTION RULES:
@@ -136,7 +136,7 @@ Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the appropriate next step file to resume the workflow.
+ONLY WHEN [C continue option] is selected and [current state confirmed], will you then read fully and follow the appropriate next step file to resume the workflow.
 
 ---
 

_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md

@@ -156,9 +156,9 @@ Prepare the following structure for document append:
 
 #### Menu Handling Logic:
 
-- IF A: Execute {advancedElicitationTask} with current vision content to dive deeper and refine
-- IF P: Execute {partyModeWorkflow} to bring different perspectives to positioning and differentiation
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then only then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with current vision content to dive deeper and refine
+- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to positioning and differentiation
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
 
 #### EXECUTION RULES:
@@ -170,7 +170,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin target user discovery.
+ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin target user discovery.
 
 ---
 

_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md

@@ -159,9 +159,9 @@ Prepare the following structure for document append:
 
 #### Menu Handling Logic:
 
-- IF A: Execute {advancedElicitationTask} with current user content to dive deeper into personas and journeys
-- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate user understanding
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then only then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with current user content to dive deeper into personas and journeys
+- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate user understanding
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
 
 #### EXECUTION RULES:
@@ -173,7 +173,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin success metrics definition.
+ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin success metrics definition.
 
 ---
 

_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md

@@ -162,9 +162,9 @@ Prepare the following structure for document append:
 
 #### Menu Handling Logic:
 
-- IF A: Execute {advancedElicitationTask} with current metrics content to dive deeper into success metric insights
-- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate comprehensive metrics
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then only then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with current metrics content to dive deeper into success metric insights
+- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate comprehensive metrics
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
 
 #### EXECUTION RULES:
@@ -176,7 +176,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin MVP scope definition.
+ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin MVP scope definition.
 
 ---
 

_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md

@@ -176,9 +176,9 @@ Prepare the following structure for document append:
 
 #### Menu Handling Logic:
 
-- IF A: Execute {advancedElicitationTask} with current scope content to optimize scope definition
-- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate MVP scope
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then only then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with current scope content to optimize scope definition
+- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate MVP scope
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
 
 #### EXECUTION RULES:
@@ -190,7 +190,7 @@ Prepare the following structure for document append:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and complete the product brief workflow.
+ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to complete the product brief workflow.
 
 ---
 

_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md

@@ -73,17 +73,7 @@ I've successfully collaborated with you to create a comprehensive Product Brief
 
 This brief serves as the foundation for all subsequent product development activities and strategic decisions."
 
-### 2. Workflow Status Update
-
-**Status File Management:**
-Update the main workflow status file:
-
-- Check if `{output_folder} or {planning_artifacts}/bmm-workflow-status.yaml` exists
-- If so, update workflow_status["product-brief"] = `{outputFile}`
-- Add completion timestamp and metadata
-- Save file, preserving all comments and structure
-
-### 3. Document Quality Check
+### 2. Document Quality Check
 
 **Completeness Validation:**
 Perform final validation of the product brief:
@@ -101,7 +91,7 @@ Perform final validation of the product brief:
 - Are success criteria traceable to user needs and business goals?
 - Does MVP scope align with the problem and solution?
 
-### 4. Suggest Next Steps
+### 3. Suggest Next Steps
 
 **Recommended Next Workflow:**
 Provide guidance on logical next workflows:
@@ -124,12 +114,11 @@ Provide guidance on logical next workflows:
 - Use brief to validate concept before committing to detailed work
 - Brief can guide early technical feasibility discussions
 
-### 5. Present MENU OPTIONS
+### 4. Congrats to the user
 
-**Completion Confirmation:**
-"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**
+"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**"
 
-The brief captures everything needed to guide subsequent product development:
+Recap that the brief captures everything needed to guide subsequent product development:
 
 - Clear vision and problem definition
 - Deep understanding of target users
@@ -137,30 +126,9 @@ The brief captures everything needed to guide subsequent product development:
 - Focused MVP scope with realistic boundaries
 - Inspiring long-term vision
 
-**Suggested Next Steps**
+### 5. Suggest next steps
 
-- PRD workflow for detailed requirements?
-- UX design workflow for user experience planning?
-
-**Product Brief Complete**"
-
-#### Menu Handling Logic:
-
-- Since this is a completion step, no continuation to other workflow steps
-- User can ask questions or request review of the completed brief
-- Provide guidance on next workflow options when requested
-- End workflow session gracefully after completion confirmation
-
-#### EXECUTION RULES:
-
-- This is a final step with completion focus
-- No additional workflow steps to load after this
-- User can request review or clarification of completed brief
-- Provide clear guidance on next workflow options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [completion confirmation is provided and workflow status updated], will you then mark the workflow as complete and end the session gracefully. No additional steps are loaded after this final completion step.
+Product Brief complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Validate PRD`.
 
 ---
 

_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md

@@ -1,7 +1,6 @@
 ---
 name: create-product-brief
 description: Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
-web_bundle: true
 ---
 
 # Product Brief Workflow
@@ -31,7 +30,7 @@ This uses **step-file architecture** for disciplined execution:
 3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
 4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
 5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
 
 ### Critical Rules (NO EXCEPTIONS)
 
@@ -55,4 +54,4 @@ Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
 
 ### 2. First Step EXECUTION
 
-Load, read the full file and then execute `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.
+Read fully and follow: `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.

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

@@ -138,7 +138,7 @@ Show initial scope document and present continue option:
 
 - Update frontmatter: `stepsCompleted: [1]`
 - Add confirmation note to document: "Scope confirmed by user on {{date}}"
-- Load: `./step-02-customer-insights.md`
+- Load: `./step-02-customer-behavior.md`
 
 #### If 'Modify':
 

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

@@ -1,200 +0,0 @@
-# Market Research Step 2: Customer Insights
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without web search verification
-
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ Search the web to verify and supplement your knowledge with current facts
-- 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator
-- 💬 FOCUS on customer behavior and needs analysis
-- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show web search analysis before presenting findings
-- ⚠️ Present [C] continue option after customer insights content generation
-- 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from step-01 are available
-- Focus on customer behavior and needs analysis
-- Web search capabilities with source verification are enabled
-- May need to search for current customer behavior trends
-
-## YOUR TASK:
-
-Conduct comprehensive customer insights analysis with emphasis on behavior patterns and needs.
-
-## CUSTOMER INSIGHTS SEQUENCE:
-
-### 1. Begin Customer Insights Analysis
-
-**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:
-"Now I'll conduct **customer insights analysis** to understand customer behavior and needs.
-
-**Customer Insights Focus:**
-
-- Customer behavior patterns and preferences
-- Pain points and challenges
-- Decision-making processes
-- Customer journey mapping
-- Customer satisfaction drivers
-- Demographic and psychographic profiles
-
-**Let me search for current customer insights using parallel web searches for comprehensive coverage.**"
-
-### 2. Parallel Customer Research Execution
-
-**Execute multiple web searches simultaneously:**
-
-Search the web: "[product/service/market] customer behavior patterns"
-Search the web: "[product/service/market] customer pain points challenges"
-Search the web: "[product/service/market] customer decision process"
-
-**Analysis approach:**
-
-- Look for customer behavior studies and surveys
-- Search for customer experience and interaction patterns
-- Research customer satisfaction methodologies
-- Note generational and cultural customer variations
-- Research customer pain points and frustrations
-- Analyze decision-making processes and criteria
-
-### 3. Analyze and Aggregate Results
-
-**Collect and analyze findings from all parallel searches:**
-
-"After executing comprehensive parallel web searches, let me analyze and aggregate the customer insights:
-
-**Research Coverage:**
-
-- Customer behavior patterns and preferences
-- Pain points and challenges
-- Decision-making processes and journey mapping
-
-**Cross-Customer Analysis:**
-[Identify patterns connecting behavior, pain points, and decisions]
-
-**Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
-
-### 4. Generate Customer Insights Content
-
-Prepare customer analysis with web search citations:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Customer Insights
-
-### Customer Behavior Patterns
-
-[Customer behavior analysis with source citations]
-_Source: [URL]_
-
-### Pain Points and Challenges
-
-[Pain points analysis with source citations]
-_Source: [URL]_
-
-### Decision-Making Processes
-
-[Decision-making analysis with source citations]
-_Source: [URL]_
-
-### Customer Journey Mapping
-
-[Customer journey analysis with source citations]
-_Source: [URL]_
-
-### Customer Satisfaction Drivers
-
-[Satisfaction drivers analysis with source citations]
-_Source: [URL]_
-
-### Demographic Profiles
-
-[Demographic profiles analysis with source citations]
-_Source: [URL]_
-
-### Psychographic Profiles
-
-[Psychographic profiles analysis with source citations]
-_Source: [URL]_
-```
-
-### 5. Present Analysis and Continue Option
-
-Show the generated customer insights and present continue option:
-"I've completed the **customer insights analysis** for customer behavior and needs.
-
-**Key Customer Findings:**
-
-- Customer behavior patterns clearly identified
-- Pain points and challenges thoroughly documented
-- Decision-making processes mapped
-- Customer journey insights captured
-- Satisfaction and profile data analyzed
-
-**Ready to proceed to competitive analysis?**
-[C] Continue - Save this to the document and proceed to competitive analysis
-
-### 6. Handle Continue Selection
-
-#### If 'C' (Continue):
-
-- Append the final content to the research document
-- Update frontmatter: `stepsCompleted: [1, 2]`
-- Load: `./step-05-competitive-analysis.md`
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C', append the content directly to the research document using the structure from step 4.
-
-## SUCCESS METRICS:
-
-✅ Customer behavior patterns identified with current citations
-✅ Pain points and challenges clearly documented
-✅ Decision-making processes thoroughly analyzed
-✅ Customer journey insights captured and mapped
-✅ Customer satisfaction drivers identified
-✅ [C] continue option presented and handled correctly
-✅ Content properly appended to document when C selected
-
-## FAILURE MODES:
-
-❌ Relying solely on training data without web verification for current facts
-
-❌ Missing critical customer behavior patterns
-❌ Not identifying key pain points and challenges
-❌ Incomplete customer journey mapping
-❌ Not presenting [C] continue option after content generation
-❌ Appending content without user selecting 'C'
-
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## CUSTOMER RESEARCH PROTOCOLS:
-
-- Search for customer behavior studies and surveys
-- Use market research firm and industry association sources
-- Research customer experience and interaction patterns
-- Note generational and cultural customer variations
-- Research customer satisfaction methodologies
-
-## NEXT STEP:
-
-After user selects 'C' and content is saved to document, load `./step-05-competitive-analysis.md` to focus on competitive landscape analysis.
-
-Remember: Always emphasize current customer data and rigorous source verification!

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

@@ -155,7 +155,7 @@ Show the generated architectural patterns and present continue option:
 #### If 'C' (Continue):
 
 - Append the final content to the research document
-- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
 - Load: `./step-05-implementation-research.md`
 
 ## APPEND TO DOCUMENT:

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

@@ -1,4 +1,4 @@
-# Technical Research Step 4: Implementation Research
+# Technical Research Step 5: Implementation Research
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -17,7 +17,7 @@
 - 🎯 Show web search analysis before presenting findings
 - ⚠️ Present [C] complete option after implementation research content generation
 - 💾 ONLY save when user chooses C (Complete)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before completing workflow
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
 - 🚫 FORBIDDEN to complete workflow until C is selected
 
 ## CONTEXT BOUNDARIES:
@@ -25,7 +25,7 @@
 - Current document and frontmatter from previous steps are available
 - Focus on implementation approaches and technology adoption strategies
 - Web search capabilities with source verification are enabled
-- This is the final step in the technical research workflow
+- This step prepares for the final synthesis step
 
 ## YOUR TASK:
 
@@ -149,10 +149,10 @@ _Source: [URL]_
 [Success measurement framework]
 ```
 
-### 6. Present Analysis and Complete Option
+### 6. Present Analysis and Continue Option
 
-Show the generated implementation research and present complete option:
-"I've completed the **implementation research and technology adoption** analysis, finalizing our comprehensive technical research.
+Show the generated implementation research and present continue option:
+"I've completed the **implementation research and technology adoption** analysis for {{research_topic}}.
 
 **Implementation Highlights:**
 
@@ -162,23 +162,24 @@ Show the generated implementation research and present complete option:
 - Team organization and skill requirements identified
 - Cost optimization and resource management strategies provided
 
-**This completes our technical research covering:**
+**Technical research phases completed:**
 
-- Technical overview and landscape analysis
-- Architectural patterns and design decisions
-- Implementation approaches and technology adoption
-- Practical recommendations and implementation roadmap
+- Step 1: Research scope confirmation
+- Step 2: Technology stack analysis
+- Step 3: Integration patterns analysis
+- Step 4: Architectural patterns analysis
+- Step 5: Implementation research (current step)
 
-**Ready to complete the technical research report?**
-[C] Complete Research - Save final document and conclude
+**Ready to proceed to the final synthesis step?**
+[C] Continue - Save this to document and proceed to synthesis
 
-### 7. Handle Complete Selection
+### 7. Handle Continue Selection
 
-#### If 'C' (Complete Research):
+#### If 'C' (Continue):
 
 - Append the final content to the research document
-- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
-- Complete the technical research workflow
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
+- Load: `./step-06-research-synthesis.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -191,9 +192,9 @@ When user selects 'C', append the content directly to the research document usin
 ✅ Testing and deployment practices clearly documented
 ✅ Team organization and skill requirements mapped
 ✅ Cost optimization and risk mitigation strategies provided
-✅ [C] complete option presented and handled correctly
+✅ [C] continue option presented and handled correctly
 ✅ Content properly appended to document when C selected
-✅ Technical research workflow completed successfully
+✅ Proper routing to synthesis step (step-06)
 
 ## FAILURE MODES:
 
@@ -202,8 +203,9 @@ When user selects 'C', append the content directly to the research document usin
 ❌ Missing critical technology adoption strategies
 ❌ Not providing practical implementation guidance
 ❌ Incomplete development workflows or operational practices analysis
-❌ Not presenting completion option for research workflow
+❌ Not presenting continue option to synthesis step
 ❌ Appending content without user selecting 'C'
+❌ Not routing to step-06-research-synthesis.md
 
 ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
 ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
@@ -221,19 +223,11 @@ When user selects 'C', append the content directly to the research document usin
 
 When 'C' is selected:
 
-- All technical research steps completed
-- Comprehensive technical research document generated
-- All sections appended with source citations
-- Technical research workflow status updated
-- Final implementation recommendations provided to user
+- Implementation research step completed
+- Content appended to research document with source citations
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5]
+- Ready to proceed to final synthesis step
 
-## NEXT STEPS:
+## NEXT STEP:
 
-Technical research workflow complete. User may:
-
-- Use technical research to inform architecture decisions
-- Conduct additional research on specific technologies
-- Combine technical research with other research types for comprehensive insights
-- Move forward with implementation based on technical insights
-
-Congratulations on completing comprehensive technical research! 🎉
+After user selects 'C', load `./step-06-research-synthesis.md` to produce the comprehensive technical research document with narrative introduction, detailed TOC, and executive summary.

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

@@ -1,4 +1,4 @@
-# Technical Research Step 5: Technical Synthesis and Completion
+# Technical Research Step 6: Technical Synthesis and Completion
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -18,7 +18,7 @@
 - 🎯 Show web search analysis before presenting findings
 - ⚠️ Present [C] complete option after synthesis content generation
 - 💾 ONLY save when user chooses C (Complete)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow
 - 🚫 FORBIDDEN to complete workflow until C is selected
 - 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
 
@@ -417,7 +417,7 @@ _This comprehensive technical research document serves as an authoritative techn
 #### If 'C' (Complete Research):
 
 - Append the complete technical document to the research file
-- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
 - Complete the technical research workflow
 - Provide final technical document delivery confirmation
 

_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md

@@ -0,0 +1,54 @@
+---
+name: domain-research
+description: Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.
+---
+
+# Domain Research Workflow
+
+**Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
+
+**Your Role:** You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
+
+## PREREQUISITE
+
+**⛔ Web search required.** If unavailable, abort and tell the user.
+
+## CONFIGURATION
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as a system-generated value
+
+## QUICK TOPIC DISCOVERY
+
+"Welcome {{user_name}}! Let's get started with your **domain/industry research**.
+
+**What domain, industry, or sector do you want to research?**
+
+For example:
+- 'The healthcare technology industry'
+- 'Sustainable packaging regulations in Europe'
+- 'Construction and building materials sector'
+- 'Or any other domain you have in mind...'"
+
+### Topic Clarification
+
+Based on the user's topic, briefly clarify:
+1. **Core Domain**: "What specific aspect of [domain] are you most interested in?"
+2. **Research Goals**: "What do you hope to achieve with this research?"
+3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
+
+## ROUTE TO DOMAIN RESEARCH STEPS
+
+After gathering the topic and goals:
+
+1. Set `research_type = "domain"`
+2. Set `research_topic = [discovered topic from discussion]`
+3. Set `research_goals = [discovered goals from discussion]`
+4. Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
+5. Load: `./domain-steps/step-01-init.md` with topic context
+
+**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for domain research.
+
+**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**

_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md

@@ -0,0 +1,54 @@
+---
+name: market-research
+description: Conduct market research covering market size, growth, competition, and customer insights using current web data and verified sources.
+---
+
+# Market Research Workflow
+
+**Goal:** Conduct comprehensive market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
+
+**Your Role:** You are a market research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
+
+## PREREQUISITE
+
+**⛔ Web search required.** If unavailable, abort and tell the user.
+
+## CONFIGURATION
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as a system-generated value
+
+## QUICK TOPIC DISCOVERY
+
+"Welcome {{user_name}}! Let's get started with your **market research**.
+
+**What topic, problem, or area do you want to research?**
+
+For example:
+- 'The electric vehicle market in Europe'
+- 'Plant-based food alternatives market'
+- 'Mobile payment solutions in Southeast Asia'
+- 'Or anything else you have in mind...'"
+
+### Topic Clarification
+
+Based on the user's topic, briefly clarify:
+1. **Core Topic**: "What exactly about [topic] are you most interested in?"
+2. **Research Goals**: "What do you hope to achieve with this research?"
+3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
+
+## ROUTE TO MARKET RESEARCH STEPS
+
+After gathering the topic and goals:
+
+1. Set `research_type = "market"`
+2. Set `research_topic = [discovered topic from discussion]`
+3. Set `research_goals = [discovered goals from discussion]`
+4. Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
+5. Load: `./market-steps/step-01-init.md` with topic context
+
+**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for market research.
+
+**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**

_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md

@@ -0,0 +1,54 @@
+---
+name: technical-research
+description: Conduct technical research covering technology evaluation, architecture decisions, and implementation approaches using current web data and verified sources.
+---
+
+# Technical Research Workflow
+
+**Goal:** Conduct comprehensive technical research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
+
+**Your Role:** You are a technical research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
+
+## PREREQUISITE
+
+**⛔ Web search required.** If unavailable, abort and tell the user.
+
+## CONFIGURATION
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as a system-generated value
+
+## QUICK TOPIC DISCOVERY
+
+"Welcome {{user_name}}! Let's get started with your **technical research**.
+
+**What technology, tool, or technical area do you want to research?**
+
+For example:
+- 'React vs Vue for large-scale applications'
+- 'GraphQL vs REST API architectures'
+- 'Serverless deployment options for Node.js'
+- 'Or any other technical topic you have in mind...'"
+
+### Topic Clarification
+
+Based on the user's topic, briefly clarify:
+1. **Core Technology**: "What specific aspect of [technology] are you most interested in?"
+2. **Research Goals**: "What do you hope to achieve with this research?"
+3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
+
+## ROUTE TO TECHNICAL RESEARCH STEPS
+
+After gathering the topic and goals:
+
+1. Set `research_type = "technical"`
+2. Set `research_topic = [discovered topic from discussion]`
+3. Set `research_goals = [discovered goals from discussion]`
+4. Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
+5. Load: `./technical-steps/step-01-init.md` with topic context
+
+**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for technical research.
+
+**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**

_bmad/bmm/workflows/1-analysis/research/workflow.md

@@ -1,173 +0,0 @@
----
-name: research
-description: Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.
-web_bundle: true
----
-
-# Research Workflow
-
-**Goal:** Conduct comprehensive, exhaustive research across multiple domains using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
-
-**Document Standards:**
-
-- **Comprehensive Coverage**: Exhaustive research with no critical gaps
-- **Source Verification**: Every factual claim backed by web sources with URL citations
-- **Document Length**: As long as needed to fully cover the research topic
-- **Professional Structure**: Compelling narrative introduction, detailed TOC, and comprehensive summary
-- **Authoritative Sources**: Multiple independent sources for all critical claims
-
-**Your Role:** You are a research facilitator and web data analyst working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
-
-**Final Deliverable**: A complete research document that serves as an authoritative reference on the research topic with:
-
-- Compelling narrative introduction
-- Comprehensive table of contents
-- Detailed research sections with proper citations
-- Executive summary and conclusions
-
-## WORKFLOW ARCHITECTURE
-
-This uses **micro-file architecture** with **routing-based discovery**:
-
-- Each research type has its own step folder
-- Step 01 discovers research type and routes to appropriate sub-workflow
-- Sequential progression within each research type
-- Document state tracked in output frontmatter
-
-## INITIALIZATION
-
-### Configuration Loading
-
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
-
-- `project_name`, `output_folder`, , `planning_artifacts`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as a system-generated value
-
-### Paths
-
-- `installed_path` = `{project-root}/_bmad/bmm/workflows/1-analysis/research`
-- `template_path` = `{installed_path}/research.template.md`
-- `default_output_file` = `{planning_artifacts}/research/{{research_type}}-{{topic}}-research-{{date}}.md` (dynamic based on research type)
-
-## PREREQUISITE
-
-**⛔ Web search required.** If unavailable, abort and tell the user.
-
-## RESEARCH BEHAVIOR
-
-### Web Research Standards
-
-- **Current Data Only**: Search the web to verify and supplement your knowledge with current facts
-- **Source Verification**: Require citations for all factual claims
-- **Anti-Hallucination Protocol**: Never present information without verified sources
-- **Multiple Sources**: Require at least 2 independent sources for critical claims
-- **Conflict Resolution**: Present conflicting views and note discrepancies
-- **Confidence Levels**: Flag uncertain data with [High/Medium/Low Confidence]
-
-### Source Quality Standards
-
-- **Distinguish Clearly**: Facts (from sources) vs Analysis (interpretation) vs Speculation
-- **URL Citation**: Always include source URLs when presenting web search data
-- **Critical Claims**: Market size, growth rates, competitive data need verification
-- **Fact Checking**: Apply fact-checking to critical data points
-
-## Implementation Instructions
-
-Execute research type discovery and routing:
-
-### Research Type Discovery
-
-**Your Role:** You are a research facilitator and web data analyst working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
-
-**Research Standards:**
-
-- **Anti-Hallucination Protocol**: Never present information without verified sources
-- **Current Data Only**: Search the web to verify and supplement your knowledge with current facts
-- **Source Citation**: Always include URLs for factual claims from web searches
-- **Multiple Sources**: Require 2+ independent sources for critical claims
-- **Conflict Resolution**: Present conflicting views and note discrepancies
-- **Confidence Levels**: Flag uncertain data with [High/Medium/Low Confidence]
-
-### Collaborative Research Discovery
-
-"Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with rigorous source verification, while you bring the domain expertise and research direction.
-
-**Let me help you clarify what you'd like to research.**
-
-**First, tell me: What specific topic, problem, or area do you want to research?**
-
-For example:
-
-- 'The electric vehicle market in Europe'
-- 'Cloud migration strategies for healthcare'
-- 'AI implementation in financial services'
-- 'Sustainable packaging regulations'
-- 'Or anything else you have in mind...'
-
-### Topic Exploration and Clarification
-
-Based on the user's initial topic, explore and refine the research scope:
-
-#### Topic Clarification Questions:
-
-1. **Core Topic**: "What exactly about [topic] are you most interested in?"
-2. **Research Goals**: "What do you hope to achieve with this research?"
-3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
-4. **Timeline**: "Are you looking at current state, historical context, or future trends?"
-5. **Application**: "How will you use this research? (product development, strategy, academic, etc.)"
-
-#### Context Building:
-
-- **Initial Input**: User provides topic or research interest
-- **Collaborative Refinement**: Work together to clarify scope and objectives
-- **Goal Alignment**: Ensure research direction matches user needs
-- **Research Boundaries**: Establish clear focus areas and deliverables
-
-### Research Type Identification
-
-After understanding the research topic and goals, identify the most appropriate research approach:
-
-**Research Type Options:**
-
-1. **Market Research** - Market size, growth, competition, customer insights
-   _Best for: Understanding market dynamics, customer behavior, competitive landscape_
-
-2. **Domain Research** - Industry analysis, regulations, technology trends in specific domain
-   _Best for: Understanding industry context, regulatory environment, ecosystem_
-
-3. **Technical Research** - Technology evaluation, architecture decisions, implementation approaches
-   _Best for: Technical feasibility, technology selection, implementation strategies_
-
-**Recommendation**: Based on [topic] and [goals], I recommend [suggested research type] because [specific rationale].
-
-**What type of research would work best for your needs?**
-
-### Research Type Routing
-
-<critical>Based on user selection, route to appropriate sub-workflow with the discovered topic using the following IF block sets of instructions. YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`</critical>
-
-#### If Market Research:
-
-- Set `research_type = "market"`
-- Set `research_topic = [discovered topic from discussion]`
-- Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
-- Load: `./market-steps/step-01-init.md` with topic context
-
-#### If Domain Research:
-
-- Set `research_type = "domain"`
-- Set `research_topic = [discovered topic from discussion]`
-- Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
-- Load: `./domain-steps/step-01-init.md` with topic context
-
-#### If Technical Research:
-
-- Set `research_type = "technical"`
-- Set `research_topic = [discovered topic from discussion]`
-- Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
-- Load: `./technical-steps/step-01-init.md` with topic context
-
-**Important**: The discovered topic from the collaborative discussion should be passed to the research initialization steps, so they don't need to ask "What do you want to research?" again - they can focus on refining the scope for their specific research type.
-
-**Note:** All research workflows require web search for current data and source verification.

_bmad/bmm/workflows/2-plan-workflows/create-prd/data/domain-complexity.csv

@@ -9,5 +9,7 @@ scientific,"research,algorithm,simulation,modeling,computational,analysis,data s
 legaltech,"legal,law,contract,compliance,litigation,patent,attorney,court",high,"Legal ethics;Bar regulations;Data retention;Attorney-client privilege;Court system integration","Legal practice rules;Ethics requirements;Court filing systems;Document standards;Confidentiality","domain-research","legal technology ethics {date};law practice management software requirements;court filing system standards;attorney client privilege technology","ethics_compliance;data_retention;confidentiality_measures;court_integration"
 insuretech,"insurance,claims,underwriting,actuarial,policy,risk,premium",high,"Insurance regulations;Actuarial standards;Data privacy;Fraud detection;State compliance","Insurance regulations by state;Actuarial methods;Risk modeling;Claims processing;Regulatory reporting","domain-research","insurance software regulations {date};actuarial standards software;insurance fraud detection;state insurance compliance","regulatory_requirements;risk_modeling;fraud_detection;reporting_compliance"
 energy,"energy,utility,grid,solar,wind,power,electricity,oil,gas",high,"Grid compliance;NERC standards;Environmental regulations;Safety requirements;Real-time operations","Energy regulations;Grid standards;Environmental compliance;Safety protocols;SCADA systems","domain-research","energy sector software compliance {date};NERC CIP standards;smart grid requirements;renewable energy software standards","grid_compliance;safety_protocols;environmental_compliance;operational_requirements"
+process_control,"industrial automation,process control,PLC,SCADA,DCS,HMI,operational technology,OT,control system,cyberphysical,MES,historian,instrumentation,I&C,P&ID",high,"Functional safety;OT cybersecurity;Real-time control requirements;Legacy system integration;Process safety and hazard analysis;Environmental compliance and permitting;Engineering authority and PE requirements","Functional safety standards;OT security frameworks;Industrial protocols;Process control architecture;Plant reliability and maintainability","domain-research + technical-model","IEC 62443 OT cybersecurity requirements {date};functional safety software requirements {date};industrial process control architecture;ISA-95 manufacturing integration","functional_safety;ot_security;process_requirements;engineering_authority"
+building_automation,"building automation,BAS,BMS,HVAC,smart building,lighting control,fire alarm,fire protection,fire suppression,life safety,elevator,access control,DDC,energy management,sequence of operations,commissioning",high,"Life safety codes;Building energy standards;Multi-trade coordination and interoperability;Commissioning and ongoing operational performance;Indoor environmental quality and occupant comfort;Engineering authority and PE requirements","Building automation protocols;HVAC and mechanical controls;Fire alarm, fire protection, and life safety design;Commissioning process and sequence of operations;Building codes and energy standards","domain-research","smart building software architecture {date};BACnet integration best practices;building automation cybersecurity {date};ASHRAE building standards","life_safety;energy_compliance;commissioning_requirements;engineering_authority"
 gaming,"game,player,gameplay,level,character,multiplayer,quest",redirect,"REDIRECT TO GAME WORKFLOWS","Game design","game-brief","NA","NA"
 general,"",low,"Standard requirements;Basic security;User experience;Performance","General software practices","continue","software development best practices {date}","standard_requirements"

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

@@ -151,7 +151,7 @@ Display menu after setup report:
 
 #### Menu Handling Logic:
 
-- IF C: Update output file frontmatter, adding this step name to the end of the list of stepsCompleted, then load, read entire {nextStepFile}, then execute {nextStepFile}
+- IF C: Update output file frontmatter, adding this step name to the end of the list of stepsCompleted, then read fully and follow: {nextStepFile}
 - IF user provides additional files: Load them, update inputDocuments and documentCounts, redisplay report
 - IF user asks questions: Answer and redisplay menu
 
@@ -162,7 +162,7 @@ Display menu after setup report:
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [frontmatter properly updated with this step added to stepsCompleted and documentCounts], will you then load and read fully `{nextStepFile}` to execute and begin project discovery.
+ONLY WHEN [C continue option] is selected and [frontmatter properly updated with this step added to stepsCompleted and documentCounts], will you then read fully and follow: `{nextStepFile}` to begin project discovery.
 
 ---
 

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

@@ -120,7 +120,7 @@ Display: "**Select an Option:** [C] Continue to {next step name}"
 
 #### Menu Handling Logic:
 
-- IF C: Load, read entire file, then execute the {nextStepFile} determined in step 3
+- IF C: Read fully and follow the {nextStepFile} determined in step 3
 - IF Any other comments or queries: respond and redisplay menu
 
 #### EXECUTION RULES:
@@ -130,7 +130,7 @@ Display: "**Select an Option:** [C] Continue to {next step name}"
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the {nextStepFile} to resume the workflow.
+ONLY WHEN [C continue option] is selected and [current state confirmed], will you then read fully and follow: {nextStepFile} to resume the workflow.
 
 ---
 

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

@@ -185,9 +185,9 @@ Present the project classification for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Product Vision (Step 2b of 13)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask} with the current classification, process the enhanced insights that come back, ask user if they accept the improvements, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
-- IF P: Execute {partyModeWorkflow} with the current classification, process the collaborative insights, ask user if they accept the changes, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
-- IF C: Save classification to {outputFile} frontmatter, add this step name to the end of stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with the current classification, process the enhanced insights that come back, ask user if they accept the improvements, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current classification, process the collaborative insights, ask user if they accept the changes, if yes update classification then redisplay menu, if no keep original classification then redisplay menu
+- IF C: Save classification to {outputFile} frontmatter, add this step name to the end of stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:
@@ -197,7 +197,7 @@ Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Pr
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [classification saved to frontmatter], will you then load and read fully `{nextStepFile}` to explore product vision.
+ONLY WHEN [C continue option] is selected and [classification saved to frontmatter], will you then read fully and follow: `{nextStepFile}` to explore product vision.
 
 ---
 

_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-03-success.md

@@ -175,9 +175,9 @@ Present the success criteria content for user review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to User Journey Mapping (Step 4 of 11)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask} with the current success criteria content, process the enhanced success metrics that come back, ask user "Accept these improvements to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF P: Execute {partyModeWorkflow} with the current success criteria, process the collaborative improvements to metrics and scope, ask user "Accept these changes to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with the current success criteria content, process the enhanced success metrics that come back, ask user "Accept these improvements to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current success criteria, process the collaborative improvements to metrics and scope, ask user "Accept these changes to the success criteria? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:

_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-04-journeys.md

@@ -155,9 +155,9 @@ Present the user journey content for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Domain Requirements (Step 5 of 11)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask} with the current journey content, process the enhanced journey insights that come back, ask user "Accept these improvements to the user journeys? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF P: Execute {partyModeWorkflow} with the current journeys, process the collaborative journey improvements and additions, ask user "Accept these changes to the user journeys? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with the current journey content, process the enhanced journey insights that come back, ask user "Accept these improvements to the user journeys? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current journeys, process the collaborative journey improvements and additions, ask user "Accept these changes to the user journeys? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:

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

@@ -154,9 +154,9 @@ Acknowledge the domain and explore what makes it complex:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue - Save and Proceed to Innovation (Step 6 of 13)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF C: Save content to {outputFile}, update frontmatter, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask}, and when finished redisplay the menu
+- IF P: Read fully and follow: {partyModeWorkflow}, and when finished redisplay the menu
+- IF C: Save content to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#n-present-menu-options)
 
 #### EXECUTION RULES:
@@ -178,7 +178,7 @@ If step was skipped, append nothing and proceed.
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [content saved or skipped], will you then load and read fully `{nextStepFile}` to explore innovation.
+ONLY WHEN [C continue option] is selected and [content saved or skipped], will you then read fully and follow: `{nextStepFile}` to explore innovation.
 
 ---
 

_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-06-innovation.md

@@ -155,9 +155,9 @@ Present the innovation content for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Project Type Analysis (Step 7 of 11)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask} with the current innovation content, process the enhanced innovation insights that come back, ask user "Accept these improvements to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF P: Execute {partyModeWorkflow} with the current innovation content, process the collaborative innovation exploration and ideation, ask user "Accept these changes to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with the current innovation content, process the enhanced innovation insights that come back, ask user "Accept these improvements to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current innovation content, process the collaborative innovation exploration and ideation, ask user "Accept these changes to the innovation analysis? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:
@@ -176,7 +176,7 @@ Display: "**Select:** [A] Advanced Elicitation - Let's try to find innovative an
 
 ### Menu Handling Logic:
 - IF A: Proceed with content generation anyway, then return to menu
-- IF C: Skip this step, then load, read entire file, then execute {nextStepFile}
+- IF C: Skip this step, then read fully and follow: {nextStepFile}
 
 ### EXECUTION RULES:
 - ALWAYS halt and wait for user input after presenting menu

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

@@ -172,9 +172,9 @@ Present the project-type content for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Scoping (Step 8 of 11)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask} with the current project-type content, process the enhanced technical insights that come back, ask user "Accept these improvements to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF P: Execute {partyModeWorkflow} with the current project-type requirements, process the collaborative technical expertise and validation, ask user "Accept these changes to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
-- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with the current project-type content, process the enhanced technical insights that come back, ask user "Accept these improvements to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current project-type requirements, process the collaborative technical expertise and validation, ask user "Accept these changes to the technical requirements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:

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

@@ -183,9 +183,9 @@ Present the scoping decisions for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Functional Requirements (Step 9 of 11)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask} with the current scoping analysis, process the enhanced insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu
-- IF P: Execute {partyModeWorkflow} with the scoping context, process the collaborative insights on MVP and roadmap decisions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
-- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with the current scoping analysis, process the enhanced insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the scoping context, process the collaborative insights on MVP and roadmap decisions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:

_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-09-functional.md

@@ -181,9 +181,9 @@ Present the functional requirements for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Non-Functional Requirements (Step 10 of 11)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask} with the current FR list, process the enhanced capability coverage that comes back, ask user if they accept the additions, if yes update content then redisplay menu, if no keep original content then redisplay menu
-- IF P: Execute {partyModeWorkflow} with the current FR list, process the collaborative capability validation and additions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
-- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with the current FR list, process the enhanced capability coverage that comes back, ask user if they accept the additions, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current FR list, process the collaborative capability validation and additions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:

_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-10-nonfunctional.md

@@ -168,9 +168,9 @@ Present the non-functional requirements for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Polish Document (Step 11 of 12)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask} with the current NFR content, process the enhanced quality attribute insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu
-- IF P: Execute {partyModeWorkflow} with the current NFR list, process the collaborative technical validation and additions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
-- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with the current NFR content, process the enhanced quality attribute insights that come back, ask user if they accept the improvements, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the current NFR list, process the collaborative technical validation and additions, ask user if they accept the changes, if yes update content then redisplay menu, if no keep original content then redisplay menu
+- IF C: Append the final content to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:

_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md

@@ -5,7 +5,7 @@ description: 'Optimize and polish the complete PRD document for flow, coherence,
 # File References
 nextStepFile: './step-12-complete.md'
 outputFile: '{planning_artifacts}/prd.md'
-purposeFile: './data/prd-purpose.md'
+purposeFile: '../data/prd-purpose.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
@@ -169,9 +169,9 @@ Present the polished document for review, then display menu:
 Display: "**Select:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Complete PRD (Step 12 of 12)"
 
 #### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask} with the polished document, process the enhanced refinements that come back, ask user "Accept these polish improvements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original polish then redisplay menu
-- IF P: Execute {partyModeWorkflow} with the polished document, process the collaborative refinements to flow and coherence, ask user "Accept these polish changes? (y/n)", if yes update content with improvements then redisplay menu, if no keep original polish then redisplay menu
-- IF C: Save the polished document to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask} with the polished document, process the enhanced refinements that come back, ask user "Accept these polish improvements? (y/n)", if yes update content with improvements then redisplay menu, if no keep original polish then redisplay menu
+- IF P: Read fully and follow: {partyModeWorkflow} with the polished document, process the collaborative refinements to flow and coherence, ask user "Accept these polish changes? (y/n)", if yes update content with improvements then redisplay menu, if no keep original polish then redisplay menu
+- IF C: Save the polished document to {outputFile}, update frontmatter by adding this step name to the end of the stepsCompleted array, then read fully and follow: {nextStepFile}
 - IF Any other: help user respond, then redisplay menu
 
 #### EXECUTION RULES:

_bmad/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-12-complete.md

@@ -87,39 +87,7 @@ Offer validation workflows to ensure PRD is ready for implementation:
 
 ### 4. Suggest Next Workflows
 
-Provide guidance on logical next workflows - strongly suggesting any of these chosen are started in a fresh context with the appropriate agent:
-
-**Typical Next Workflows:**
-
-**Immediate Next Steps:**
-
-1. **PRD Quality Validation First (Recommended):**
-   - execute the `{validationFlow}` workflow if selected or start a new chat with me and select the validate PRD menu item
-   - Ensures PRD is complete and ready
-   - Identifies any gaps or issues
-   - Validates before committing to architecture/design
-
-2. **UX Design:** `workflow create-ux-design` with the UX-Designer Agent (if UI exists)
-   - User journey insights from step-04 inform interaction design
-   - Functional requirements from step-09 define design scope
-   - Polish-optimized document provides clear design requirements
-
-3. **Technical Architecture:** `workflow create-architecture` with the Architect Agent
-   - Project-type requirements from step-07 guide technical decisions
-   - Non-functional requirements from step-10 inform architecture choices
-   - Functional requirements define system capabilities
-
-4. **Epic Breakdown:** `workflow create-epics-and-stories` with me again - but really recommend first doing a UX if needed and an architecture!
-   - Functional requirements from step-09 become epics and stories
-   - Scope definition from step-03 guides sprint planning
-   - Richer when created after UX/architecture
-
-**Strategic Considerations:**
-
-- Validation adds confidence before architecture/design investment
-- UX design and architecture can happen in parallel after validation
-- Epics/stories are richer when created after UX/architecture
-- Order depends on team preferences and project needs
+PRD complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Create PRD`.
 
 ### 5. Final Completion Confirmation
 
@@ -149,30 +117,6 @@ Provide guidance on logical next workflows - strongly suggesting any of these ch
 ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
 ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 
-## WORKFLOW COMPLETION CHECKLIST:
-
-### Document Structure Complete:
-
-- [ ] Executive Summary with vision and differentiator
-- [ ] Success Criteria with measurable outcomes
-- [ ] Product Scope (MVP, Growth, Vision)
-- [ ] User Journeys (comprehensive coverage)
-- [ ] Domain Requirements (if applicable)
-- [ ] Innovation Analysis (if applicable)
-- [ ] Project-Type Requirements
-- [ ] Functional Requirements (capability contract)
-- [ ] Non-Functional Requirements
-- [ ] Document polished for flow and coherence
-
-### Process Complete:
-
-- [ ] All steps (including polish) completed with user confirmation
-- [ ] All content saved and optimized
-- [ ] Frontmatter properly updated
-- [ ] Workflow status file updated (if exists)
-- [ ] Validation options presented
-- [ ] Next steps clearly communicated
-
 ## FINAL REMINDER to give the user:
 
 The polished PRD serves as the foundation for all subsequent product development activities. All design, architecture, and development work should trace back to the requirements and vision documented in this PRD - update it also as needed as you continue planning.

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

@@ -4,7 +4,7 @@ description: 'Discovery & Understanding - Understand what user wants to edit and
 
 # File references (ONLY variables used in this step)
 altStepFile: './step-e-01b-legacy-conversion.md'
-prdPurpose: '{project-root}/src/modules/bmm/workflows/2-plan-workflows/prd/data/prd-purpose.md'
+prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
 advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
@@ -189,7 +189,7 @@ Display: "**Edit Requirements Understood**
 
 **Proceeding to deep review and analysis...**"
 
-Load and execute next step (step-e-02-review.md)
+Read fully and follow: next step (step-e-02-review.md)
 
 **IF PRD is Legacy (Non-Standard) AND no validation report:**
 
@@ -216,7 +216,7 @@ Present MENU OPTIONS below for user selection
 
 #### Menu Handling Logic:
 
-- IF C (Convert): Load, read entire file, then execute {altStepFile} (step-e-01b-legacy-conversion.md)
+- IF C (Convert): Read fully and follow: {altStepFile} (step-e-01b-legacy-conversion.md)
 - IF E (Edit As-Is): Display "Proceeding with edits..." then load next step
 - IF X (Exit): Display summary and exit
 - IF Any other: help user, then redisplay menu

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

@@ -5,7 +5,7 @@ description: 'Legacy PRD Conversion Assessment - Analyze legacy PRD and propose
 # File references (ONLY variables used in this step)
 nextStepFile: './step-e-02-review.md'
 prdFile: '{prd_file_path}'
-prdPurpose: '{project-root}/src/modules/bmm/workflows/2-plan-workflows/prd/data/prd-purpose.md'
+prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
 ---
 
 # Step E-1B: Legacy PRD Conversion Assessment
@@ -182,7 +182,7 @@ Edit goals: {summary}
 
 **Proceeding to deep review...**"
 
-Load and execute {nextStepFile} (step-e-02-review.md)
+Read fully and follow: {nextStepFile} (step-e-02-review.md)
 
 ---
 

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

@@ -6,7 +6,7 @@ description: 'Deep Review & Analysis - Thoroughly review existing PRD and prepar
 nextStepFile: './step-e-03-edit.md'
 prdFile: '{prd_file_path}'
 validationReport: '{validation_report_path}'  # If provided
-prdPurpose: '{project-root}/src/modules/bmm/workflows/2-plan-workflows/prd/data/prd-purpose.md'
+prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
 advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 ---
 
@@ -204,7 +204,7 @@ Display: "**Change Plan Approved**
 
 **Proceeding to edit step...**"
 
-Load and execute {nextStepFile} (step-e-03-edit.md)
+Read fully and follow: {nextStepFile} (step-e-03-edit.md)
 
 ### 7. Present MENU OPTIONS (If User Wants Discussion)
 
@@ -219,8 +219,8 @@ Load and execute {nextStepFile} (step-e-03-edit.md)
 
 #### Menu Handling Logic:
 
-- IF A: Execute {advancedElicitationTask}, then return to discussion
-- IF P: Execute {partyModeWorkflow}, then return to discussion
+- IF A: Read fully and follow: {advancedElicitationTask}, then return to discussion
+- IF P: Read fully and follow: {partyModeWorkflow}, then return to discussion
 - IF C: Document approval, then load {nextStepFile}
 - IF Any other: discuss, then redisplay menu
 

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

@@ -5,7 +5,7 @@ description: 'Edit & Update - Apply changes to PRD following approved change pla
 # File references (ONLY variables used in this step)
 nextStepFile: './step-e-04-complete.md'
 prdFile: '{prd_file_path}'
-prdPurpose: '{project-root}/src/modules/bmm/workflows/2-plan-workflows/prd/data/prd-purpose.md'
+prdPurpose: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
 ---
 
 # Step E-3: Edit & Update
@@ -222,7 +222,7 @@ Display:
 
 #### Menu Handling Logic:
 
-- IF V (Validate): Display "Starting validation workflow..." then load and execute steps-v/step-v-01-discovery.md
+- IF V (Validate): Display "Starting validation workflow..." then read fully and follow: steps-v/step-v-01-discovery.md
 - IF S (Summary): Present edit summary and exit
 - IF A (Adjust): Accept additional requirements, loop back to editing
 - IF X (Exit): Display summary and exit

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

@@ -4,7 +4,7 @@ description: 'Complete & Validate - Present options for next steps including ful
 
 # File references (ONLY variables used in this step)
 prdFile: '{prd_file_path}'
-validationWorkflow: './steps-v/step-v-01-discovery.md'
+validationWorkflow: '../steps-v/step-v-01-discovery.md'
 ---
 
 # Step E-4: Complete & Validate
@@ -120,14 +120,14 @@ Display:
   - Display: "This will run all 13 validation checks on the updated PRD."
   - Display: "Preparing to validate: {prd_file_path}"
   - Display: "**Proceeding to validation...**"
-  - Load, read entire file, then execute {validationWorkflow} (steps-v/step-v-01-discovery.md)
+  - 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
 
 - **IF E (Edit More):**
   - Display: "**Additional Edits**"
   - Ask: "What additional edits would you like to make?"
   - Accept input, then display: "**Returning to edit step...**"
-  - Load and execute step-e-03-edit.md again
+  - Read fully and follow: step-e-03-edit.md again
 
 - **IF S (Summary):**
   - Display detailed summary including:

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

@@ -187,9 +187,9 @@ Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Conti
 
 #### Menu Handling Logic:
 
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF C: Load, read entire file, then execute {nextStepFile} to begin format detection
+- IF A: Read fully and follow: {advancedElicitationTask}, and when finished redisplay the menu
+- IF P: Read fully and follow: {partyModeWorkflow}, and when finished redisplay the menu
+- IF C: Read fully and follow: {nextStepFile} to begin format detection
 - IF user provides additional document: Load it, update report, redisplay summary
 - IF Any other: help user, then redisplay menu
 

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

@@ -136,7 +136,7 @@ Display: "**Format Detected:** {classification}
 
 Proceeding to systematic validation checks..."
 
-Immediately load and execute {nextStepFile} (step-v-03-density-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-03-density-validation.md)
 
 **IF format is Non-Standard (< 3 core sections):**
 
@@ -161,8 +161,8 @@ Present MENU OPTIONS below for user selection
 
 #### Menu Handling Logic:
 
-- IF A (Parity Check): Load, read entire file, then execute {altStepFile} (step-v-02b-parity-check.md)
-- IF B (Validate As-Is): Display "Proceeding with validation..." then load, read entire file, then execute {nextStepFile}
+- IF A (Parity Check): Read fully and follow: {altStepFile} (step-v-02b-parity-check.md)
+- IF B (Validate As-Is): Display "Proceeding with validation..." then read fully and follow: {nextStepFile}
 - IF C (Exit): Display format findings summary and exit validation
 - IF Any other: help user respond, then redisplay menu
 

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

@@ -180,7 +180,7 @@ Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to r
 
 #### Menu Handling Logic:
 
-- IF C (Continue): Display "Proceeding with validation..." then load, read entire file, then execute {nextStepFile}
+- IF C (Continue): Display "Proceeding with validation..." then read fully and follow: {nextStepFile}
 - IF E (Exit): Display parity summary and exit validation
 - IF S (Save): Confirm saved, display summary, exit
 - IF Any other: help user respond, then redisplay menu

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

@@ -148,7 +148,7 @@ Severity: {Critical/Warning/Pass}
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile} (step-v-04-brief-coverage-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-04-brief-coverage-validation.md)
 
 ---
 

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

@@ -76,7 +76,7 @@ Display: "**Product Brief Coverage: Skipped** (No Product Brief provided)
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile}
+Without delay, read fully and follow: {nextStepFile}
 
 **IF Product Brief exists:** Continue to step 2 below
 
@@ -186,7 +186,7 @@ Overall Coverage: {assessment}
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile} (step-v-05-measurability-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-05-measurability-validation.md)
 
 ---
 

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

@@ -201,7 +201,7 @@ Total Violations: {count} ({severity})
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile} (step-v-06-traceability-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-06-traceability-validation.md)
 
 ---
 

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

@@ -189,7 +189,7 @@ Total Issues: {count} ({severity})
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile} (step-v-07-implementation-leakage-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-07-implementation-leakage-validation.md)
 
 ---
 

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

@@ -178,7 +178,7 @@ Total Violations: {count} ({severity})
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile} (step-v-08-domain-compliance-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-08-domain-compliance-validation.md)
 
 ---
 

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

@@ -161,7 +161,7 @@ Domain: {domain} (low complexity)
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile}
+Without delay, read fully and follow: {nextStepFile}
 
 ### 6. Report Compliance Findings (High-Complexity Domains)
 
@@ -213,7 +213,7 @@ Compliance Status: {status}
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile} (step-v-09-project-type-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-09-project-type-validation.md)
 
 ---
 

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

@@ -234,7 +234,7 @@ Compliance: {score}%
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile} (step-v-10-smart-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-10-smart-validation.md)
 
 ---
 

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

@@ -179,7 +179,7 @@ FR Quality: {percentage}% with acceptable scores ({severity})
 
 **Proceeding to next validation check...**"
 
-Immediately load and execute {nextStepFile} (step-v-11-holistic-quality-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-11-holistic-quality-validation.md)
 
 ---
 

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

@@ -66,7 +66,7 @@ Assess the PRD as a cohesive, compelling document - evaluating document flow, du
 
 "Perform holistic quality assessment on this PRD using multi-perspective evaluation:
 
-**Load and execute Advanced Elicitation workflow:**
+**Read fully and follow the Advanced Elicitation workflow:**
 {advancedElicitationTask}
 
 **Evaluate the PRD from these perspectives:**
@@ -232,7 +232,7 @@ Overall Rating: {rating}/5 - {label}
 
 **Proceeding to final validation checks...**"
 
-Immediately load and execute {nextStepFile} (step-v-12-completeness-validation.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-12-completeness-validation.md)
 
 ---
 

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

@@ -212,7 +212,7 @@ Overall Completeness: {percentage}% ({severity})
 
 **Proceeding to final step...**"
 
-Immediately load and execute {nextStepFile} (step-v-13-report-complete.md)
+Without delay, read fully and follow: {nextStepFile} (step-v-13-report-complete.md)
 
 ---
 

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

@@ -163,7 +163,7 @@ Display:
 **[R] Review Detailed Findings** - Walk through validation report section by section
 **[E] Use Edit Workflow** - Use validation report with Edit workflow for systematic improvements
 **[F] Fix Simpler Items** - Immediate fixes for simple issues (anti-patterns, leakage, missing headers)
-**[X] Exit** - Exit and review validation report
+**[X] Exit** - Exit and Suggest Next Steps.
 
 #### EXECUTION RULES:
 
@@ -181,7 +181,7 @@ Display:
 - **IF E (Use Edit Workflow):**
   - Explain: "The Edit workflow (steps-e/) can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
   - Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
-  - If yes: Load and execute steps-e/step-e-01-discovery.md
+  - If yes: Read fully and follow: steps-e/step-e-01-discovery.md
   - If no: Return to menu
 
 - **IF F (Fix Simpler Items):**
@@ -197,8 +197,7 @@ Display:
 - **IF X (Exit):**
   - Display: "**Validation Report Saved:** {validationReportPath}"
   - Display: "**Summary:** {overall status} - {recommendation}"
-  - Display: "**Next Steps:** Review the validation report and address findings. For systematic improvements, consider using Edit workflow when available, or manually fix issues identified in this report."
-  - Exit validation
+  - PRD Validation complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Validate PRD`.
 
 - **IF Any other:** Help user, then redisplay menu
 

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

@@ -0,0 +1,63 @@
+---
+name: create-prd
+description: Create a comprehensive PRD (Product Requirements Document) through structured workflow facilitation
+main_config: '{project-root}/_bmad/bmm/config.yaml'
+nextStep: './steps-c/step-01-init.md'
+---
+
+# PRD Create Workflow
+
+**Goal:** Create comprehensive PRDs through structured workflow facilitation.
+
+**Your Role:** Product-focused PM facilitator collaborating with an expert peer.
+
+You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {main_config} and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `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 configured `{communication_language}`.
+
+### 2. Route to Create Workflow
+
+"**Create Mode: Creating a new PRD from scratch.**"
+
+Read fully and follow: `{nextStep}` (steps-c/step-01-init.md)

_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md

@@ -0,0 +1,65 @@
+---
+name: edit-prd
+description: Edit and improve an existing PRD - enhance clarity, completeness, and quality
+main_config: '{project-root}/_bmad/bmm/config.yaml'
+editWorkflow: './steps-e/step-e-01-discovery.md'
+---
+
+# PRD Edit Workflow
+
+**Goal:** Edit and improve existing PRDs through structured enhancement workflow.
+
+**Your Role:** PRD improvement specialist.
+
+You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {main_config} and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `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 configured `{communication_language}`.
+
+### 2. Route to Edit Workflow
+
+"**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)

_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md

@@ -0,0 +1,65 @@
+---
+name: validate-prd
+description: Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality
+main_config: '{project-root}/_bmad/bmm/config.yaml'
+validateWorkflow: './steps-v/step-v-01-discovery.md'
+---
+
+# PRD Validate Workflow
+
+**Goal:** Validate existing PRDs against BMAD standards through comprehensive review.
+
+**Your Role:** Validation Architect and Quality Assurance Specialist.
+
+You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {main_config} and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `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 configured `{communication_language}`.
+
+### 2. Route to Validate Workflow
+
+"**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)

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -159,7 +159,7 @@ Show the generated project understanding content and present choices:
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the document. Only after the content is saved to document, load `./step-03-core-experience.md` and execute the instructions.
+When user selects 'C', append the content directly to the document. Only after the content is saved to document, read fully and follow: `./step-03-core-experience.md`.
 
 ## SUCCESS METRICS:
 

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -161,7 +161,7 @@ Show the generated core experience content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current core experience content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current core experience content
 - Process the enhanced experience insights that come back
 - Ask user: "Accept these improvements to the core experience definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -169,7 +169,7 @@ Show the generated core experience content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current core experience definition
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current core experience definition
 - Process the collaborative experience improvements that come back
 - Ask user: "Accept these changes to the core experience definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -164,7 +164,7 @@ Show the generated emotional response content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current emotional response content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current emotional response content
 - Process the enhanced emotional insights that come back
 - Ask user: "Accept these improvements to the emotional response definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -172,7 +172,7 @@ Show the generated emotional response content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current emotional response definition
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current emotional response definition
 - Process the collaborative emotional insights that come back
 - Ask user: "Accept these changes to the emotional response definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -179,7 +179,7 @@ Show the generated inspiration analysis content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current inspiration analysis content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current inspiration analysis content
 - Process the enhanced pattern insights that come back
 - Ask user: "Accept these improvements to the inspiration analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -187,7 +187,7 @@ Show the generated inspiration analysis content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis
 - Process the collaborative pattern insights that come back
 - Ask user: "Accept these changes to the inspiration analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -197,7 +197,7 @@ Show the generated inspiration analysis content and present choices:
 
 - Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: append step to end of stepsCompleted array
-- Load and execute`./step-06-design-system.md`
+- Read fully and follow: `./step-06-design-system.md`
 
 ## APPEND TO DOCUMENT:
 

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -197,7 +197,7 @@ Show the generated design system content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current design system content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current design system content
 - Process the enhanced design system insights that come back
 - Ask user: "Accept these improvements to the design system decision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -205,7 +205,7 @@ Show the generated design system content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design system choice
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design system choice
 - Process the collaborative design system insights that come back
 - Ask user: "Accept these changes to the design system decision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -199,7 +199,7 @@ Show the generated defining experience content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current defining experience content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current defining experience content
 - Process the enhanced experience insights that come back
 - Ask user: "Accept these improvements to the defining experience? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -207,7 +207,7 @@ Show the generated defining experience content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current defining experience
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current defining experience
 - Process the collaborative experience insights that come back
 - Ask user: "Accept these changes to the defining experience? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -169,7 +169,7 @@ Show the generated visual foundation content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current visual foundation content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current visual foundation content
 - Process the enhanced visual insights that come back
 - Ask user: "Accept these improvements to the visual foundation? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -177,7 +177,7 @@ Show the generated visual foundation content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current visual foundation
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current visual foundation
 - Process the collaborative visual insights that come back
 - Ask user: "Accept these changes to the visual foundation? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -169,7 +169,7 @@ Show the generated design direction content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current design direction content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current design direction content
 - Process the enhanced design insights that come back
 - Ask user: "Accept these improvements to the design direction? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -177,7 +177,7 @@ Show the generated design direction content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design direction
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design direction
 - Process the collaborative design insights that come back
 - Ask user: "Accept these changes to the design direction? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -187,7 +187,7 @@ Show the generated user journey content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current user journey content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current user journey content
 - Process the enhanced journey insights that come back
 - Ask user: "Accept these improvements to the user journeys? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -195,7 +195,7 @@ Show the generated user journey content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current user journeys
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current user journeys
 - Process the collaborative journey insights that come back
 - Ask user: "Accept these changes to the user journeys? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -193,7 +193,7 @@ Show the generated component strategy content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current component strategy content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current component strategy content
 - Process the enhanced component insights that come back
 - Ask user: "Accept these improvements to the component strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -201,7 +201,7 @@ Show the generated component strategy content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current component strategy
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current component strategy
 - Process the collaborative component insights that come back
 - Ask user: "Accept these changes to the component strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -182,7 +182,7 @@ Show the generated UX patterns content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current UX patterns content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current UX patterns content
 - Process the enhanced pattern insights that come back
 - Ask user: "Accept these improvements to the UX patterns? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -190,7 +190,7 @@ Show the generated UX patterns content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current UX patterns
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current UX patterns
 - Process the collaborative pattern insights that come back
 - Ask user: "Accept these changes to the UX patterns? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.md

@@ -30,8 +30,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -209,7 +209,7 @@ Show the generated responsive and accessibility content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current responsive/accessibility content
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current responsive/accessibility content
 - Process the enhanced insights that come back
 - Ask user: "Accept these improvements to the responsive/accessibility strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -217,7 +217,7 @@ Show the generated responsive and accessibility content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy
 - Process the collaborative insights that come back
 - Ask user: "Accept these changes to the responsive/accessibility strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-14-complete.md

@@ -82,70 +82,13 @@ Update the main workflow status file:
 
 ### 3. Suggest Next Steps
 
-Provide guidance on logical next workflows:
-
-**Typical Next Workflows:**
-
-**Immediate Next Steps:**
-
-1. **Wireframe Generation** - Create detailed wireframes based on UX specification
-2. **Interactive Prototype** - Build clickable prototypes for user testing
-3. **Solution Architecture** - Technical architecture design with UX context
-4. **Figma Design** - High-fidelity visual design implementation
-
-**Visual Design Workflows:**
-
-- Wireframe Generation → Interactive Prototype → Figma Design
-- Component Showcase → AI Frontend Prompt → Design System Implementation
-
-**Development Workflows:**
-
-- Solution Architecture → Epic Creation → Development Sprints
-
-**What would be most valuable to tackle next?**
-
-### 4. Document Quality Check
-
-Perform final validation of the UX design:
-
-**Completeness Check:**
-
-- Does the specification clearly communicate the design vision?
-- Are user journeys thoroughly documented?
-- Are all critical components specified?
-- Are responsive and accessibility requirements comprehensive?
-- Is there clear guidance for implementation?
-
-**Consistency Check:**
-
-- Do all sections align with the emotional goals?
-- Is design system integration clearly defined?
-- Are patterns consistent across all user flows?
-- Does visual direction match established foundation?
+UX Design complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Create UX`.
 
 ### 5. Final Completion Confirmation
 
-Confirm completion with user:
-"**Your UX Design Specification for {{project_name}} is now complete and ready for implementation!**
+Congratulate the user on the completion you both completed together of the UX.
 
-**The specification contains everything needed to:**
 
-- Guide visual designers in creating the final interfaces
-- Inform developers of all UX requirements and patterns
-- Ensure consistency across all user interactions
-- Maintain accessibility and responsive design standards
-- Provide a foundation for user testing and iteration
-
-**Ready to continue with:**
-
-- Wireframe generation for detailed layouts?
-- Interactive prototype for user testing?
-- Solution architecture for technical planning?
-- Visual design implementation?
-
-**Or would you like to review the complete specification first?**
-
-[UX Design Workflow Complete]"
 
 ## SUCCESS METRICS:
 

_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md

@@ -1,7 +1,6 @@
 ---
 name: create-ux-design
 description: Work with a peer UX Design expert to plan your applications UX patterns, look and feel.
-web_bundle: true
 ---
 
 # Create UX Design Workflow
@@ -40,4 +39,4 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 ## EXECUTION
 
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-- Load and execute `steps/step-01-init.md` to begin the UX design workflow.
+- Read fully and follow: `steps/step-01-init.md` to begin the UX design workflow.

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

@@ -1,433 +0,0 @@
----
-validationTarget: 'PRD Workflow Structure'
-validationDate: '2026-01-08'
-inputDocuments: []
-validationStepsCompleted: ['discovery', 'frontmatter-validation', 'content-validation', 'documentation-validation', 'integration-validation', 'corrections-applied']
-validationStatus: COMPLETE - PRODUCTION READY
----
-
-# PRD Workflow Validation Report
-
-**Workflow Being Validated:** /Users/brianmadison/dev/BMAD-METHOD/src/modules/bmm/workflows/2-plan-workflows/prd
-**Validation Date:** 2026-01-08
-**Validator:** BMAD Workflow Validation System
-
----
-
-## Executive Summary
-
-This validation report assesses the PRD workflow structure against BMAD workflow standards. The PRD workflow is a tri-modal workflow system with Create, Validate, and Edit phases.
-
----
-
-## 1. File Structure & Size Analysis
-
-### Folder Structure
-
-```
-prd/
-├── workflow.md (main workflow file)
-├── steps-c/ (Create steps - 12 files)
-├── steps-v/ (Validation steps - 13 files)
-├── steps-e/ (Edit steps - 5 files)
-├── data/
-│   └── prd-purpose.md
-└── templates/
-    └── prd-template.md
-```
-
-**✅ Structure Status**: PASS - All required folders present
-
-### File Size Analysis
-
-#### Steps-C (Create Steps) - 12 files
-| File | Lines | Status |
-|------|-------|--------|
-| step-01-init.md | 191 | ⚠️ Approaching limit |
-| step-01b-continue.md | 153 | ✅ Good |
-| step-02-discovery.md | 197 | ⚠️ Approaching limit |
-| step-03-success.md | 226 | ⚠️ Approaching limit |
-| step-04-journeys.md | 213 | ⚠️ Approaching limit |
-| step-05-domain.md | 193 | ⚠️ Approaching limit |
-| step-06-innovation.md | 226 | ⚠️ Approaching limit |
-| step-07-project-type.md | 225 | ⚠️ Approaching limit |
-| step-08-scoping.md | 228 | ⚠️ Approaching limit |
-| step-09-functional.md | 231 | ⚠️ Approaching limit |
-| step-10-nonfunctional.md | 242 | ⚠️ Approaching limit |
-| step-11-polish.md | 217 | ⚠️ Approaching limit |
-| step-12-complete.md | 185 | ✅ Good |
-
-#### Steps-V (Validation Steps) - 13 files
-| File | Lines | Status |
-|------|-------|--------|
-| step-v-01-discovery.md | 217 | ⚠️ Approaching limit |
-| step-v-02-format-detection.md | 191 | ⚠️ Approaching limit |
-| step-v-02b-parity-check.md | 209 | ⚠️ Approaching limit |
-| step-v-03-density-validation.md | 174 | ✅ Good |
-| step-v-04-brief-coverage-validation.md | 214 | ⚠️ Approaching limit |
-| step-v-05-measurability-validation.md | 228 | ⚠️ Approaching limit |
-| step-v-06-traceability-validation.md | 217 | ⚠️ Approaching limit |
-| step-v-07-implementation-leakage-validation.md | 205 | ⚠️ Approaching limit |
-| step-v-08-domain-compliance-validation.md | 243 | ⚠️ Approaching limit |
-| step-v-09-project-type-validation.md | 263 | ❌ Exceeds limit |
-| step-v-10-smart-validation.md | 209 | ⚠️ Approaching limit |
-| step-v-11-holistic-quality-validation.md | 264 | ❌ Exceeds limit |
-| step-v-12-completeness-validation.md | 242 | ⚠️ Approaching limit |
-| step-v-13-report-complete.md | 231 | ⚠️ Approaching limit |
-
-#### Steps-E (Edit Steps) - 5 files
-| File | Lines | Status |
-|------|-------|--------|
-| step-e-01-discovery.md | 206 | ⚠️ Approaching limit |
-| step-e-01b-legacy-conversion.md | 208 | ⚠️ Approaching limit |
-| step-e-02-review.md | 249 | ⚠️ Approaching limit |
-| step-e-03-edit.md | 253 | ❌ Exceeds limit |
-| step-e-04-complete.md | 168 | ✅ Good |
-
-#### Data & Templates
-| File | Lines | Status |
-|------|-------|--------|
-| data/prd-purpose.md | 197 | ⚠️ Approaching limit |
-| templates/prd-template.md | 10 | ✅ Good |
-| workflow.md | 114 | ✅ Good |
-
-### File Size Statistics
-
-- **Total Files**: 32 markdown files
-- **✅ Good (<200 lines)**: 6 files (18.8%)
-- **⚠️ Approaching limit (200-250)**: 23 files (71.9%)
-- **❌ Exceeds limit (>250)**: 3 files (9.4%)
-- **Average lines per file**: 213.3 lines
-
-### ⚠️ Recommendations
-
-1. **Files Exceeding 250-line limit**:
-   - `step-v-09-project-type-validation.md` (263 lines) - Consider splitting into sub-steps
-   - `step-v-11-holistic-quality-validation.md` (264 lines) - Consider splitting into sub-steps
-   - `step-e-03-edit.md` (253 lines) - Consider splitting into sub-steps
-
-2. **Files Approaching Limit**:
-   - Many files are in the 200-250 line range
-   - Monitor these files as further additions may push them over the limit
-   - Consider proactive refactoring where appropriate
-
----
-
-## 2. Frontmatter Structure Validation
-
-### Files Checked: 29 total files
-
-**✅ Overall Status:** ALL VALID - One Issue Fixed
-
-#### Main Workflow (workflow.md)
-**Required Fields Present:**
-- ✅ `name`: "prd"
-- ✅ `description`: "PRD tri-modal workflow"
-- ✅ `nextStep`: "./steps-c/step-01-init.md"
-- ✅ `validateWorkflow`: "./steps-v/step-v-01-discovery.md"
-- ✅ `editWorkflow`: "./steps-e/step-e-01-discovery.md" (FIXED - was assess-workflow.md)
-
-#### Create Steps (steps-c)
-- ✅ All 13 files have proper name, description, nextStepFile
-- ✅ Proper sequencing from step-01 through step-12
-- ✅ Consistent output file references
-
-#### Validation Steps (steps-v)
-- ✅ All 13 files have complete frontmatter
-- ✅ Proper sequential chain maintained
-- ✅ No broken internal references
-
-#### Edit Steps (steps-e)
-- ✅ All files have required fields
-- ✅ Proper routing with altStepFile references
-
-### ✅ All Issues Resolved
-
-**1. Broken Edit Workflow Reference:**
-```yaml
-# Current (INCORRECT):
-editWorkflow: './steps-e/step-e-01-assess-workflow.md'
-
-# Should be:
-editWorkflow: './steps-e/step-e-01-discovery.md'
-```
-
-**2. Step Numbering Gap:**
-- Original `step-11-complete.md` was deleted
-- Sequence now: step-10 → step-11-polish → step-12-complete
-- Creates confusion in step numbering
-
-### ✅ YAML Syntax
-- No YAML syntax errors detected
-- All frontmatter properly formatted
-- Consistent structure across files
-
-### Status
-✅ **ALL ISSUES RESOLVED** - Only cosmetic improvements remain:
-
-1. **✅ FIXED**: Edit workflow path corrected in workflow.md
-2. **⚠️ OPTIONAL**: Address step numbering gap for clarity
-3. **⚠️ OPTIONAL**: Rename step-01b-continue.md to step-01a-continue.md for consistency
-
----
-
-## 3. Step File Content Validation
-
-### Content Quality Assessment: 4.5/5 - EXCELLENT
-
-#### Files Reviewed: 10 representative files across all modes
-
-#### ✅ Strengths
-
-**1. Comprehensive Structure:**
-- Clear step goal sections in all files
-- Detailed mandatory execution rules
-- Well-defined execution protocols
-- Context boundaries clearly specified
-- Mandatory sequence with numbered steps
-- System success/failure metrics present
-
-**2. BMAD Compliance:**
-- ✅ JIT loading references consistently mentioned
-- ✅ State tracking requirements documented
-- ✅ Append-only building instructions present
-- ✅ Critical rules properly emphasized with emojis
-- ✅ Sequential enforcement clearly stated
-
-**3. Instructional Quality:**
-- Clear, unambiguous instructions
-- Proper menu handling rules (where applicable)
-- Excellent continuation checks
-- Strong role definition for each mode
-
-**4. Role Clarity:**
-- Create Mode: "Product-focused PM facilitator"
-- Validate Mode: "Validation Architect and Quality Assurance Specialist"
-- Edit Mode: "PRD improvement specialist"
-
-#### ⚠️ Minor Improvement Opportunities
-
-**1. Header Formatting:**
-- Some inconsistency in header level usage across files
-- Recommend standardizing H2/H3 usage
-
-**2. Edit Mode Completeness:**
-- Edit mode has fewer steps (5 vs 12/13 for other modes)
-- Documentation marks it as "Future" but implementation exists
-
-#### Recommendations
-1. **LOW PRIORITY**: Standardize header formatting across all step files
-2. **LOW PRIORITY**: Complete remaining edit mode steps for parity
-3. **MAINTAIN**: Current excellent quality standards
-
----
-
-## 4. Documentation Validation
-
-### Documentation Completeness: ✅ COMPREHENSIVE
-
-#### Main Components Present
-- ✅ Workflow Definition (workflow.md)
-- ✅ Purpose Document (data/prd-purpose.md)
-- ✅ Template (templates/prd-template.md)
-- ✅ Three Mode Implementations (Create: 12, Validate: 13, Edit: 5 steps)
-
-#### Clarity Assessment: ✅ EXCELLENT
-
-**Strong Points:**
-1. Clear mode determination (commands, flags, menu selection)
-2. Detailed routing instructions for each mode
-3. Comprehensive workflow architecture explanation
-4. Well-defined critical rules with visual emphasis
-5. Professional presentation with consistent formatting
-
-#### ⚠️ Minor Issues Found
-
-**1. Step Count Mismatch:**
-- workflow.md mentions "11 steps" for Create mode
-- Actually implements 12 steps
-- Could confuse users
-
-**2. Edit Mode Status:**
-- workflow.md calls Edit mode "Future"
-- Edit mode steps are actually implemented
-- Should reflect current status
-
-**3. Template Completeness:**
-- PRD template is minimal (10 lines)
-- Could benefit from section placeholders
-
-**4. Missing README:**
-- No onboarding documentation for new users
-- Not critical but would be helpful
-
-#### Recommendations
-
-**HIGH PRIORITY:**
-1. Fix step count reference to match implementation (12 steps)
-2. Update edit mode documentation to "Implemented"
-
-**MEDIUM PRIORITY:**
-3. Enhance PRD template with section structure
-4. Add quick-start README for new users
-
-**LOW PRIORITY:**
-5. Add troubleshooting section
-6. Document external dependencies (domain-complexity.csv, project-types.csv)
-
----
-
-## 5. Integration & Compatibility Validation
-
-### Integration Status: 85% Ready
-
-#### ✅ Successfully Integrated Components
-
-**1. Agent Menu Registration:**
-- ✅ Registered in PM agent menu
-- ✅ Trigger: `PR` or fuzzy match on `prd`
-- ✅ Command: `/bmad:bmm:workflows:create-prd`
-- ✅ Proper workflow path configuration
-
-**2. External Workflow References:**
-- ✅ Party-mode workflow: Exists at `/src/core/workflows/party-mode/workflow.md`
-- ✅ Advanced-elicitation task: Exists at `/src/core/workflows/advanced-elicitation/workflow.xml`
-
-**3. Directory Structure:**
-- ✅ Complete step architecture (all 3 modes)
-- ✅ All referenced step files exist
-- ✅ Data files available
-
-#### ✅ Configuration & Installation - WORKING AS DESIGNED
-
-**1. BMM Config Reference:**
-- Path: `{project-root}/_bmad/bmm/config.yaml`
-- **Status:** ✅ Correct installation-time placeholder
-- Resolves to actual config during workflow installation
-- **Note:** This is expected behavior, not an issue
-
-**2. Planning Artifacts Folder:**
-- Reference: `{planning_artifacts}/prd.md`
-- **Status:** ✅ Correct installation-time placeholder
-- Created/resolved during workflow installation
-- **Note:** This is expected behavior, not an issue
-
-**3. Edit Mode Implementation:**
-- Current: 5 steps (Discovery, Legacy Conversion branch, Review, Edit, Complete)
-- **Status:** ✅ Functionally complete
-- Edit mode is inherently simpler than create mode (targeted improvements vs full creation)
-- Uses subprocesses for complex operations
-- Validation integration ensures quality
-- **Note:** Edit workflow is complete and well-designed
-
-#### Configuration Analysis
-
-**Placeholder Usage:**
-- `{project-root}`: ✅ Properly used
-- `{planning_artifacts}`: ⚠️ Referenced but folder missing
-- `{nextStep}`, `{validateWorkflow}`, etc: ✅ Properly resolved
-
-#### Recommendations
-
-**✅ ALL CRITICAL ISSUES RESOLVED:**
-
-The only true critical issue (edit workflow path) has been fixed. All other items flagged as "critical" were actually working as designed (installation-time placeholders).
-
-**LOW PRIORITY:**
-3. Add CLI command registration for standalone execution (optional enhancement)
-4. Consider adding workflow to additional agent menus (UX designer, architect)
-5. Create standalone execution documentation (nice-to-have)
-6. Address step numbering gap if desired (cosmetic)
-
----
-
-## 6. Executive Summary & Overall Assessment
-
-### Overall Validation Status: ✅ PRODUCTION-READY
-
-#### Validation Scores by Category
-
-| Category | Status | Score | Notes |
-|----------|--------|-------|-------|
-| **File Structure & Size** | ⚠️ WARNINGS | 7/10 | 3 files exceed 250-line limit, 23 approaching |
-| **Frontmatter Validation** | ✅ PASS | 9/10 | One broken path reference |
-| **Step Content Quality** | ✅ EXCELLENT | 9.5/10 | High-quality instructional design |
-| **Documentation** | ✅ EXCELLENT | 9/10 | Comprehensive, minor inconsistencies |
-| **Integration** | ✅ PASS | 9/10 | All paths correct (one issue fixed) |
-| **BMAD Compliance** | ✅ EXCELLENT | 9.5/10 | Strong adherence to standards |
-
-**Overall Score: 9.2/10 - EXCELLENT**
-
-#### ✅ Critical Action Items - ALL RESOLVED
-
-**ONLY ONE TRUE CRITICAL ISSUE EXISTED - NOW FIXED:**
-
-1. **✅ FIXED: Edit Workflow Path**
-   - File: `workflow.md` ✓ RESOLVED
-   - Changed from: `./steps-e/step-e-01-assess-workflow.md`
-   - Changed to: `./steps-e/step-e-01-discovery.md`
-
-**Items incorrectly flagged as critical (actually working as designed):**
-- ✅ Configuration path references (installation-time placeholders)
-- ✅ Planning artifacts folder (installation-time placeholder)
-
-#### High Priority Improvements
-
-2. **⚠️ Split Large Step Files** (>250 lines):
-   - `step-v-09-project-type-validation.md` (263 lines)
-   - `step-v-11-holistic-quality-validation.md` (264 lines)
-   - `step-e-03-edit.md` (253 lines)
-
-3. **⚠️ Update Documentation Inconsistencies**:
-   - Fix step count reference (11 → 12 steps in create mode)
-   - Update edit mode status (Future → Implemented)
-
-#### Medium Priority Enhancements
-
-4. **Enhance PRD Template** (currently minimal at 10 lines)
-5. **Add quick-start README** for new users
-6. **Address step numbering gap** (cosmetic - missing step-11-complete.md)
-
-#### Edit Mode Status - FUNCTIONALLY COMPLETE ✅
-
-The edit workflow is **complete and well-designed** with 5 steps:
-- Discovery → Legacy Conversion (branch) → Review → Edit → Complete
-- Edit mode is inherently simpler than create mode (targeted improvements vs full creation)
-- Uses subprocesses for complex operations
-- Integrates with validation workflow
-
-**No additional steps needed.**
-
-### Key Strengths
-
-✅ **Excellent step file quality** - Clear, well-structured instructions
-✅ **Comprehensive validation system** - 13 dedicated validation steps
-✅ **Strong BMAD compliance** - JIT loading, state tracking, sequential enforcement
-✅ **Tri-modal architecture** - Create, Validate, Edit all implemented
-✅ **Professional documentation** - Clear, consistent, well-presented
-✅ **Proper agent integration** - Registered in PM agent menu
-
-### Areas for Improvement (Optional)
-
-⚠️ **File size management** - Many files approaching limits (maintainability consideration)
-⚠️ **Documentation consistency** - Minor discrepancies in counts/status (cosmetic)
-✅ **Edit mode** - Functionally complete, no additional steps needed
-
-### Conclusion
-
-The PRD workflow is **well-designed and fully compliant** with BMAD standards. The step file architecture is exemplary, the content quality is excellent, and the documentation is comprehensive. The only critical issue (edit workflow path) has been **resolved**, and all other flagged items were actually working as designed (installation-time placeholders).
-
-**Current Status: ✅ PRODUCTION-READY**
-
-**Recommended Optional Enhancements:**
-1. Split the 3 files exceeding 250-line limit (maintainability)
-2. Update documentation inconsistencies (step counts, edit mode status)
-3. Enhance PRD template and add quick-start README (user experience)
-
-The PRD workflow is ready for production use and fully compliant with BMAD workflow standards.
-
----
-
-**Validation Completed:** 2026-01-08
-**Validation Method:** Systematic subprocess analysis with maximum context coverage
-**Validator:** BMAD Workflow Validation System (Wendy - Workflow Building Master)

_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md

@@ -1,150 +0,0 @@
----
-name: prd
-description: PRD tri-modal workflow - Create, Validate, or Edit comprehensive PRDs
-main_config: '{project-root}/_bmad/bmm/config.yaml'
-nextStep: './steps-c/step-01-init.md'
-validateWorkflow: './steps-v/step-v-01-discovery.md'
-editWorkflow: './steps-e/step-e-01-discovery.md'
-web_bundle: true
----
-
-# PRD Workflow (Tri-Modal)
-
-**Goal:** Create, Validate, or Edit comprehensive PRDs through structured workflows.
-
-**Your Role:**
-- **Create Mode:** Product-focused PM facilitator collaborating with an expert peer
-- **Validate Mode:** Validation Architect and Quality Assurance Specialist
-- **Edit Mode:** PRD improvement specialist
-
-You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
-
----
-
-## MODE DETERMINATION
-
-### Detect Workflow Mode
-
-Determine which mode to invoke based on:
-
-1. **Command/Invocation:**
-   - "create prd" or "new prd" → Create mode
-   - "validate prd" or "check prd" → Validate mode
-   - "edit prd" or "improve prd" → Edit mode
-
-2. **Context Detection:**
-   - If invoked with -c flag → Create mode
-   - If invoked with -v flag → Validate mode
-   - If invoked with -e flag → Edit mode
-
-3. **Menu Selection (if unclear):**
-
-If mode cannot be determined from invocation:
-"**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?"
-
-Wait for user selection.
-
-### Route to Appropriate Workflow
-
-**IF Create Mode:**
-"**Create Mode: Creating a new PRD from scratch.**"
-Load, read entire file, then execute: `{nextStep}` (steps-c/step-01-init.md)
-
-**IF Validate Mode:**
-"**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 load, read entire file, and execute: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
-
-**IF Edit Mode:**
-"**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 load, read entire file, and execute: `{editWorkflow}` (steps-e/step-e-01-discovery.md)
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
-- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Mode Determination
-
-**Check if mode was specified in the command invocation:**
-
-- If user invoked with "create prd" or "new prd" or "build prd" or "-c" or "--create" → Set mode to **create**
-- If user invoked with "validate prd" or "review prd" or "check prd" or "-v" or "--validate" → Set mode to **validate**
-- If user invoked with "edit prd" or "modify prd" or "improve prd" or "-e" or "--edit" → Set mode to **edit**
-
-**If mode is still unclear, ask user:**
-
-"**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?"
-
-Wait for user selection.
-
-### 2. Configuration Loading
-
-Load and read full config from {main_config} and resolve:
-
-- `project_name`, `output_folder`, `planning_artifacts`, `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 configured `{communication_language}`.
-
-### 3. Route to Appropriate Workflow
-
-**IF mode == create:**
-"**Create Mode: Creating a new PRD from scratch.**"
-Load, read entire file, then execute `{nextStep}` (steps-c/step-01-init.md)
-
-**IF mode == validate:**
-"**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 load, read entire file, and execute `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
-
-**IF mode == edit:**
-"**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 load, read entire file, and execute `{editWorkflow}` (steps-e/step-e-01-discovery.md)

_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md

@@ -2,15 +2,9 @@
 name: 'step-01-document-discovery'
 description: 'Discover and inventory all project documents, handling duplicates and organizing file structure'
 
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
-
-# File References
-thisStepFile: './step-01-document-discovery.md'
 nextStepFile: './step-02-prd-analysis.md'
-workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
-templateFile: '{workflow_path}/templates/readiness-report-template.md'
+templateFile: '../templates/readiness-report-template.md'
 ---
 
 # Step 1: Document Discovery
@@ -162,7 +156,7 @@ Display: **Select an Option:** [C] Continue to File Validation
 
 #### Menu Handling Logic:
 
-- IF C: Save document inventory to {outputFile}, update frontmatter with completed step and files being included, and only then load read fully and execute {nextStepFile}
+- IF C: Save document inventory to {outputFile}, update frontmatter with completed step and files being included, and then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then redisplay menu
 
 ## CRITICAL STEP COMPLETION NOTE

_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md

@@ -2,13 +2,7 @@
 name: 'step-02-prd-analysis'
 description: 'Read and analyze PRD to extract all FRs and NFRs for coverage validation'
 
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
-
-# File References
-thisStepFile: './step-02-prd-analysis.md'
 nextStepFile: './step-03-epic-coverage-validation.md'
-workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 epicsFile: '{planning_artifacts}/*epic*.md' # Will be resolved to actual file
 ---

_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-03-epic-coverage-validation.md

@@ -2,13 +2,7 @@
 name: 'step-03-epic-coverage-validation'
 description: 'Validate that all PRD FRs are covered in epics and stories'
 
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
-
-# File References
-thisStepFile: './step-03-epic-coverage-validation.md'
 nextStepFile: './step-04-ux-alignment.md'
-workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 ---
 

_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-04-ux-alignment.md

@@ -2,13 +2,7 @@
 name: 'step-04-ux-alignment'
 description: 'Check for UX document and validate alignment with PRD and Architecture'
 
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
-
-# File References
-thisStepFile: './step-04-ux-alignment.md'
 nextStepFile: './step-05-epic-quality-review.md'
-workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 ---
 

_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-05-epic-quality-review.md

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

_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md

@@ -2,12 +2,6 @@
 name: 'step-06-final-assessment'
 description: 'Compile final assessment and polish the readiness report'
 
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
-
-# File References
-thisStepFile: './step-06-final-assessment.md'
-workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 ---
 
@@ -115,6 +109,8 @@ The assessment found [number] issues requiring attention. Review the detailed re
 
 The implementation readiness workflow is now complete. The report contains all findings and recommendations for the user to consider.
 
+Implementation Readiness complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `implementation readiness`.
+
 ---
 
 ## 🚨 SYSTEM SUCCESS/FAILURE METRICS

_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md

@@ -1,7 +1,6 @@
 ---
 name: check-implementation-readiness
 description: 'Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.'
-web_bundle: false
 ---
 
 # Implementation Readiness
@@ -15,7 +14,7 @@ web_bundle: false
 ### Core Principles
 
 - **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
-- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
+- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so
 - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
 - **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
 - **Append-Only Building**: Build documents by appending content as directed to the output file
@@ -27,7 +26,7 @@ web_bundle: false
 3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
 4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
 5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
 
 ### Critical Rules (NO EXCEPTIONS)
 
@@ -52,4 +51,4 @@ Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
 
 ### 2. First Step EXECUTION
 
-Load, read the full file and then execute `./step-01-document-discovery.md` to begin the workflow.
+Read fully and follow: `./step-01-document-discovery.md` to begin the workflow.

_bmad/bmm/workflows/3-solutioning/create-architecture/data/domain-complexity.csv

@@ -8,4 +8,6 @@ productivity,"productivity,workflow,tasks,management,business,tools",medium,stan
 media,"content,media,video,audio,streaming,broadcast",high,advanced,"CDN architecture, video encoding, streaming protocols, content delivery"
 iot,"IoT,sensors,devices,embedded,smart,connected",high,advanced,"device communication, real-time data processing, edge computing, security"
 government,"government,civic,public,admin,policy,regulation",high,enhanced,"accessibility standards, security clearance, data privacy, audit trails"
+process_control,"industrial automation,process control,PLC,SCADA,DCS,HMI,operational technology,control system,cyberphysical,MES,instrumentation,I&C,P&ID",high,advanced,"industrial process control architecture, SCADA system design, OT cybersecurity architecture, real-time control systems"
+building_automation,"building automation,BAS,BMS,HVAC,smart building,fire alarm,fire protection,fire suppression,life safety,elevator,DDC,access control,sequence of operations,commissioning",high,advanced,"building automation architecture, BACnet integration patterns, smart building design, building management system security"
 gaming,"game,gaming,multiplayer,real-time,interactive,entertainment",high,advanced,"real-time multiplayer, game engine architecture, matchmaking, leaderboards"

_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md

@@ -31,8 +31,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -170,7 +170,7 @@ Show the generated content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current context analysis
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current context analysis
 - Process the enhanced architectural insights that come back
 - Ask user: "Accept these enhancements to the project context analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -178,7 +178,7 @@ Show the generated content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project context
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project context
 - Process the collaborative improvements to architectural understanding
 - Ask user: "Accept these changes to the project context analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md

@@ -31,8 +31,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -277,7 +277,7 @@ Show the generated content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current starter analysis
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current starter analysis
 - Process enhanced insights about starter options or custom approaches
 - Ask user: "Accept these changes to the starter template evaluation? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -285,7 +285,7 @@ Show the generated content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with starter evaluation context
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with starter evaluation context
 - Process collaborative insights about starter trade-offs
 - Ask user: "Accept these changes to the starter template evaluation? (y/n)"
 - If yes: Update content, then return to A/P/C menu

_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md

@@ -32,8 +32,8 @@ This step will generate content and present choices for each decision 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -264,7 +264,7 @@ Show the generated decisions content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with specific decision categories
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with specific decision categories
 - Process enhanced insights about particular decisions
 - Ask user: "Accept these enhancements to the architectural decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -272,7 +272,7 @@ Show the generated decisions content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with architectural decisions context
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with architectural decisions context
 - Process collaborative insights about decision trade-offs
 - Ask user: "Accept these changes to the architectural decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu

_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md

@@ -32,8 +32,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -305,7 +305,7 @@ Show the generated patterns content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current patterns
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current patterns
 - Process enhanced consistency rules that come back
 - Ask user: "Accept these additional pattern refinements? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -313,7 +313,7 @@ Show the generated patterns content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with implementation patterns context
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with implementation patterns context
 - Process collaborative insights about potential conflicts
 - Ask user: "Accept these changes to the implementation patterns? (y/n)"
 - If yes: Update content, then return to A/P/C menu

_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md

@@ -32,8 +32,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -325,7 +325,7 @@ Show the generated project structure content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current project structure
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current project structure
 - Process enhanced organizational insights that come back
 - Ask user: "Accept these changes to the project structure? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -333,7 +333,7 @@ Show the generated project structure content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with project structure context
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with project structure context
 - Process collaborative insights about organization trade-offs
 - Ask user: "Accept these changes to the project structure? (y/n)"
 - If yes: Update content, then return to A/P/C menu

_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md

@@ -32,8 +32,8 @@ This step will generate content and present choices:
 
 ## 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/workflow.md
+- When 'A' selected: Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
+- When 'P' selected: Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -299,13 +299,13 @@ Show the validation results and present choices:
 **What would you like to do?**
 [A] Advanced Elicitation - Address any complex architectural concerns
 [P] Party Mode - Review validation from different implementation perspectives
-[C] Continue - Complete the architecture and finish workflow"
+[C] Continue - Complete the architecture and finish workflow
 
 ### 8. Handle Menu Selection
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with validation issues
+- Read fully and follow: {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with validation issues
 - Process enhanced solutions for complex concerns
 - Ask user: "Accept these architectural improvements? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -313,7 +313,7 @@ Show the validation results and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with validation context
+- Read fully and follow: {project-root}/_bmad/core/workflows/party-mode/workflow.md with validation context
 - Process collaborative insights on implementation readiness
 - Ask user: "Accept these changes to the validation results? (y/n)"
 - If yes: Update content, then return to A/P/C menu

_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md

@@ -5,7 +5,6 @@
 - 🛑 NEVER generate content without user input
 
 - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS treat this as collaborative completion between architectural peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on successful workflow completion and implementation handoff
@@ -18,14 +17,7 @@
 - 🎯 Show your analysis before taking any action
 - 🎯 Present completion summary and implementation guidance
 - 📖 Update frontmatter with final workflow state
-- 🚫 NO MORE STEPS - this is the final step
-
-## CONTEXT BOUNDARIES:
-
-- Complete architecture document is finished and validated
-- All architectural decisions, patterns, and structure are documented
-- Focus on successful completion and implementation preparation
-- Provide clear guidance for next steps in the development process
+- 🚫 THIS IS THE FINAL STEP IN THIS WORKFLOW
 
 ## YOUR TASK:
 
@@ -33,75 +25,11 @@ Complete the architecture workflow, provide a comprehensive completion summary,
 
 ## COMPLETION SEQUENCE:
 
-### 1. Present Architecture Completion Summary
+### 1. Congratulate the User on Completion
 
-Based on user skill level, present the completion:
+Both you and the User completed something amazing here - give a summary of what you achieved together and really congratulate the user on a job well done.
 
-**For Expert Users:**
-"Architecture workflow complete. {{decision_count}} architectural decisions documented across {{step_count}} steps.
-
-Your architecture is ready for AI agent implementation. All decisions are documented with specific versions and implementation patterns.
-
-Key deliverables:
-
-- Complete architecture decision document
-- Implementation patterns for agent consistency
-- Project structure with all files and directories
-- Validation confirming coherence and completeness
-
-Ready for implementation phase."
-
-**For Intermediate Users:**
-"Excellent! Your architecture for {{project_name}} is now complete and ready for implementation.
-
-**What we accomplished:**
-
-- Made {{decision_count}} key architectural decisions together
-- Established implementation patterns to ensure consistency
-- Created a complete project structure with {{component_count}} main areas
-- Validated that all your requirements are fully supported
-
-**Your architecture document includes:**
-
-- Technology choices with specific versions
-- Clear implementation patterns for AI agents to follow
-- Complete project directory structure
-- Mapping of your requirements to specific files and folders
-
-The architecture is comprehensive and ready to guide consistent implementation."
-
-**For Beginner Users:**
-"Congratulations! Your architecture for {{project_name}} is complete! 🎉
-
-**What this means:**
-Think of this as creating the complete blueprint for your house. We've made all the important decisions about how it will be built, what materials to use, and how everything fits together.
-
-**What we created together:**
-
-- {{decision_count}} architectural decisions (like choosing the foundation, framing, and systems)
-- Clear rules so that multiple builders (AI agents) all work the same way
-- A complete folder structure showing exactly where every file goes
-- Confirmation that everything you want to build is supported by these decisions
-
-**What happens next:**
-AI agents will read this architecture document before building anything. They'll follow all your decisions exactly, which means your app will be built with consistent patterns throughout.
-
-You're ready for the implementation phase!"
-
-### 2. Review Final Document State
-
-Confirm the architecture document is complete:
-
-**Document Structure Verification:**
-
-- Project Context Analysis ✅
-- Starter Template Evaluation ✅
-- Core Architectural Decisions ✅
-- Implementation Patterns & Consistency Rules ✅
-- Project Structure & Boundaries ✅
-- Architecture Validation Results ✅
-
-**Frontmatter Update:**
+### 2. Update the created document's frontmatter
 
 ```yaml
 stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]
@@ -111,216 +39,12 @@ status: 'complete'
 completedAt: '{{current_date}}'
 ```
 
-### 3. Implementation Guidance
+### 3. Next Steps Guidance
 
-Provide specific next steps for implementation:
+Architecture complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Create Architecture`.
 
-**Immediate Next Steps:**
+Upon Completion of task output: offer to answer any questions about the Architecture Document.
 
-1. **Review the complete architecture document** at `{planning_artifacts}/architecture.md`
-2. **Begin with project initialization** using the starter template command documented
-3. **Create first implementation story** for project setup
-4. **Start implementing user stories** following the architectural decisions
-
-**Development Workflow:**
-"AI agents will:
-
-1. Read the architecture document before implementing each story
-2. Follow your technology choices and patterns exactly
-3. Use the project structure we defined
-4. Maintain consistency across all components"
-
-**Quality Assurance:**
-"Your architecture includes:
-
-- Specific technology versions to use
-- Implementation patterns that prevent conflicts
-- Clear project structure and boundaries
-- Validation that all requirements are supported"
-
-### 4. Generate Completion Content
-
-Prepare the final content to append to the document:
-
-#### Content Structure:
-
-```markdown
-## Architecture Completion Summary
-
-### Workflow Completion
-
-**Architecture Decision Workflow:** COMPLETED ✅
-**Total Steps Completed:** 8
-**Date Completed:** {{current_date}}
-**Document Location:** {planning_artifacts}/architecture.md
-
-### Final Architecture Deliverables
-
-**📋 Complete Architecture Document**
-
-- All architectural decisions documented with specific versions
-- Implementation patterns ensuring AI agent consistency
-- Complete project structure with all files and directories
-- Requirements to architecture mapping
-- Validation confirming coherence and completeness
-
-**🏗️ Implementation Ready Foundation**
-
-- {{decision_count}} architectural decisions made
-- {{pattern_count}} implementation patterns defined
-- {{component_count}} architectural components specified
-- {{requirement_count}} requirements fully supported
-
-**📚 AI Agent Implementation Guide**
-
-- Technology stack with verified versions
-- Consistency rules that prevent implementation conflicts
-- Project structure with clear boundaries
-- Integration patterns and communication standards
-
-### Implementation Handoff
-
-**For AI Agents:**
-This architecture document is your complete guide for implementing {{project_name}}. Follow all decisions, patterns, and structures exactly as documented.
-
-**First Implementation Priority:**
-{{starter_template_command_or_initialization_step}}
-
-**Development Sequence:**
-
-1. Initialize project using documented starter template
-2. Set up development environment per architecture
-3. Implement core architectural foundations
-4. Build features following established patterns
-5. Maintain consistency with documented rules
-
-### Quality Assurance Checklist
-
-**✅ Architecture Coherence**
-
-- [x] All decisions work together without conflicts
-- [x] Technology choices are compatible
-- [x] Patterns support the architectural decisions
-- [x] Structure aligns with all choices
-
-**✅ Requirements Coverage**
-
-- [x] All functional requirements are supported
-- [x] All non-functional requirements are addressed
-- [x] Cross-cutting concerns are handled
-- [x] Integration points are defined
-
-**✅ Implementation Readiness**
-
-- [x] Decisions are specific and actionable
-- [x] Patterns prevent agent conflicts
-- [x] Structure is complete and unambiguous
-- [x] Examples are provided for clarity
-
-### Project Success Factors
-
-**🎯 Clear Decision Framework**
-Every technology choice was made collaboratively with clear rationale, ensuring all stakeholders understand the architectural direction.
-
-**🔧 Consistency Guarantee**
-Implementation patterns and rules ensure that multiple AI agents will produce compatible, consistent code that works together seamlessly.
-
-**📋 Complete Coverage**
-All project requirements are architecturally supported, with clear mapping from business needs to technical implementation.
-
-**🏗️ Solid Foundation**
-The chosen starter template and architectural patterns provide a production-ready foundation following current best practices.
-
----
-
-**Architecture Status:** READY FOR IMPLEMENTATION ✅
-
-**Next Phase:** Begin implementation using the architectural decisions and patterns documented herein.
-
-**Document Maintenance:** Update this architecture when major technical decisions are made during implementation.
-```
-
-### 5. Complete Workflow Finalization
-
-**Save Final Document:**
-
-- Ensure all content is properly appended to `{planning_artifacts}/architecture.md`
-- Update frontmatter with completion status
-- Verify document is complete and coherent
-
-**Workflow Status Update:**
-If not in standalone mode, update workflow status:
-
-- Load `{planning_artifacts}/bmm-workflow-status.yaml`
-- Update workflow_status["create-architecture"] = "{planning_artifacts}/architecture.md"
-- Save file with all structure and comments preserved
-
-### 6. Present Completion to User
-
-"🎉 **Architecture Workflow Complete!**
-
-Your architecture for {{project_name}} is comprehensive, validated, and ready for implementation.
-
-**✅ What's been delivered:**
-
-- Complete architecture document with all decisions and patterns
-- Project structure ready for AI agent implementation
-- Validation confirming everything works together coherently
-- Implementation guidance for the development phase
-
-**📍 Where to find it:**
-`{planning_artifacts}/architecture.md`
-
-**🚀 What's next:**
-
-1. Review your complete architecture document
-2. Begin implementation using the starter template command
-3. Create stories for AI agents to implement following your architectural decisions
-
-Your architecture will ensure consistent, high-quality implementation across all development work. Great job collaborating through these important architectural decisions!
-
-**💡 Optional Enhancement: Project Context File**
-
-Would you like to create a `project-context.md` file? This is a concise, optimized guide for AI agents that captures:
-
-- Critical language and framework rules they might miss
-- Specific patterns and conventions for your project
-- Testing and code quality requirements
-- Anti-patterns and edge cases to avoid
-
-{if_existing_project_context}
-I noticed you already have a project context file. Would you like to update it with your new architectural decisions?
-{else}
-This file helps ensure AI agents implement code consistently with your project's unique requirements and patterns.
-{/if_existing_project_context}
-
-**Create/Update project context?** [Y/N]
-
-**Ready to move to the next phase of your project development?**"
-
-### 7. Handle Project Context Creation Choice
-
-If user responds 'Y' or 'yes' to creating/updating project context:
-
-"Excellent choice! Let me launch the Generate Project Context workflow to create a comprehensive guide for AI agents.
-
-This will help ensure consistent implementation by capturing:
-
-- Language-specific patterns and rules
-- Framework conventions from your architecture
-- Testing and quality standards
-- Anti-patterns to avoid
-
-The workflow will collaborate with you to create an optimized `project-context.md` file that AI agents will read before implementing any code."
-
-**Execute the Generate Project Context workflow:**
-
-- Load and execute: `{project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md`
-- The workflow will handle discovery, generation, and completion of the project context file
-- After completion, return here for final handoff
-
-If user responds 'N' or 'no':
-"Understood! Your architecture is complete and ready for implementation. You can always create a project context file later using the Generate Project Context workflow if needed."
 
 ## SUCCESS METRICS:
 

_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md

@@ -1,7 +1,6 @@
 ---
 name: create-architecture
 description: Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.
-web_bundle: true
 ---
 
 # Architecture Workflow
@@ -45,6 +44,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ## EXECUTION
 
-Load and execute `steps/step-01-init.md` to begin the workflow.
+Read fully and follow: `steps/step-01-init.md` to begin the workflow.
 
 **Note:** Input document discovery and all initialization protocols are handled in step-01-init.md.

_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md

@@ -229,12 +229,12 @@ Display: `**Confirm the Requirements are complete and correct to [C] continue:**
 
 #### Menu Handling Logic:
 
-- IF C: Save all to {outputFile}, update frontmatter, only then load, read entire file, then execute {nextStepFile}
+- IF C: Save all to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#10-present-menu-options)
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN C is selected and all requirements are saved to document and frontmatter is updated, will you then load, read entire file, then execute {nextStepFile} to execute and begin epic design step.
+ONLY WHEN C is selected and all requirements are saved to document and frontmatter is updated, will you then read fully and follow: {nextStepFile} to begin epic design step.
 
 ---
 

_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md

@@ -194,9 +194,9 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
 
 #### Menu Handling Logic:
 
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Save approved epics_list to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask}
+- IF P: Read fully and follow: {partyModeWorkflow}
+- IF C: Save approved epics_list to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-menu-options)
 
 #### EXECUTION RULES:
@@ -208,7 +208,7 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN C is selected and the approved epics_list is saved to document, will you then load, read entire file, then execute {nextStepFile} to execute and begin story creation step.
+ONLY WHEN C is selected and the approved epics_list is saved to document, will you then read fully and follow: {nextStepFile} to begin story creation step.
 
 ---
 

_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md

@@ -231,9 +231,9 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
 
 #### Menu Handling Logic:
 
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Save content to {outputFile}, update frontmatter, then only then load, read entire file, then execute {nextStepFile}
+- IF A: Read fully and follow: {advancedElicitationTask}
+- IF P: Read fully and follow: {partyModeWorkflow}
+- IF C: Save content to {outputFile}, update frontmatter, then read fully and follow: {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-final-menu-options)
 
 #### EXECUTION RULES:
@@ -245,7 +245,7 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN [C continue option] is selected and [all epics and stories saved to document following the template structure exactly], will you then load and read fully `{nextStepFile}` to execute and begin final validation phase.
+ONLY WHEN [C continue option] is selected and [all epics and stories saved to document following the template structure exactly], will you then read fully and follow: `{nextStepFile}` to begin final validation phase.
 
 ---
 

_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md

@@ -143,3 +143,7 @@ If all validations pass:
 **All validations complete!** [C] Complete Workflow
 
 When C is selected, the workflow is complete and the epics.md is ready for development.
+
+Epics and Stories complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Create Epics and Stories`.
+
+Upon Completion of task output: offer to answer any questions about the Epics and Stories.

_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md

@@ -1,7 +1,6 @@
 ---
 name: create-epics-and-stories
 description: 'Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.'
-web_bundle: true
 ---
 
 # Create Epics and Stories
@@ -19,7 +18,7 @@ This uses **step-file architecture** for disciplined execution:
 ### Core Principles
 
 - **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
-- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
+- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so
 - **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
 - **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
 - **Append-Only Building**: Build documents by appending content as directed to the output file
@@ -31,7 +30,7 @@ This uses **step-file architecture** for disciplined execution:
 3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
 4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
 5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
 
 ### Critical Rules (NO EXCEPTIONS)
 
@@ -56,4 +55,4 @@ Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
 
 ### 2. First Step EXECUTION
 
-Load, read the full file and then execute `{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md` to begin the workflow.
+Read fully and follow: `{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md` to begin the workflow.

_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml

@@ -46,5 +46,3 @@ input_file_patterns:
     sharded_index: "{planning_artifacts}/*epic*/index.md"
     sharded_single: "{planning_artifacts}/*epic*/epic-{{epic_num}}.md"
     load_strategy: "SELECTIVE_LOAD"
-
-standalone: true

_bmad/bmm/workflows/4-implementation/correct-course/checklist.md

@@ -253,6 +253,15 @@
 </check-item>
 
 <check-item id="6.4">
+<prompt>Update sprint-status.yaml to reflect approved epic changes</prompt>
+<action>If epics were added: Add new epic entries with status 'backlog'</action>
+<action>If epics were removed: Remove corresponding entries</action>
+<action>If epics were renumbered: Update epic IDs and story references</action>
+<action>If stories were added/removed: Update story entries within affected epics</action>
+<status>[ ] Done / [ ] N/A / [ ] Action-needed</status>
+</check-item>
+
+<check-item id="6.5">
 <prompt>Confirm next steps and handoff plan</prompt>
 <action>Review handoff responsibilities with user</action>
 <action>Ensure all stakeholders understand their roles</action>

_bmad/bmm/workflows/4-implementation/correct-course/instructions.md

@@ -33,7 +33,7 @@
 </step>
 
 <step n="2" goal="Execute Change Analysis Checklist">
-  <action>Load and execute the systematic analysis from: {checklist}</action>
+  <action>Read fully and follow the systematic analysis from: {checklist}</action>
   <action>Work through each checklist section interactively with the user</action>
   <action>Record status for each checklist item:</action>
     - [x] Done - Item completed successfully

_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml

@@ -54,5 +54,3 @@ instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 checklist: "{installed_path}/checklist.md"
 default_output_file: "{planning_artifacts}/sprint-change-proposal-{date}.md"
-
-standalone: true

_bmad/bmm/workflows/4-implementation/create-story/instructions.xml

@@ -336,7 +336,7 @@
       1. Review the comprehensive story in {{story_file}}
       2. Run dev agents `dev-story` for optimized implementation
       3. Run `code-review` when complete (auto-marks done)
-      4. Optional: Run TEA `*automate` after `dev-story` to generate guardrail tests
+      4. Optional: If Test Architect module installed, run `/bmad:tea:automate` after `dev-story` to generate guardrail tests
 
       **The developer now has everything needed for flawless implementation!**
     </output>

_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml

@@ -55,5 +55,3 @@ input_file_patterns:
     whole: "{planning_artifacts}/*epic*.md"
     sharded: "{planning_artifacts}/*epic*/*.md"
     load_strategy: "SELECTIVE_LOAD" # Only load needed epic
-
-standalone: true

_bmad/bmm/workflows/4-implementation/dev-story/instructions.xml

@@ -397,7 +397,7 @@
       - Verify all acceptance criteria are met
       - Ensure deployment readiness if applicable
       - Run `code-review` workflow for peer review
-      - Optional: Run TEA `*automate` to expand guardrail tests
+      - Optional: If Test Architect module installed, run `/bmad:tea:automate` to expand guardrail tests
     </action>
 
     <output>💡 **Tip:** For best results, run `code-review` using a **different** LLM than the one that implemented this story.</output>