Merge 417fc44a98 into 1786d1debc

package-lock.json

@@ -7230,9 +7230,9 @@
       "license": "ISC"
     },
     "node_modules/h3": {
-      "version": "1.15.8",
-      "resolved": "https://registry.npmjs.org/h3/-/h3-1.15.8.tgz",
-      "integrity": "sha512-iOH6Vl8mGd9nNfu9C0IZ+GuOAfJHcyf3VriQxWaSWIB76Fg4BnFuk4cxBxjmQSSxJS664+pgjP6e7VBnUzFfcg==",
+      "version": "1.15.5",
+      "resolved": "https://registry.npmjs.org/h3/-/h3-1.15.5.tgz",
+      "integrity": "sha512-xEyq3rSl+dhGX2Lm0+eFQIAzlDN6Fs0EcC4f7BNUmzaRX/PTzeuM+Tr2lHB8FoXggsQIeXLj8EDVgs5ywxyxmg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {

src/bmm-skills/1-analysis/bmad-create-product-brief/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: bmad-create-product-brief
+description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
+---
+
+Follow the instructions in ./workflow.md.

src/bmm-skills/1-analysis/bmad-create-product-brief/product-brief.template.md

@@ -0,0 +1,10 @@
+---
+stepsCompleted: []
+inputDocuments: []
+date: {{system-date}}
+author: {{user_name}}
+---
+
+# Product Brief: {{project_name}}
+
+<!-- Content will be appended sequentially through collaborative workflow steps -->

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

@@ -0,0 +1,170 @@
+---
+# File References
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+---
+
+# Step 1: Product Brief Initialization
+
+## STEP GOAL:
+
+Initialize the product brief workflow by detecting continuation state and setting up the document structure for collaborative product discovery.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused Business Analyst facilitator
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+- ✅ Maintain collaborative discovery tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on initialization and setup - no content generation yet
+- 🚫 FORBIDDEN to look ahead to future steps or assume knowledge from them
+- 💬 Approach: Systematic setup with clear reporting to user
+- 📋 Detect existing workflow state and handle continuation properly
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking any action
+- 💾 Initialize document structure and update frontmatter appropriately
+- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until user selects 'C' (Continue)
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Variables from workflow.md are available in memory
+- Focus: Workflow initialization and document setup only
+- Limits: Don't assume knowledge from other steps or create content yet
+- Dependencies: Configuration loaded from workflow.md initialization
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Check for Existing Workflow State
+
+First, check if the output document already exists:
+
+**Workflow State Detection:**
+
+- Look for file `{outputFile}`
+- If exists, read the complete file including frontmatter
+- If not exists, this is a fresh workflow
+
+### 2. Handle Continuation (If Document Exists)
+
+If the document exists and has frontmatter with `stepsCompleted`:
+
+**Continuation Protocol:**
+
+- **STOP immediately** and load `./step-01b-continue.md`
+- Do not proceed with any initialization tasks
+- Let step-01b handle all continuation logic
+- This is an auto-proceed situation - no user choice needed
+
+### 3. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Input Document Discovery
+
+load context documents using smart discovery. Documents can be in the following locations:
+- {planning_artifacts}/**
+- {output_folder}/**
+- {product_knowledge}/**
+- {project-root}/docs/**
+
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
+
+Try to discover the following:
+- Brainstorming Reports (`*brainstorming*.md`)
+- Research Documents (`*research*.md`)
+- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
+
+<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
+
+**Loading Rules:**
+
+- Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
+- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
+- index.md is a guide to what's relevant whenever available
+- Track all successfully loaded files in frontmatter `inputDocuments` array
+
+#### B. Create Initial Document
+
+**Document Setup:**
+
+- Copy the template from `../product-brief.template.md` to `{outputFile}`, and update the frontmatter fields
+
+#### C. Present Initialization Results
+
+**Setup Report to User:**
+"Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}.
+
+**Document Setup:**
+
+- Created: `{outputFile}` from template
+- Initialized frontmatter with workflow state
+
+**Input Documents Discovered:**
+
+- Research: {number of research files loaded or "None found"}
+- Brainstorming: {number of brainstorming files loaded or "None found"}
+- Project docs: {number of project files loaded or "None found"}
+- Project Context: {number of project context files loaded or "None found"}
+
+**Files loaded:** {list of specific file names or "No additional documents found"}
+
+Do you have any other documents you'd like me to include, or shall we continue to the next step?"
+
+### 4. Present MENU OPTIONS
+
+Display: "**Proceeding to product vision discovery...**"
+
+#### Menu Handling Logic:
+
+- After setup report is presented, without delay, read fully and follow: ./step-02-vision.md
+
+#### EXECUTION RULES:
+
+- This is an initialization step with auto-proceed after setup completion
+- Proceed directly to next step after document setup and reporting
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then read fully and follow: `./step-02-vision.md` to begin product vision discovery.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Existing workflow detected and properly handed off to step-01b
+- Fresh workflow initialized with template and proper frontmatter
+- Input documents discovered and loaded using sharded-first logic
+- All discovered files tracked in frontmatter `inputDocuments`
+- Menu presented and user input handled correctly
+- Frontmatter updated with `stepsCompleted: [1]` before proceeding
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding with fresh initialization when existing workflow exists
+- Not updating frontmatter with discovered input documents
+- Creating document without proper template structure
+- Not checking sharded folders first before whole files
+- Not reporting discovered documents to user clearly
+- Proceeding without user selecting 'C' (Continue)
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

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

@@ -0,0 +1,158 @@
+---
+# File References
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+---
+
+# Step 1B: Product Brief Continuation
+
+## STEP GOAL:
+
+Resume the product brief workflow from where it was left off, ensuring smooth continuation with full context restoration.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused Business Analyst facilitator
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+- ✅ Maintain collaborative continuation tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on understanding where we left off and continuing appropriately
+- 🚫 FORBIDDEN to modify content completed in previous steps
+- 💬 Approach: Systematic state analysis with clear progress reporting
+- 📋 Resume workflow from exact point where it was interrupted
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking any action
+- 💾 Keep existing frontmatter `stepsCompleted` values
+- 📖 Only load documents that were already tracked in `inputDocuments`
+- 🚫 FORBIDDEN to discover new input documents during continuation
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Current document and frontmatter are already loaded
+- Focus: Workflow state analysis and continuation logic only
+- Limits: Don't assume knowledge beyond what's in the document
+- Dependencies: Existing workflow state from previous session
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Analyze Current State
+
+**State Assessment:**
+Review the frontmatter to understand:
+
+- `stepsCompleted`: Which steps are already done
+- `lastStep`: The most recently completed step number
+- `inputDocuments`: What context was already loaded
+- All other frontmatter variables
+
+### 2. Restore Context Documents
+
+**Context Reloading:**
+
+- For each document in `inputDocuments`, load the complete file
+- This ensures you have full context for continuation
+- Don't discover new documents - only reload what was previously processed
+- Maintain the same context as when workflow was interrupted
+
+### 3. Present Current Progress
+
+**Progress Report to User:**
+"Welcome back {{user_name}}! I'm resuming our product brief collaboration for {{project_name}}.
+
+**Current Progress:**
+
+- Steps completed: {stepsCompleted}
+- Last worked on: Step {lastStep}
+- Context documents available: {len(inputDocuments)} files
+
+**Document Status:**
+
+- Current product brief is ready with all completed sections
+- Ready to continue from where we left off
+
+Does this look right, or do you want to make any adjustments before we proceed?"
+
+### 4. Determine Continuation Path
+
+**Next Step Logic:**
+Based on `lastStep` value, determine which step to load next:
+
+- If `lastStep = 1` → Load `./step-02-vision.md`
+- If `lastStep = 2` → Load `./step-03-users.md`
+- If `lastStep = 3` → Load `./step-04-metrics.md`
+- Continue this pattern for all steps
+- If `lastStep = 6` → Workflow already complete
+
+### 5. Handle Workflow Completion
+
+**If workflow already complete (`lastStep = 6`):**
+"Great news! It looks like we've already completed the product brief workflow for {{project_name}}.
+
+The final document is ready at `{outputFile}` with all sections completed through step 6.
+
+Would you like me to:
+
+- Review the completed product brief with you
+- Suggest next workflow steps (like PRD creation)
+- Start a new product brief revision
+
+What would be most helpful?"
+
+### 6. Present MENU OPTIONS
+
+**If workflow not complete:**
+Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
+
+**Select an Option:** [C] Continue to Step {nextStepNumber}"
+
+#### Menu Handling Logic:
+
+- 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:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- User can chat or ask questions about current progress
+
+## CRITICAL STEP COMPLETION NOTE
+
+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.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- All previous input documents successfully reloaded
+- Current workflow state accurately analyzed and presented
+- User confirms understanding of progress before continuation
+- Correct next step identified and prepared for loading
+- Proper continuation path determined based on `lastStep`
+
+### ❌ SYSTEM FAILURE:
+
+- Discovering new input documents instead of reloading existing ones
+- Modifying content from already completed steps
+- Loading wrong next step based on `lastStep` value
+- Proceeding without user confirmation of current state
+- Not maintaining context consistency from previous session
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

src/bmm-skills/1-analysis/bmad-create-product-brief/steps/step-02-vision.md

@@ -0,0 +1,193 @@
+---
+# File References
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+
+---
+
+# Step 2: Product Vision Discovery
+
+## STEP GOAL:
+
+Conduct comprehensive product vision discovery to define the core problem, solution, and unique value proposition through collaborative analysis.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused Business Analyst facilitator
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+- ✅ Maintain collaborative discovery tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on product vision, problem, and solution discovery
+- 🚫 FORBIDDEN to generate vision without real user input and collaboration
+- 💬 Approach: Systematic discovery from problem to solution
+- 📋 COLLABORATIVE discovery, not assumption-based vision crafting
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- 💾 Generate vision content collaboratively with user
+- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
+- 🚫 FORBIDDEN to proceed without user confirmation through menu
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Current document and frontmatter from step 1, input documents already loaded in memory
+- Focus: This will be the first content section appended to the document
+- Limits: Focus on clear, compelling product vision and problem statement
+- Dependencies: Document initialization from step-01 must be complete
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Begin Vision Discovery
+
+**Opening Conversation:**
+"As your PM peer, I'm excited to help you shape the vision for {{project_name}}. Let's start with the foundation.
+
+**Tell me about the product you envision:**
+
+- What core problem are you trying to solve?
+- Who experiences this problem most acutely?
+- What would success look like for the people you're helping?
+- What excites you most about this solution?
+
+Let's start with the problem space before we get into solutions."
+
+### 2. Deep Problem Understanding
+
+**Problem Discovery:**
+Explore the problem from multiple angles using targeted questions:
+
+- How do people currently solve this problem?
+- What's frustrating about current solutions?
+- What happens if this problem goes unsolved?
+- Who feels this pain most intensely?
+
+### 3. Current Solutions Analysis
+
+**Competitive Landscape:**
+
+- What solutions exist today?
+- Where do they fall short?
+- What gaps are they leaving open?
+- Why haven't existing solutions solved this completely?
+
+### 4. Solution Vision
+
+**Collaborative Solution Crafting:**
+
+- If we could solve this perfectly, what would that look like?
+- What's the simplest way we could make a meaningful difference?
+- What makes your approach different from what's out there?
+- What would make users say 'this is exactly what I needed'?
+
+### 5. Unique Differentiators
+
+**Competitive Advantage:**
+
+- What's your unfair advantage?
+- What would be hard for competitors to copy?
+- What insight or approach is uniquely yours?
+- Why is now the right time for this solution?
+
+### 6. Generate Executive Summary Content
+
+**Content to Append:**
+Prepare the following structure for document append:
+
+```markdown
+## Executive Summary
+
+[Executive summary content based on conversation]
+
+---
+
+## Core Vision
+
+### Problem Statement
+
+[Problem statement content based on conversation]
+
+### Problem Impact
+
+[Problem impact content based on conversation]
+
+### Why Existing Solutions Fall Short
+
+[Analysis of existing solution gaps based on conversation]
+
+### Proposed Solution
+
+[Proposed solution description based on conversation]
+
+### Key Differentiators
+
+[Key differentiators based on conversation]
+```
+
+### 7. Present MENU OPTIONS
+
+**Content Presentation:**
+"I've drafted the executive summary and core vision based on our conversation. This captures the essence of {{project_name}} and what makes it special.
+
+**Here's what I'll add to the document:**
+[Show the complete markdown content from step 6]
+
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Invoke the `bmad-advanced-elicitation` skill with current vision content to dive deeper and refine
+- IF P: Invoke the `bmad-party-mode` skill 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: ./step-03-users.md
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu with updated content
+- User can chat or ask questions - always respond and then end with display again of the menu options
+
+## 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 read fully and follow: `./step-03-users.md` to begin target user discovery.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Clear problem statement that resonates with target users
+- Compelling solution vision that addresses the core problem
+- Unique differentiators that provide competitive advantage
+- Executive summary that captures the product essence
+- A/P/C menu presented and handled correctly with proper task execution
+- Content properly appended to document when C selected
+- Frontmatter updated with stepsCompleted: [1, 2]
+
+### ❌ SYSTEM FAILURE:
+
+- Accepting vague problem statements without pushing for specificity
+- Creating solution vision without fully understanding the problem
+- Missing unique differentiators or competitive insights
+- Generating vision without real user input and collaboration
+- Not presenting standard A/P/C menu after content generation
+- Appending content without user selecting 'C'
+- Not updating frontmatter properly
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

src/bmm-skills/1-analysis/bmad-create-product-brief/steps/step-03-users.md

@@ -0,0 +1,196 @@
+---
+# File References
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+
+---
+
+# Step 3: Target Users Discovery
+
+## STEP GOAL:
+
+Define target users with rich personas and map their key interactions with the product through collaborative user research and journey mapping.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused Business Analyst facilitator
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+- ✅ Maintain collaborative discovery tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on defining who this product serves and how they interact with it
+- 🚫 FORBIDDEN to create generic user profiles without specific details
+- 💬 Approach: Systematic persona development with journey mapping
+- 📋 COLLABORATIVE persona development, not assumption-based user creation
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- 💾 Generate user personas and journeys collaboratively with user
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+- 🚫 FORBIDDEN to proceed without user confirmation through menu
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Current document and frontmatter from previous steps, product vision and problem already defined
+- Focus: Creating vivid, actionable user personas that align with product vision
+- Limits: Focus on users who directly experience the problem or benefit from the solution
+- Dependencies: Product vision and problem statement from step-02 must be complete
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Begin User Discovery
+
+**Opening Exploration:**
+"Now that we understand what {{project_name}} does, let's define who it's for.
+
+**User Discovery:**
+
+- Who experiences the problem we're solving?
+- Are there different types of users with different needs?
+- Who gets the most value from this solution?
+- Are there primary users and secondary users we should consider?
+
+Let's start by identifying the main user groups."
+
+### 2. Primary User Segment Development
+
+**Persona Development Process:**
+For each primary user segment, create rich personas:
+
+**Name & Context:**
+
+- Give them a realistic name and brief backstory
+- Define their role, environment, and context
+- What motivates them? What are their goals?
+
+**Problem Experience:**
+
+- How do they currently experience the problem?
+- What workarounds are they using?
+- What are the emotional and practical impacts?
+
+**Success Vision:**
+
+- What would success look like for them?
+- What would make them say "this is exactly what I needed"?
+
+**Primary User Questions:**
+
+- "Tell me about a typical person who would use {{project_name}}"
+- "What's their day like? Where does our product fit in?"
+- "What are they trying to accomplish that's hard right now?"
+
+### 3. Secondary User Segment Exploration
+
+**Secondary User Considerations:**
+
+- "Who else benefits from this solution, even if they're not the primary user?"
+- "Are there admin, support, or oversight roles we should consider?"
+- "Who influences the decision to adopt or purchase this product?"
+- "Are there partner or stakeholder users who matter?"
+
+### 4. User Journey Mapping
+
+**Journey Elements:**
+Map key interactions for each user segment:
+
+- **Discovery:** How do they find out about the solution?
+- **Onboarding:** What's their first experience like?
+- **Core Usage:** How do they use the product day-to-day?
+- **Success Moment:** When do they realize the value?
+- **Long-term:** How does it become part of their routine?
+
+**Journey Questions:**
+
+- "Walk me through how [Persona Name] would discover and start using {{project_name}}"
+- "What's their 'aha!' moment?"
+- "How does this product change how they work or live?"
+
+### 5. Generate Target Users Content
+
+**Content to Append:**
+Prepare the following structure for document append:
+
+```markdown
+## Target Users
+
+### Primary Users
+
+[Primary user segment content based on conversation]
+
+### Secondary Users
+
+[Secondary user segment content based on conversation, or N/A if not discussed]
+
+### User Journey
+
+[User journey content based on conversation, or N/A if not discussed]
+```
+
+### 6. Present MENU OPTIONS
+
+**Content Presentation:**
+"I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
+
+**Here's what I'll add to the document:**
+[Show the complete markdown content from step 5]
+
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Invoke the `bmad-advanced-elicitation` skill with current user content to dive deeper into personas and journeys
+- IF P: Invoke the `bmad-party-mode` skill 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: ./step-04-metrics.md
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu with updated content
+- User can chat or ask questions - always respond and then end with display again of the menu options
+
+## 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 read fully and follow: `./step-04-metrics.md` to begin success metrics definition.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Rich, believable user personas with clear motivations
+- Clear distinction between primary and secondary users
+- User journeys that show key interaction points and value creation
+- User segments that align with product vision and problem statement
+- A/P/C menu presented and handled correctly with proper task execution
+- Content properly appended to document when C selected
+- Frontmatter updated with stepsCompleted: [1, 2, 3]
+
+### ❌ SYSTEM FAILURE:
+
+- Creating generic user profiles without specific details
+- Missing key user segments that are important to success
+- User journeys that don't show how the product creates value
+- Not connecting user needs back to the problem statement
+- Not presenting standard A/P/C menu after content generation
+- Appending content without user selecting 'C'
+- Not updating frontmatter properly
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

src/bmm-skills/1-analysis/bmad-create-product-brief/steps/step-04-metrics.md

@@ -0,0 +1,199 @@
+---
+# File References
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+
+---
+
+# Step 4: Success Metrics Definition
+
+## STEP GOAL:
+
+Define comprehensive success metrics that include user success, business objectives, and key performance indicators through collaborative metric definition aligned with product vision and user value.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused Business Analyst facilitator
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+- ✅ Maintain collaborative discovery tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on defining measurable success criteria and business objectives
+- 🚫 FORBIDDEN to create vague metrics that can't be measured or tracked
+- 💬 Approach: Systematic metric definition that connects user value to business success
+- 📋 COLLABORATIVE metric definition that drives actionable decisions
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- 💾 Generate success metrics collaboratively with user
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
+- 🚫 FORBIDDEN to proceed without user confirmation through menu
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Current document and frontmatter from previous steps, product vision and target users already defined
+- Focus: Creating measurable, actionable success criteria that align with product strategy
+- Limits: Focus on metrics that drive decisions and demonstrate real value creation
+- Dependencies: Product vision and user personas from previous steps must be complete
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Begin Success Metrics Discovery
+
+**Opening Exploration:**
+"Now that we know who {{project_name}} serves and what problem it solves, let's define what success looks like.
+
+**Success Discovery:**
+
+- How will we know we're succeeding for our users?
+- What would make users say 'this was worth it'?
+- What metrics show we're creating real value?
+
+Let's start with the user perspective."
+
+### 2. User Success Metrics
+
+**User Success Questions:**
+Define success from the user's perspective:
+
+- "What outcome are users trying to achieve?"
+- "How will they know the product is working for them?"
+- "What's the moment where they realize this is solving their problem?"
+- "What behaviors indicate users are getting value?"
+
+**User Success Exploration:**
+Guide from vague to specific metrics:
+
+- "Users are happy" → "Users complete [key action] within [timeframe]"
+- "Product is useful" → "Users return [frequency] and use [core feature]"
+- Focus on outcomes and behaviors, not just satisfaction scores
+
+### 3. Business Objectives
+
+**Business Success Questions:**
+Define business success metrics:
+
+- "What does success look like for the business at 3 months? 12 months?"
+- "Are we measuring revenue, user growth, engagement, something else?"
+- "What business metrics would make you say 'this is working'?"
+- "How does this product contribute to broader company goals?"
+
+**Business Success Categories:**
+
+- **Growth Metrics:** User acquisition, market penetration
+- **Engagement Metrics:** Usage patterns, retention, satisfaction
+- **Financial Metrics:** Revenue, profitability, cost efficiency
+- **Strategic Metrics:** Market position, competitive advantage
+
+### 4. Key Performance Indicators
+
+**KPI Development Process:**
+Define specific, measurable KPIs:
+
+- Transform objectives into measurable indicators
+- Ensure each KPI has a clear measurement method
+- Define targets and timeframes where appropriate
+- Include leading indicators that predict success
+
+**KPI Examples:**
+
+- User acquisition: "X new users per month"
+- Engagement: "Y% of users complete core journey weekly"
+- Business impact: "$Z in cost savings or revenue generation"
+
+### 5. Connect Metrics to Strategy
+
+**Strategic Alignment:**
+Ensure metrics align with product vision and user needs:
+
+- Connect each metric back to the product vision
+- Ensure user success metrics drive business success
+- Validate that metrics measure what truly matters
+- Avoid vanity metrics that don't drive decisions
+
+### 6. Generate Success Metrics Content
+
+**Content to Append:**
+Prepare the following structure for document append:
+
+```markdown
+## Success Metrics
+
+[Success metrics content based on conversation]
+
+### Business Objectives
+
+[Business objectives content based on conversation, or N/A if not discussed]
+
+### Key Performance Indicators
+
+[Key performance indicators content based on conversation, or N/A if not discussed]
+```
+
+### 7. Present MENU OPTIONS
+
+**Content Presentation:**
+"I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
+
+**Here's what I'll add to the document:**
+[Show the complete markdown content from step 6]
+
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Invoke the `bmad-advanced-elicitation` skill with current metrics content to dive deeper into success metric insights
+- IF P: Invoke the `bmad-party-mode` skill 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: ./step-05-scope.md
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu with updated content
+- User can chat or ask questions - always respond and then end with display again of the menu options
+
+## 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 read fully and follow: `./step-05-scope.md` to begin MVP scope definition.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- User success metrics that focus on outcomes and behaviors
+- Clear business objectives aligned with product strategy
+- Specific, measurable KPIs with defined targets and timeframes
+- Metrics that connect user value to business success
+- A/P/C menu presented and handled correctly with proper task execution
+- Content properly appended to document when C selected
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4]
+
+### ❌ SYSTEM FAILURE:
+
+- Vague success metrics that can't be measured or tracked
+- Business objectives disconnected from user success
+- Too many metrics or missing critical success indicators
+- Metrics that don't drive actionable decisions
+- Not presenting standard A/P/C menu after content generation
+- Appending content without user selecting 'C'
+- Not updating frontmatter properly
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

src/bmm-skills/1-analysis/bmad-create-product-brief/steps/step-05-scope.md

@@ -0,0 +1,213 @@
+---
+# File References
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+
+---
+
+# Step 5: MVP Scope Definition
+
+## STEP GOAL:
+
+Define MVP scope with clear boundaries and outline future vision through collaborative scope negotiation that balances ambition with realism.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused Business Analyst facilitator
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+- ✅ Maintain collaborative discovery tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on defining minimum viable scope and future vision
+- 🚫 FORBIDDEN to create MVP scope that's too large or includes non-essential features
+- 💬 Approach: Systematic scope negotiation with clear boundary setting
+- 📋 COLLABORATIVE scope definition that prevents scope creep
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- 💾 Generate MVP scope collaboratively with user
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step
+- 🚫 FORBIDDEN to proceed without user confirmation through menu
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Current document and frontmatter from previous steps, product vision, users, and success metrics already defined
+- Focus: Defining what's essential for MVP vs. future enhancements
+- Limits: Balance user needs with implementation feasibility
+- Dependencies: Product vision, user personas, and success metrics from previous steps must be complete
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Begin Scope Definition
+
+**Opening Exploration:**
+"Now that we understand what {{project_name}} does, who it serves, and how we'll measure success, let's define what we need to build first.
+
+**Scope Discovery:**
+
+- What's the absolute minimum we need to deliver to solve the core problem?
+- What features would make users say 'this solves my problem'?
+- How do we balance ambition with getting something valuable to users quickly?
+
+Let's start with the MVP mindset: what's the smallest version that creates real value?"
+
+### 2. MVP Core Features Definition
+
+**MVP Feature Questions:**
+Define essential features for minimum viable product:
+
+- "What's the core functionality that must work?"
+- "Which features directly address the main problem we're solving?"
+- "What would users consider 'incomplete' if it was missing?"
+- "What features create the 'aha!' moment we discussed earlier?"
+
+**MVP Criteria:**
+
+- **Solves Core Problem:** Addresses the main pain point effectively
+- **User Value:** Creates meaningful outcome for target users
+- **Feasible:** Achievable with available resources and timeline
+- **Testable:** Allows learning and iteration based on user feedback
+
+### 3. Out of Scope Boundaries
+
+**Out of Scope Exploration:**
+Define what explicitly won't be in MVP:
+
+- "What features would be nice to have but aren't essential?"
+- "What functionality could wait for version 2.0?"
+- "What are we intentionally saying 'no' to for now?"
+- "How do we communicate these boundaries to stakeholders?"
+
+**Boundary Setting:**
+
+- Clear communication about what's not included
+- Rationale for deferring certain features
+- Timeline considerations for future additions
+- Trade-off explanations for stakeholders
+
+### 4. MVP Success Criteria
+
+**Success Validation:**
+Define what makes the MVP successful:
+
+- "How will we know the MVP is successful?"
+- "What metrics will indicate we should proceed beyond MVP?"
+- "What user feedback signals validate our approach?"
+- "What's the decision point for scaling beyond MVP?"
+
+**Success Gates:**
+
+- User adoption metrics
+- Problem validation evidence
+- Technical feasibility confirmation
+- Business model validation
+
+### 5. Future Vision Exploration
+
+**Vision Questions:**
+Define the longer-term product vision:
+
+- "If this is wildly successful, what does it become in 2-3 years?"
+- "What capabilities would we add with more resources?"
+- "How does the MVP evolve into the full product vision?"
+- "What markets or user segments could we expand to?"
+
+**Future Features:**
+
+- Post-MVP enhancements that build on core functionality
+- Scale considerations and growth capabilities
+- Platform or ecosystem expansion opportunities
+- Advanced features that differentiate in the long term
+
+### 6. Generate MVP Scope Content
+
+**Content to Append:**
+Prepare the following structure for document append:
+
+```markdown
+## MVP Scope
+
+### Core Features
+
+[Core features content based on conversation]
+
+### Out of Scope for MVP
+
+[Out of scope content based on conversation, or N/A if not discussed]
+
+### MVP Success Criteria
+
+[MVP success criteria content based on conversation, or N/A if not discussed]
+
+### Future Vision
+
+[Future vision content based on conversation, or N/A if not discussed]
+```
+
+### 7. Present MENU OPTIONS
+
+**Content Presentation:**
+"I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
+
+**Here's what I'll add to the document:**
+[Show the complete markdown content from step 6]
+
+**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Invoke the `bmad-advanced-elicitation` skill with current scope content to optimize scope definition
+- IF P: Invoke the `bmad-party-mode` skill 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: ./step-06-complete.md
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu with updated content
+- User can chat or ask questions - always respond and then end with display again of the menu options
+
+## 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 read fully and follow: `./step-06-complete.md` to complete the product brief workflow.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- MVP features that solve the core problem effectively
+- Clear out-of-scope boundaries that prevent scope creep
+- Success criteria that validate MVP approach and inform go/no-go decisions
+- Future vision that inspires while maintaining focus on MVP
+- A/P/C menu presented and handled correctly with proper task execution
+- Content properly appended to document when C selected
+- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5]
+
+### ❌ SYSTEM FAILURE:
+
+- MVP scope too large or includes non-essential features
+- Missing clear boundaries leading to scope creep
+- No success criteria to validate MVP approach
+- Future vision disconnected from MVP foundation
+- Not presenting standard A/P/C menu after content generation
+- Appending content without user selecting 'C'
+- Not updating frontmatter properly
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

src/bmm-skills/1-analysis/bmad-create-product-brief/steps/step-06-complete.md

@@ -0,0 +1,159 @@
+---
+# File References
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+---
+
+# Step 6: Product Brief Completion
+
+## STEP GOAL:
+
+Complete the product brief workflow, update status files, and provide guidance on logical next steps for continued product development.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused Business Analyst facilitator
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+- ✅ Maintain collaborative completion tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on completion, next steps, and project guidance
+- 🚫 FORBIDDEN to generate new content for the product brief
+- 💬 Approach: Systematic completion with quality validation and next step recommendations
+- 📋 FINALIZE document and update workflow status appropriately
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- 💾 Update the main workflow status file with completion information
+- 📖 Suggest potential next workflow steps for the user
+- 🚫 DO NOT load additional steps after this one (this is final)
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Complete product brief document from all previous steps, workflow frontmatter shows all completed steps
+- Focus: Completion validation, status updates, and next step guidance
+- Limits: No new content generation, only completion and wrap-up activities
+- Dependencies: All previous steps must be completed with content saved to document
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Announce Workflow Completion
+
+**Completion Announcement:**
+"🎉 **Product Brief Complete, {{user_name}}!**
+
+I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
+
+**What we've accomplished:**
+
+- ✅ Executive Summary with clear vision and problem statement
+- ✅ Core Vision with solution definition and unique differentiators
+- ✅ Target Users with rich personas and user journeys
+- ✅ Success Metrics with measurable outcomes and business objectives
+- ✅ MVP Scope with focused feature set and clear boundaries
+- ✅ Future Vision that inspires while maintaining current focus
+
+**The complete Product Brief is now available at:** `{outputFile}`
+
+This brief serves as the foundation for all subsequent product development activities and strategic decisions."
+
+### 2. Document Quality Check
+
+**Completeness Validation:**
+Perform final validation of the product brief:
+
+- Does the executive summary clearly communicate the vision and problem?
+- Are target users well-defined with compelling personas?
+- Do success metrics connect user value to business objectives?
+- Is MVP scope focused and realistic?
+- Does the brief provide clear direction for next steps?
+
+**Consistency Validation:**
+
+- Do all sections align with the core problem statement?
+- Is user value consistently emphasized throughout?
+- Are success criteria traceable to user needs and business goals?
+- Does MVP scope align with the problem and solution?
+
+### 3. Suggest Next Steps
+
+**Recommended Next Workflow:**
+Provide guidance on logical next workflows:
+
+1. `create-prd` - Create detailed Product Requirements Document
+   - Brief provides foundation for detailed requirements
+   - User personas inform journey mapping
+   - Success metrics become specific acceptance criteria
+   - MVP scope becomes detailed feature specifications
+
+**Other Potential Next Steps:**
+
+1. `create-ux-design` - UX research and design (can run parallel with PRD)
+2. `domain-research` - Deep market or domain research (if needed)
+
+**Strategic Considerations:**
+
+- The PRD workflow builds directly on this brief for detailed planning
+- Consider team capacity and immediate priorities
+- Use brief to validate concept before committing to detailed work
+- Brief can guide early technical feasibility discussions
+
+### 4. Congrats to the user
+
+"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**"
+
+Recap that the brief captures everything needed to guide subsequent product development:
+
+- Clear vision and problem definition
+- Deep understanding of target users
+- Measurable success criteria
+- Focused MVP scope with realistic boundaries
+- Inspiring long-term vision
+
+### 5. Suggest next steps
+
+Product Brief complete. Invoke the `bmad-help` skill.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Product brief contains all essential sections with collaborative content
+- All collaborative content properly saved to document with proper frontmatter
+- Workflow status file updated with completion information and timestamp
+- Clear next step guidance provided to user with specific workflow recommendations
+- Document quality validation completed with completeness and consistency checks
+- User acknowledges completion and understands next available options
+- Workflow properly marked as complete in status tracking
+
+### ❌ SYSTEM FAILURE:
+
+- Not updating workflow status file with completion information
+- Missing clear next step guidance for user
+- Not confirming document completeness with user
+- Workflow not properly marked as complete in status tracking
+- User unclear about what happens next or available options
+- Document quality issues not identified or addressed
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+## FINAL WORKFLOW COMPLETION
+
+This product brief is now complete and serves as the strategic foundation for the entire product lifecycle. All subsequent design, architecture, and development work should trace back to the vision, user needs, and success criteria documented in this brief.
+
+**Congratulations on completing the Product Brief for {{project_name}}!** 🎉

src/bmm-skills/1-analysis/bmad-create-product-brief/workflow.md

@@ -0,0 +1,55 @@
+# Product Brief Workflow
+
+**Goal:** Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a product-focused Business Analyst collaborating with an expert peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision. Work together as equals.
+
+---
+
+## 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 {project-root}/_bmad/bmm/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
+
+✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
+
+### 2. First Step EXECUTION
+
+Read fully and follow: `./steps/step-01-init.md` to begin the workflow.

src/bmm-skills/1-analysis/bmad-product-brief-preview/SKILL.md

@@ -1,6 +1,7 @@
 ---
-name: bmad-product-brief
-description: Create or update product briefs through guided or autonomous discovery. Use when the user requests to create or update a Product Brief.
+name: bmad-product-brief-preview
+description: Create or update product briefs through guided or autonomous discovery. Use when the user requests to 'create a product brief', 'help me create a project brief', or 'update my product brief'.
+argument-hint: "[optional --create, --edit, --optimize, --distillate, --inputs, --headless] [brief idea]"
 ---
 
 # Create Product Brief

src/bmm-skills/1-analysis/bmad-product-brief-preview/bmad-skill-manifest.yaml

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

src/bmm-skills/1-analysis/research/bmad-domain-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-domain-research
-description: 'Conduct domain and industry research. Use when the user says wants to do domain research for a topic or industry'
+description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
 ---
 
 Follow the instructions in ./workflow.md.

src/bmm-skills/1-analysis/research/bmad-market-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-market-research
-description: 'Conduct market research on competition and customers. Use when the user says they need market research'
+description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".'
 ---
 
 Follow the instructions in ./workflow.md.

src/bmm-skills/1-analysis/research/bmad-technical-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bmad-technical-research
-description: 'Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report'
+description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
 ---
 
 Follow the instructions in ./workflow.md.

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

@@ -0,0 +1,182 @@
+# Market Research Step 1: Market Research Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate research content in init step
+- ✅ ALWAYS confirm understanding of user's research goals
+- 📋 YOU ARE A MARKET RESEARCH FACILITATOR, not content generator
+- 💬 FOCUS on clarifying scope and approach
+- 🔍 NO WEB RESEARCH in init - that's for later steps
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Confirm research understanding before proceeding
+- ⚠️ Present [C] continue option after scope clarification
+- 💾 Write initial scope document immediately
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from main workflow discovery are available
+- Research type = "market" is already set
+- **Research topic = "{{research_topic}}"** - discovered from initial discussion
+- **Research goals = "{{research_goals}}"** - captured from initial discussion
+- Focus on market research scope clarification
+- Web search capabilities are enabled for later steps
+
+## YOUR TASK:
+
+Initialize market research by confirming understanding of {{research_topic}} and establishing clear research scope.
+
+## MARKET RESEARCH INITIALIZATION:
+
+### 1. Confirm Research Understanding
+
+**INITIALIZE - DO NOT RESEARCH YET**
+
+Start with research confirmation:
+"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
+
+**My Understanding of Your Research Needs:**
+
+- **Research Topic**: {{research_topic}}
+- **Research Goals**: {{research_goals}}
+- **Research Type**: Market Research
+- **Approach**: Comprehensive market analysis with source verification
+
+**Market Research Areas We'll Cover:**
+
+- Market size, growth dynamics, and trends
+- Customer insights and behavior analysis
+- Competitive landscape and positioning
+- Strategic recommendations and implementation guidance
+
+**Does this accurately capture what you're looking for?**"
+
+### 2. Refine Research Scope
+
+Gather any clarifications needed:
+
+#### Scope Clarification Questions:
+
+- "Are there specific customer segments or aspects of {{research_topic}} we should prioritize?"
+- "Should we focus on specific geographic regions or global market?"
+- "Is this for market entry, expansion, product development, or other business purpose?"
+- "Any competitors or market segments you specifically want us to analyze?"
+
+### 3. Document Initial Scope
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Write initial research scope to document:
+
+```markdown
+# Market Research: {{research_topic}}
+
+## Research Initialization
+
+### Research Understanding Confirmed
+
+**Topic**: {{research_topic}}
+**Goals**: {{research_goals}}
+**Research Type**: Market Research
+**Date**: {{date}}
+
+### Research Scope
+
+**Market Analysis Focus Areas:**
+
+- Market size, growth projections, and dynamics
+- Customer segments, behavior patterns, and insights
+- Competitive landscape and positioning analysis
+- Strategic recommendations and implementation guidance
+
+**Research Methodology:**
+
+- Current web data with source verification
+- Multiple independent sources for critical claims
+- Confidence level assessment for uncertain data
+- Comprehensive coverage with no critical gaps
+
+### Next Steps
+
+**Research Workflow:**
+
+1. ✅ Initialization and scope setting (current step)
+2. Customer Insights and Behavior Analysis
+3. Competitive Landscape Analysis
+4. Strategic Synthesis and Recommendations
+
+**Research Status**: Scope confirmed, ready to proceed with detailed market analysis
+```
+
+### 4. Present Confirmation and Continue Option
+
+Show initial scope document and present continue option:
+"I've documented our understanding and initial scope for **{{research_topic}}** market research.
+
+**What I've established:**
+
+- Research topic and goals confirmed
+- Market analysis focus areas defined
+- Research methodology verification
+- Clear workflow progression
+
+**Document Status:** Initial scope written to research file for your review
+
+**Ready to begin detailed market research?**
+[C] Continue - Confirm scope and proceed to customer insights analysis
+[Modify] Suggest changes to research scope before proceeding
+
+### 5. Handle User Response
+
+#### If 'C' (Continue):
+
+- Update frontmatter: `stepsCompleted: [1]`
+- Add confirmation note to document: "Scope confirmed by user on {{date}}"
+- Load: `{project-root}/_bmad/bmm-skills/1-analysis/research/market-steps/step-02-customer-behavior.md`
+
+#### If 'Modify':
+
+- Gather user changes to scope
+- Update document with modifications
+- Re-present updated scope for confirmation
+
+## SUCCESS METRICS:
+
+✅ Research topic and goals accurately understood
+✅ Market research scope clearly defined
+✅ Initial scope document written immediately
+✅ User opportunity to review and modify scope
+✅ [C] continue option presented and handled correctly
+✅ Document properly updated with scope confirmation
+
+## FAILURE MODES:
+
+❌ Not confirming understanding of research topic and goals
+❌ Generating research content instead of just scope clarification
+❌ Not writing initial scope document to file
+❌ Not providing opportunity for user to modify scope
+❌ Proceeding to next step without user confirmation
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research 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
+
+## INITIALIZATION PRINCIPLES:
+
+This step ensures:
+
+- Clear mutual understanding of research objectives
+- Well-defined research scope and approach
+- Immediate documentation for user review
+- User control over research direction before detailed work begins
+
+## NEXT STEP:
+
+After user confirmation and scope finalization, load `{project-root}/_bmad/bmm-skills/1-analysis/research/market-steps/step-02-customer-behavior.md` to begin detailed market research with customer insights analysis.
+
+Remember: Init steps confirm understanding and scope, not generate research content!

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

@@ -0,0 +1,237 @@
+# Market Research Step 2: Customer Behavior and Segments
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ Search the web to verify and supplement your knowledge with current facts
+- 📋 YOU ARE A CUSTOMER BEHAVIOR ANALYST, not content generator
+- 💬 FOCUS on customer behavior patterns and demographic analysis
+- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ 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 behavior content generation
+- 📝 WRITE CUSTOMER BEHAVIOR ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed 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 patterns and demographic analysis
+- Web search capabilities with source verification are enabled
+- Previous step confirmed research scope and goals
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+
+## YOUR TASK:
+
+Conduct customer behavior and segment analysis with emphasis on patterns and demographics.
+
+## CUSTOMER BEHAVIOR ANALYSIS SEQUENCE:
+
+### 1. Begin Customer Behavior Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly.
+
+Start with customer behavior research approach:
+"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns.
+
+**Customer Behavior Focus:**
+
+- Customer behavior patterns and preferences
+- Demographic profiles and segmentation
+- Psychographic characteristics and values
+- Behavior drivers and influences
+- Customer interaction patterns and engagement
+
+**Let me search for current customer behavior insights.**"
+
+### 2. Parallel Customer Behavior Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+Search the web: "{{research_topic}} customer behavior patterns"
+Search the web: "{{research_topic}} customer demographics"
+Search the web: "{{research_topic}} psychographic profiles"
+Search the web: "{{research_topic}} customer behavior drivers"
+
+**Analysis approach:**
+
+- Look for customer behavior studies and research reports
+- Search for demographic segmentation and analysis
+- Research psychographic profiling and value systems
+- Analyze behavior drivers and influencing factors
+- Study customer interaction and engagement patterns
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
+
+**Research Coverage:**
+
+- Customer behavior patterns and preferences
+- Demographic profiles and segmentation
+- Psychographic characteristics and values
+- Behavior drivers and influences
+- Customer interaction patterns and engagement
+
+**Cross-Behavior Analysis:**
+[Identify patterns connecting demographics, psychographics, and behaviors]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Customer Behavior Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare customer behavior analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Behavior and Segments
+
+### Customer Behavior Patterns
+
+[Customer behavior patterns analysis with source citations]
+_Behavior Drivers: [Key motivations and patterns from web search]_
+_Interaction Preferences: [Customer engagement and interaction patterns]_
+_Decision Habits: [How customers typically make decisions]_
+_Source: [URL]_
+
+### Demographic Segmentation
+
+[Demographic analysis with source citations]
+_Age Demographics: [Age groups and preferences]_
+_Income Levels: [Income segments and purchasing behavior]_
+_Geographic Distribution: [Regional/city differences]_
+_Education Levels: [Education impact on behavior]_
+_Source: [URL]_
+
+### Psychographic Profiles
+
+[Psychographic analysis with source citations]
+_Values and Beliefs: [Core values driving customer behavior]_
+_Lifestyle Preferences: [Lifestyle choices and behaviors]_
+_Attitudes and Opinions: [Customer attitudes toward products/services]_
+_Personality Traits: [Personality influences on behavior]_
+_Source: [URL]_
+
+### Customer Segment Profiles
+
+[Detailed customer segment profiles with source citations]
+_Segment 1: [Detailed profile including demographics, psychographics, behavior]_
+_Segment 2: [Detailed profile including demographics, psychographics, behavior]_
+_Segment 3: [Detailed profile including demographics, psychographics, behavior]_
+_Source: [URL]_
+
+### Behavior Drivers and Influences
+
+[Behavior drivers analysis with source citations]
+_Emotional Drivers: [Emotional factors influencing behavior]_
+_Rational Drivers: [Logical decision factors]_
+_Social Influences: [Social and peer influences]_
+_Economic Influences: [Economic factors affecting behavior]_
+_Source: [URL]_
+
+### Customer Interaction Patterns
+
+[Customer interaction analysis with source citations]
+_Research and Discovery: [How customers find and research options]_
+_Purchase Decision Process: [Steps in purchase decision making]_
+_Post-Purchase Behavior: [After-purchase engagement patterns]_
+_Loyalty and Retention: [Factors driving customer loyalty]_
+_Source: [URL]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
+
+**Key Customer Behavior Findings:**
+
+- Customer behavior patterns clearly identified with drivers
+- Demographic segmentation thoroughly analyzed
+- Psychographic profiles mapped and documented
+- Customer interaction patterns captured
+- Multiple sources verified for critical insights
+
+**Ready to proceed to customer pain points?**
+[C] Continue - Save this to document and proceed to pain points analysis
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load: `{project-root}/_bmad/bmm-skills/1-analysis/research/market-steps/step-03-customer-pain-points.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Customer behavior patterns identified with current citations
+✅ Demographic segmentation thoroughly analyzed
+✅ Psychographic profiles clearly documented
+✅ Customer interaction patterns captured
+✅ Multiple sources verified for critical insights
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (customer pain points)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Relying solely on training data without web verification for current facts
+
+❌ Missing critical customer behavior patterns
+❌ Incomplete demographic segmentation analysis
+❌ Missing psychographic profile documentation
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to customer pain points analysis step
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research 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 BEHAVIOR RESEARCH PROTOCOLS:
+
+- Research customer behavior studies and market research
+- Use demographic data from authoritative sources
+- Research psychographic profiling and value systems
+- Analyze customer interaction and engagement patterns
+- Focus on current behavior data and trends
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## BEHAVIOR ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative customer research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable customer insights
+
+## NEXT STEP:
+
+After user selects 'C', load `{project-root}/_bmad/bmm-skills/1-analysis/research/market-steps/step-03-customer-pain-points.md` to analyze customer pain points, challenges, and unmet needs for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current customer data with rigorous source verification!

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

@@ -0,0 +1,249 @@
+# Market Research Step 3: Customer Pain Points and Needs
+
+## 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 NEEDS ANALYST, not content generator
+- 💬 FOCUS on customer pain points, challenges, and unmet needs
+- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ 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 pain points content generation
+- 📝 WRITE CUSTOMER PAIN POINTS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Customer behavior analysis completed in previous step
+- Focus on customer pain points, challenges, and unmet needs
+- Web search capabilities with source verification are enabled
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+
+## YOUR TASK:
+
+Conduct customer pain points and needs analysis with emphasis on challenges and frustrations.
+
+## CUSTOMER PAIN POINTS ANALYSIS SEQUENCE:
+
+### 1. Begin Customer Pain Points Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer pain point areas simultaneously and thoroughly.
+
+Start with customer pain points research approach:
+"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to understand customer challenges.
+
+**Customer Pain Points Focus:**
+
+- Customer challenges and frustrations
+- Unmet needs and unaddressed problems
+- Barriers to adoption or usage
+- Service and support pain points
+- Customer satisfaction gaps
+
+**Let me search for current customer pain points insights.**"
+
+### 2. Parallel Pain Points Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+Search the web: "{{research_topic}} customer pain points challenges"
+Search the web: "{{research_topic}} customer frustrations"
+Search the web: "{{research_topic}} unmet customer needs"
+Search the web: "{{research_topic}} customer barriers to adoption"
+
+**Analysis approach:**
+
+- Look for customer satisfaction surveys and reports
+- Search for customer complaints and reviews
+- Research customer support and service issues
+- Analyze barriers to customer adoption
+- Study unmet needs and market gaps
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings:
+
+**Research Coverage:**
+
+- Customer challenges and frustrations
+- Unmet needs and unaddressed problems
+- Barriers to adoption or usage
+- Service and support pain points
+
+**Cross-Pain Points Analysis:**
+[Identify patterns connecting different types of pain points]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Customer Pain Points Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare customer pain points analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Pain Points and Needs
+
+### Customer Challenges and Frustrations
+
+[Customer challenges analysis with source citations]
+_Primary Frustrations: [Major customer frustrations identified]_
+_Usage Barriers: [Barriers preventing effective usage]_
+_Service Pain Points: [Customer service and support issues]_
+_Frequency Analysis: [How often these challenges occur]_
+_Source: [URL]_
+
+### Unmet Customer Needs
+
+[Unmet needs analysis with source citations]
+_Critical Unmet Needs: [Most important unaddressed needs]_
+_Solution Gaps: [Opportunities to address unmet needs]_
+_Market Gaps: [Market opportunities from unmet needs]_
+_Priority Analysis: [Which needs are most critical]_
+_Source: [URL]_
+
+### Barriers to Adoption
+
+[Adoption barriers analysis with source citations]
+_Price Barriers: [Cost-related barriers to adoption]_
+_Technical Barriers: [Complexity or technical barriers]_
+_Trust Barriers: [Trust and credibility issues]_
+_Convenience Barriers: [Ease of use or accessibility issues]_
+_Source: [URL]_
+
+### Service and Support Pain Points
+
+[Service pain points analysis with source citations]
+_Customer Service Issues: [Common customer service problems]_
+_Support Gaps: [Areas where customer support is lacking]_
+_Communication Issues: [Communication breakdowns and frustrations]_
+_Response Time Issues: [Slow response and resolution problems]_
+_Source: [URL]_
+
+### Customer Satisfaction Gaps
+
+[Satisfaction gap analysis with source citations]
+_Expectation Gaps: [Differences between expectations and reality]_
+_Quality Gaps: [Areas where quality expectations aren't met]_
+_Value Perception Gaps: [Perceived value vs actual value]_
+_Trust and Credibility Gaps: [Trust issues affecting satisfaction]_
+_Source: [URL]_
+
+### Emotional Impact Assessment
+
+[Emotional impact analysis with source citations]
+_Frustration Levels: [Customer frustration severity assessment]_
+_Loyalty Risks: [How pain points affect customer loyalty]_
+_Reputation Impact: [Impact on brand or product reputation]_
+_Customer Retention Risks: [Risk of customer loss from pain points]_
+_Source: [URL]_
+
+### Pain Point Prioritization
+
+[Pain point prioritization with source citations]
+_High Priority Pain Points: [Most critical pain points to address]_
+_Medium Priority Pain Points: [Important but less critical pain points]_
+_Low Priority Pain Points: [Minor pain points with lower impact]_
+_Opportunity Mapping: [Pain points with highest solution opportunity]_
+_Source: [URL]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges.
+
+**Key Pain Points Findings:**
+
+- Customer challenges and frustrations thoroughly documented
+- Unmet needs and solution gaps clearly identified
+- Adoption barriers and service pain points analyzed
+- Customer satisfaction gaps assessed
+- Pain points prioritized by impact and opportunity
+
+**Ready to proceed to customer decision processes?**
+[C] Continue - Save this to document and proceed to decision processes analysis
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `{project-root}/_bmad/bmm-skills/1-analysis/research/market-steps/step-04-customer-decisions.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Customer challenges and frustrations clearly documented
+✅ Unmet needs and solution gaps identified
+✅ Adoption barriers and service pain points analyzed
+✅ Customer satisfaction gaps assessed
+✅ Pain points prioritized by impact and opportunity
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (customer decisions)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Relying solely on training data without web verification for current facts
+
+❌ Missing critical customer challenges or frustrations
+❌ Not identifying unmet needs or solution gaps
+❌ Incomplete adoption barriers analysis
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to customer decisions analysis step
+
+❌ **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 PAIN POINTS RESEARCH PROTOCOLS:
+
+- Research customer satisfaction surveys and reviews
+- Use customer feedback and complaint data
+- Analyze customer support and service issues
+- Study barriers to customer adoption
+- Focus on current pain point data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## PAIN POINTS ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative customer research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable pain point insights
+
+## NEXT STEP:
+
+After user selects 'C', load `{project-root}/_bmad/bmm-skills/1-analysis/research/market-steps/step-04-customer-decisions.md` to analyze customer decision processes, journey mapping, and decision factors for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current customer pain points data with rigorous source verification!

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

@@ -0,0 +1,259 @@
+# Market Research Step 4: Customer Decisions and Journey
+
+## 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 DECISION ANALYST, not content generator
+- 💬 FOCUS on customer decision processes and journey mapping
+- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- ✅ 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 decision processes content generation
+- 📝 WRITE CUSTOMER DECISIONS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Customer behavior and pain points analysis completed in previous steps
+- Focus on customer decision processes and journey mapping
+- Web search capabilities with source verification are enabled
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+
+## YOUR TASK:
+
+Conduct customer decision processes and journey analysis with emphasis on decision factors and journey mapping.
+
+## CUSTOMER DECISIONS ANALYSIS SEQUENCE:
+
+### 1. Begin Customer Decisions Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer decision areas simultaneously and thoroughly.
+
+Start with customer decisions research approach:
+"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** to understand customer decision-making.
+
+**Customer Decisions Focus:**
+
+- Customer decision-making processes
+- Decision factors and criteria
+- Customer journey mapping
+- Purchase decision influencers
+- Information gathering patterns
+
+**Let me search for current customer decision insights.**"
+
+### 2. Parallel Decisions Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+Search the web: "{{research_topic}} customer decision process"
+Search the web: "{{research_topic}} buying criteria factors"
+Search the web: "{{research_topic}} customer journey mapping"
+Search the web: "{{research_topic}} decision influencing factors"
+
+**Analysis approach:**
+
+- Look for customer decision research studies
+- Search for buying criteria and factor analysis
+- Research customer journey mapping methodologies
+- Analyze decision influence factors and channels
+- Study information gathering and evaluation patterns
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings:
+
+**Research Coverage:**
+
+- Customer decision-making processes
+- Decision factors and criteria
+- Customer journey mapping
+- Decision influence factors
+
+**Cross-Decisions Analysis:**
+[Identify patterns connecting decision factors and journey stages]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Customer Decisions Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare customer decisions analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Decision Processes and Journey
+
+### Customer Decision-Making Processes
+
+[Decision processes analysis with source citations]
+_Decision Stages: [Key stages in customer decision making]_
+_Decision Timelines: [Timeframes for different decisions]_
+_Complexity Levels: [Decision complexity assessment]_
+_Evaluation Methods: [How customers evaluate options]_
+_Source: [URL]_
+
+### Decision Factors and Criteria
+
+[Decision factors analysis with source citations]
+_Primary Decision Factors: [Most important factors in decisions]_
+_Secondary Decision Factors: [Supporting factors influencing decisions]_
+_Weighing Analysis: [How different factors are weighed]_
+_Evoluton Patterns: [How factors change over time]_
+_Source: [URL]_
+
+### Customer Journey Mapping
+
+[Journey mapping analysis with source citations]
+_Awareness Stage: [How customers become aware of {{research_topic}}]_
+_Consideration Stage: [Evaluation and comparison process]_
+_Decision Stage: [Final decision-making process]_
+_Purchase Stage: [Purchase execution and completion]_
+_Post-Purchase Stage: [Post-decision evaluation and behavior]_
+_Source: [URL]_
+
+### Touchpoint Analysis
+
+[Touchpoint analysis with source citations]
+_Digital Touchpoints: [Online and digital interaction points]_
+_Offline Touchpoints: [Physical and in-person interaction points]_
+_Information Sources: [Where customers get information]_
+_Influence Channels: [What influences customer decisions]_
+_Source: [URL]_
+
+### Information Gathering Patterns
+
+[Information patterns analysis with source citations]
+_Research Methods: [How customers research options]_
+_Information Sources Trusted: [Most trusted information sources]_
+_Research Duration: [Time spent gathering information]_
+_Evaluation Criteria: [How customers evaluate information]_
+_Source: [URL]_
+
+### Decision Influencers
+
+[Decision influencer analysis with source citations]
+_Peer Influence: [How friends and family influence decisions]_
+_Expert Influence: [How expert opinions affect decisions]_
+_Media Influence: [How media and marketing affect decisions]_
+_Social Proof Influence: [How reviews and testimonials affect decisions]_
+_Source: [URL]_
+
+### Purchase Decision Factors
+
+[Purchase decision factors analysis with source citations]
+_Immediate Purchase Drivers: [Factors triggering immediate purchase]_
+_Delayed Purchase Drivers: [Factors causing purchase delays]_
+_Brand Loyalty Factors: [Factors driving repeat purchases]_
+_Price Sensitivity: [How price affects purchase decisions]_
+_Source: [URL]_
+
+### Customer Decision Optimizations
+
+[Decision optimization analysis with source citations]
+_Friction Reduction: [Ways to make decisions easier]_
+_Trust Building: [Building customer trust in decisions]_
+_Conversion Optimization: [Optimizing decision-to-purchase rates]_
+_Loyalty Building: [Building long-term customer relationships]_
+_Source: [URL]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making.
+
+**Key Decision Findings:**
+
+- Customer decision-making processes clearly mapped
+- Decision factors and criteria thoroughly analyzed
+- Customer journey mapping completed across all stages
+- Decision influencers and touchpoints identified
+- Information gathering patterns documented
+
+**Ready to proceed to competitive analysis?**
+[C] Continue - Save this to document and proceed to competitive analysis
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Load: `{project-root}/_bmad/bmm-skills/1-analysis/research/market-steps/step-05-competitive-analysis.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Customer decision-making processes clearly mapped
+✅ Decision factors and criteria thoroughly analyzed
+✅ Customer journey mapping completed across all stages
+✅ Decision influencers and touchpoints identified
+✅ Information gathering patterns documented
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (competitive analysis)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Relying solely on training data without web verification for current facts
+
+❌ Missing critical decision-making process stages
+❌ Not identifying key decision factors
+❌ Incomplete customer journey mapping
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to competitive analysis step
+
+❌ **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 DECISIONS RESEARCH PROTOCOLS:
+
+- Research customer decision studies and psychology
+- Use customer journey mapping methodologies
+- Analyze buying criteria and decision factors
+- Study decision influence and touchpoint analysis
+- Focus on current decision data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## DECISION ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative customer decision research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable decision insights
+
+## NEXT STEP:
+
+After user selects 'C', load `{project-root}/_bmad/bmm-skills/1-analysis/research/market-steps/step-05-competitive-analysis.md` to analyze competitive landscape, market positioning, and competitive strategies for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current customer decision data with rigorous source verification!

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

@@ -0,0 +1,177 @@
+# Market Research Step 5: Competitive Analysis
+
+## 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 COMPETITIVE ANALYST, not content generator
+- 💬 FOCUS on competitive landscape and market positioning
+- 🔍 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] complete option after competitive analysis content generation
+- 💾 ONLY save when user chooses C (Complete)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
+- 🚫 FORBIDDEN to complete workflow until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Focus on competitive landscape and market positioning analysis
+- Web search capabilities with source verification are enabled
+- May need to search for specific competitor information
+
+## YOUR TASK:
+
+Conduct comprehensive competitive analysis with emphasis on market positioning.
+
+## COMPETITIVE ANALYSIS SEQUENCE:
+
+### 1. Begin Competitive Analysis
+
+Start with competitive research approach:
+"Now I'll conduct **competitive analysis** to understand the competitive landscape.
+
+**Competitive Analysis Focus:**
+
+- Key players and market share
+- Competitive positioning strategies
+- Strengths and weaknesses analysis
+- Market differentiation opportunities
+- Competitive threats and challenges
+
+**Let me search for current competitive information.**"
+
+### 2. Generate Competitive Analysis Content
+
+Prepare competitive analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Competitive Landscape
+
+### Key Market Players
+
+[Key players analysis with market share data]
+_Source: [URL]_
+
+### Market Share Analysis
+
+[Market share analysis with source citations]
+_Source: [URL]_
+
+### Competitive Positioning
+
+[Positioning analysis with source citations]
+_Source: [URL]_
+
+### Strengths and Weaknesses
+
+[SWOT analysis with source citations]
+_Source: [URL]_
+
+### Market Differentiation
+
+[Differentiation analysis with source citations]
+_Source: [URL]_
+
+### Competitive Threats
+
+[Threats analysis with source citations]
+_Source: [URL]_
+
+### Opportunities
+
+[Competitive opportunities analysis with source citations]
+_Source: [URL]_
+```
+
+### 3. Present Analysis and Complete Option
+
+Show the generated competitive analysis and present complete option:
+"I've completed the **competitive analysis** for the competitive landscape.
+
+**Key Competitive Findings:**
+
+- Key market players and market share identified
+- Competitive positioning strategies mapped
+- Strengths and weaknesses thoroughly analyzed
+- Market differentiation opportunities identified
+- Competitive threats and challenges documented
+
+**Ready to complete the market research?**
+[C] Complete Research - Save final document and conclude
+
+### 4. Handle Complete Selection
+
+#### If 'C' (Complete Research):
+
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Complete the market research workflow
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 2.
+
+## SUCCESS METRICS:
+
+✅ Key market players identified
+✅ Market share analysis completed with source verification
+✅ Competitive positioning strategies clearly mapped
+✅ Strengths and weaknesses thoroughly analyzed
+✅ Market differentiation opportunities identified
+✅ [C] complete option presented and handled correctly
+✅ Content properly appended to document when C selected
+✅ Market research workflow completed successfully
+
+## FAILURE MODES:
+
+❌ Relying solely on training data without web verification for current facts
+
+❌ Missing key market players or market share data
+❌ Incomplete competitive positioning analysis
+❌ Not identifying market differentiation opportunities
+❌ Not presenting completion option for research workflow
+❌ 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
+
+## COMPETITIVE RESEARCH PROTOCOLS:
+
+- Search for industry reports and competitive intelligence
+- Use competitor company websites and annual reports
+- Research market research firm competitive analyses
+- Note competitive advantages and disadvantages
+- Search for recent market developments and disruptions
+
+## MARKET RESEARCH COMPLETION:
+
+When 'C' is selected:
+
+- All market research steps completed
+- Comprehensive market research document generated
+- All sections appended with source citations
+- Market research workflow status updated
+- Final recommendations provided to user
+
+## NEXT STEPS:
+
+Market research workflow complete. User may:
+
+- Use market research to inform product development strategies
+- Conduct additional competitive research on specific companies
+- Combine market research with other research types for comprehensive insights
+
+Congratulations on completing comprehensive market research! 🎉

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

@@ -0,0 +1,476 @@
+# Market Research Step 6: Research Completion
+
+## 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 MARKET RESEARCH STRATEGIST, not content generator
+- 💬 FOCUS on strategic recommendations and actionable insights
+- 🔍 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] complete option after completion content generation
+- 💾 ONLY save when user chooses C (Complete)
+- 📖 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
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - comprehensive market analysis
+- **Research goals = "{{research_goals}}"** - achieved through exhaustive market research
+- All market research sections have been completed (customer behavior, pain points, decisions, competitive analysis)
+- Web search capabilities with source verification are enabled
+- This is the final synthesis step producing the complete market research document
+
+## YOUR TASK:
+
+Produce a comprehensive, authoritative market research document on **{{research_topic}}** with compelling narrative introduction, detailed TOC, and executive summary based on exhaustive market research.
+
+## MARKET RESEARCH COMPLETION SEQUENCE:
+
+### 1. Begin Strategic Synthesis
+
+Start with strategic synthesis approach:
+"Now I'll complete our market research with **strategic synthesis and recommendations** .
+
+**Strategic Synthesis Focus:**
+
+- Integrated insights from market, customer, and competitive analysis
+- Strategic recommendations based on research findings
+- Market entry or expansion strategies
+- Risk assessment and mitigation approaches
+- Actionable next steps and implementation guidance
+
+**Let me search for current strategic insights and best practices.**"
+
+### 2. Web Search for Market Entry Strategies
+
+Search for current market strategies:
+Search the web: "market entry strategies best practices"
+
+**Strategy focus:**
+
+- Market entry timing and approaches
+- Go-to-market strategies and frameworks
+- Market positioning and differentiation tactics
+- Customer acquisition and growth strategies
+
+### 3. Web Search for Risk Assessment
+
+Search for current risk approaches:
+Search the web: "market research risk assessment frameworks"
+
+**Risk focus:**
+
+- Market risks and uncertainty management
+- Competitive threats and mitigation strategies
+- Regulatory and compliance risks
+- Economic and market volatility considerations
+
+### 4. Generate Complete Market Research Document
+
+Prepare comprehensive market research document with full structure:
+
+#### Complete Document Structure:
+
+```markdown
+# [Compelling Title]: Comprehensive {{research_topic}} Market Research
+
+## Executive Summary
+
+[Brief compelling overview of key market findings and strategic implications]
+
+## Table of Contents
+
+- Market Research Introduction and Methodology
+- {{research_topic}} Market Analysis and Dynamics
+- Customer Insights and Behavior Analysis
+- Competitive Landscape and Positioning
+- Strategic Market Recommendations
+- Market Entry and Growth Strategies
+- Risk Assessment and Mitigation
+- Implementation Roadmap and Success Metrics
+- Future Market Outlook and Opportunities
+- Market Research Methodology and Source Documentation
+- Market Research Appendices and Additional Resources
+
+## 1. Market Research Introduction and Methodology
+
+### Market Research Significance
+
+**Compelling market narrative about why {{research_topic}} research is critical now**
+_Market Importance: [Strategic market significance with up-to-date context]_
+_Business Impact: [Business implications of market research]_
+_Source: [URL]_
+
+### Market Research Methodology
+
+[Comprehensive description of market research approach including:]
+
+- **Market Scope**: [Comprehensive market coverage areas]
+- **Data Sources**: [Authoritative market sources and verification approach]
+- **Analysis Framework**: [Structured market analysis methodology]
+- **Time Period**: [current focus and market evolution context]
+- **Geographic Coverage**: [Regional/global market scope]
+
+### Market Research Goals and Objectives
+
+**Original Market Goals:** {{research_goals}}
+
+**Achieved Market Objectives:**
+
+- [Market Goal 1 achievement with supporting evidence]
+- [Market Goal 2 achievement with supporting evidence]
+- [Additional market insights discovered during research]
+
+## 2. {{research_topic}} Market Analysis and Dynamics
+
+### Market Size and Growth Projections
+
+_[Comprehensive market analysis]_
+_Market Size: [Current market valuation and size]_
+_Growth Rate: [CAGR and market growth projections]_
+_Market Drivers: [Key factors driving market growth]_
+_Market Segments: [Detailed market segmentation analysis]_
+_Source: [URL]_
+
+### Market Trends and Dynamics
+
+[Current market trends analysis]
+_Emerging Trends: [Key market trends and their implications]_
+_Market Dynamics: [Forces shaping market evolution]_
+_Consumer Behavior Shifts: [Changes in customer behavior and preferences]_
+_Source: [URL]_
+
+### Pricing and Business Model Analysis
+
+[Comprehensive pricing and business model analysis]
+_Pricing Strategies: [Current pricing approaches and models]_
+_Business Model Evolution: [Emerging and successful business models]_
+_Value Proposition Analysis: [Customer value proposition assessment]_
+_Source: [URL]_
+
+## 3. Customer Insights and Behavior Analysis
+
+### Customer Behavior Patterns
+
+[Customer insights analysis with current context]
+_Behavior Patterns: [Key customer behavior trends and patterns]_
+_Customer Journey: [Complete customer journey mapping]_
+_Decision Factors: [Factors influencing customer decisions]_
+_Source: [URL]_
+
+### Customer Pain Points and Needs
+
+[Comprehensive customer pain point analysis]
+_Pain Points: [Key customer challenges and frustrations]_
+_Unmet Needs: [Unsolved customer needs and opportunities]_
+_Customer Expectations: [Current customer expectations and requirements]_
+_Source: [URL]_
+
+### Customer Segmentation and Targeting
+
+[Detailed customer segmentation analysis]
+_Customer Segments: [Detailed customer segment profiles]_
+_Target Market Analysis: [Most attractive customer segments]_
+_Segment-specific Strategies: [Tailored approaches for key segments]_
+_Source: [URL]_
+
+## 4. Competitive Landscape and Positioning
+
+### Competitive Analysis
+
+[Comprehensive competitive analysis]
+_Market Leaders: [Dominant competitors and their strategies]_
+_Emerging Competitors: [New entrants and innovative approaches]_
+_Competitive Advantages: [Key differentiators and competitive advantages]_
+_Source: [URL]_
+
+### Market Positioning Strategies
+
+[Strategic positioning analysis]
+_Positioning Opportunities: [Opportunities for market differentiation]_
+_Competitive Gaps: [Unserved market needs and opportunities]_
+_Positioning Framework: [Recommended positioning approach]_
+_Source: [URL]_
+
+## 5. Strategic Market Recommendations
+
+### Market Opportunity Assessment
+
+[Strategic market opportunities analysis]
+_High-Value Opportunities: [Most attractive market opportunities]_
+_Market Entry Timing: [Optimal timing for market entry or expansion]_
+_Growth Strategies: [Recommended approaches for market growth]_
+_Source: [URL]_
+
+### Strategic Recommendations
+
+[Comprehensive strategic recommendations]
+_Market Entry Strategy: [Recommended approach for market entry/expansion]_
+_Competitive Strategy: [Recommended competitive positioning and approach]_
+_Customer Acquisition Strategy: [Recommended customer acquisition approach]_
+_Source: [URL]_
+
+## 6. Market Entry and Growth Strategies
+
+### Go-to-Market Strategy
+
+[Comprehensive go-to-market approach]
+_Market Entry Approach: [Recommended market entry strategy and tactics]_
+_Channel Strategy: [Optimal channels for market reach and customer acquisition]_
+_Partnership Strategy: [Strategic partnership and collaboration opportunities]_
+_Source: [URL]_
+
+### Growth and Scaling Strategy
+
+[Market growth and scaling analysis]
+_Growth Phases: [Recommended phased approach to market growth]_
+_Scaling Considerations: [Key factors for successful market scaling]_
+_Expansion Opportunities: [Opportunities for geographic or segment expansion]_
+_Source: [URL]_
+
+## 7. Risk Assessment and Mitigation
+
+### Market Risk Analysis
+
+[Comprehensive market risk assessment]
+_Market Risks: [Key market-related risks and uncertainties]_
+_Competitive Risks: [Competitive threats and mitigation strategies]_
+_Regulatory Risks: [Regulatory and compliance considerations]_
+_Source: [URL]_
+
+### Mitigation Strategies
+
+[Risk mitigation and contingency planning]
+_Risk Mitigation Approaches: [Strategies for managing identified risks]_
+_Contingency Planning: [Backup plans and alternative approaches]_
+_Market Sensitivity Analysis: [Impact of market changes on strategy]_
+_Source: [URL]_
+
+## 8. Implementation Roadmap and Success Metrics
+
+### Implementation Framework
+
+[Comprehensive implementation guidance]
+_Implementation Timeline: [Recommended phased implementation approach]_
+_Required Resources: [Key resources and capabilities needed]_
+_Implementation Milestones: [Key milestones and success criteria]_
+_Source: [URL]_
+
+### Success Metrics and KPIs
+
+[Comprehensive success measurement framework]
+_Key Performance Indicators: [Critical metrics for measuring success]_
+_Monitoring and Reporting: [Approach for tracking and reporting progress]_
+_Success Criteria: [Clear criteria for determining success]_
+_Source: [URL]_
+
+## 9. Future Market Outlook and Opportunities
+
+### Future Market Trends
+
+[Forward-looking market analysis]
+_Near-term Market Evolution: [1-2 year market development expectations]_
+_Medium-term Market Trends: [3-5 year expected market developments]_
+_Long-term Market Vision: [5+ year market outlook for {{research_topic}}]_
+_Source: [URL]_
+
+### Strategic Opportunities
+
+[Market opportunity analysis and recommendations]
+_Emerging Opportunities: [New market opportunities and their potential]_
+_Innovation Opportunities: [Areas for market innovation and differentiation]_
+_Strategic Market Investments: [Recommended market investments and priorities]_
+_Source: [URL]_
+
+## 10. Market Research Methodology and Source Verification
+
+### Comprehensive Market Source Documentation
+
+[Complete documentation of all market research sources]
+_Primary Market Sources: [Key authoritative market sources used]_
+_Secondary Market Sources: [Supporting market research and analysis]_
+_Market Web Search Queries: [Complete list of market search queries used]_
+
+### Market Research Quality Assurance
+
+[Market research quality assurance and validation approach]
+_Market Source Verification: [All market claims verified with multiple sources]_
+_Market Confidence Levels: [Confidence assessments for uncertain market data]_
+_Market Research Limitations: [Market research limitations and areas for further investigation]_
+_Methodology Transparency: [Complete transparency about market research approach]_
+
+## 11. Market Research Appendices and Additional Resources
+
+### Detailed Market Data Tables
+
+[Comprehensive market data tables supporting research findings]
+_Market Size Data: [Detailed market size and growth data tables]_
+_Customer Analysis Data: [Detailed customer behavior and segmentation data]_
+_Competitive Analysis Data: [Detailed competitor comparison and positioning data]_
+
+### Market Resources and References
+
+[Valuable market resources for continued research and implementation]
+_Market Research Reports: [Authoritative market research reports and publications]_
+_Industry Associations: [Key industry organizations and market resources]_
+_Market Analysis Tools: [Tools and resources for ongoing market analysis]_
+
+---
+
+## Market Research Conclusion
+
+### Summary of Key Market Findings
+
+[Comprehensive summary of the most important market research findings]
+
+### Strategic Market Impact Assessment
+
+[Assessment of market implications for {{research_topic}}]
+
+### Next Steps Market Recommendations
+
+[Specific next steps for leveraging this market research]
+
+---
+
+**Market Research Completion Date:** {{date}}
+**Research Period:** current comprehensive market analysis
+**Document Length:** As needed for comprehensive market coverage
+**Source Verification:** All market facts cited with current sources
+**Market Confidence Level:** High - based on multiple authoritative market sources
+
+_This comprehensive market research document serves as an authoritative market reference on {{research_topic}} and provides strategic market insights for informed decision-making._
+```
+
+### 5. Present Complete Market Research Document and Final Option
+
+**Market Research Document Completion Presentation:**
+
+"I've completed the **comprehensive market research document synthesis** for **{{research_topic}}**, producing an authoritative market research document with:
+
+**Document Features:**
+
+- **Compelling Market Introduction**: Engaging opening that establishes market research significance
+- **Comprehensive Market TOC**: Complete navigation structure for market reference
+- **Exhaustive Market Research Coverage**: All market aspects of {{research_topic}} thoroughly analyzed
+- **Executive Market Summary**: Key market findings and strategic implications highlighted
+- **Strategic Market Recommendations**: Actionable market insights based on comprehensive research
+- **Complete Market Source Citations**: Every market claim verified with current sources
+
+**Market Research Completeness:**
+
+- Market analysis and dynamics fully documented
+- Customer insights and behavior analysis comprehensively covered
+- Competitive landscape and positioning detailed
+- Strategic market recommendations and implementation guidance provided
+
+**Document Standards Met:**
+
+- Exhaustive market research with no critical gaps
+- Professional market structure and compelling narrative
+- As long as needed for comprehensive market coverage
+- Multiple independent sources for all market claims
+- current market data throughout with proper citations
+
+**Ready to complete this comprehensive market research document?**
+[C] Complete Research - Save final comprehensive market research document
+
+### 6. Handle Complete Selection
+
+#### If 'C' (Complete Research):
+
+- **Replace** the template placeholder `[Research overview and methodology will be appended here]` in the `## Research Overview` section near the top of the document with a concise 2-3 paragraph overview summarizing the research scope, key findings, and a pointer to the full executive summary in the Research Synthesis section
+- Append the final content to the research document
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Complete the market research workflow
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to the research document using the structure from step 4. Also replace the `[Research overview and methodology will be appended here]` placeholder in the Research Overview section at the top of the document.
+
+## SUCCESS METRICS:
+
+✅ Compelling market introduction with research significance
+✅ Comprehensive market table of contents with complete document structure
+✅ Exhaustive market research coverage across all market aspects
+✅ Executive market summary with key findings and strategic implications
+✅ Strategic market recommendations grounded in comprehensive research
+✅ Complete market source verification with current citations
+✅ Professional market document structure and compelling narrative
+✅ [C] complete option presented and handled correctly
+✅ Market research workflow completed with comprehensive document
+
+## FAILURE MODES:
+
+❌ Not producing compelling market introduction
+❌ Missing comprehensive market table of contents
+❌ Incomplete market research coverage across market aspects
+❌ Not providing executive market summary with key findings
+❌ Missing strategic market recommendations based on research
+❌ Relying solely on training data without web verification for current facts
+❌ Producing market document without professional structure
+❌ Not presenting completion option for final market document
+
+❌ **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
+
+## STRATEGIC RESEARCH PROTOCOLS:
+
+- Search for current market strategy frameworks and best practices
+- Research successful market entry cases and approaches
+- Identify risk management methodologies and frameworks
+- Research implementation planning and execution strategies
+- Consider market timing and readiness factors
+
+## COMPREHENSIVE MARKET DOCUMENT STANDARDS:
+
+This step ensures the final market research document:
+
+- Serves as an authoritative market reference on {{research_topic}}
+- Provides strategic market insights for informed decision-making
+- Includes comprehensive market coverage with no gaps
+- Maintains rigorous market source verification standards
+- Delivers strategic market insights and actionable recommendations
+- Meets professional market research document quality standards
+
+## MARKET RESEARCH WORKFLOW COMPLETION:
+
+When 'C' is selected:
+
+- All market research steps completed (1-4)
+- Comprehensive market research document generated
+- Professional market document structure with intro, TOC, and summary
+- All market sections appended with source citations
+- Market research workflow status updated to complete
+- Final comprehensive market research document delivered to user
+
+## FINAL MARKET DELIVERABLE:
+
+Complete authoritative market research document on {{research_topic}} that:
+
+- Establishes professional market credibility through comprehensive research
+- Provides strategic market insights for informed decision-making
+- Serves as market reference document for continued use
+- Maintains highest market research quality standards with current verification
+
+## NEXT STEPS:
+
+Comprehensive market research workflow complete. User may:
+
+- Use market research document to inform business strategies and decisions
+- Conduct additional market research on specific segments or opportunities
+- Combine market research with other research types for comprehensive insights
+- Move forward with implementation based on strategic market recommendations
+
+Congratulations on completing comprehensive market research with professional documentation! 🎉

src/bmm-skills/1-analysis/research/research.template.md

@@ -0,0 +1,29 @@
+---
+stepsCompleted: []
+inputDocuments: []
+workflowType: 'research'
+lastStep: 1
+research_type: '{{research_type}}'
+research_topic: '{{research_topic}}'
+research_goals: '{{research_goals}}'
+user_name: '{{user_name}}'
+date: '{{date}}'
+web_research_enabled: true
+source_verification: true
+---
+
+# Research Report: {{research_type}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+**Research Type:** {{research_type}}
+
+---
+
+## Research Overview
+
+[Research overview and methodology will be appended here]
+
+---
+
+<!-- Content will be appended sequentially through research workflow steps -->

src/bmm-skills/4-implementation/bmad-code-review/steps/step-02-review.md

@@ -13,20 +13,27 @@ failed_layers: '' # set at runtime: comma-separated list of layers that failed o
 
 ## INSTRUCTIONS
 
-1. If `{review_mode}` = `"no-spec"`, note to the user: "Acceptance Auditor skipped — no spec file provided."
+1. Launch parallel subagents. Each subagent gets NO conversation history from this session:
 
-2. Launch parallel subagents without conversation context. If subagents are not available, generate prompt files in `{implementation_artifacts}` — one per reviewer role below — and HALT. Ask the user to run each in a separate session (ideally a different LLM) and paste back the findings. When findings are pasted, resume from this point and proceed to step 3.
+   - **Blind Hunter** -- Invoke the `bmad-review-adversarial-general` skill in a subagent. Pass `content` = `{diff_output}` only. No spec, no project access.
 
-   - **Blind Hunter** — receives `{diff_output}` only. No spec, no context docs, no project access. Invoke via the `bmad-review-adversarial-general` skill.
+   - **Edge Case Hunter** -- Invoke the `bmad-review-edge-case-hunter` skill in a subagent. Pass `content` = `{diff_output}`. This subagent has read access to the project.
 
-   - **Edge Case Hunter** — receives `{diff_output}` and read access to the project. Invoke via the `bmad-review-edge-case-hunter` skill.
+   - **Acceptance Auditor** (only if `{review_mode}` = `"full"`) -- A subagent that receives `{diff_output}`, the content of the file at `{spec_file}`, and any loaded context docs. Its prompt:
+     > You are an Acceptance Auditor. Review this diff against the spec and context docs. Check for: violations of acceptance criteria, deviations from spec intent, missing implementation of specified behavior, contradictions between spec constraints and actual code. Output findings as a markdown list. Each finding: one-line title, which AC/constraint it violates, and evidence from the diff.
 
-   - **Acceptance Auditor** (only if `{review_mode}` = `"full"`) — receives `{diff_output}`, the content of the file at `{spec_file}`, and any loaded context docs. Its prompt:
-     > You are an Acceptance Auditor. Review this diff against the spec and context docs. Check for: violations of acceptance criteria, deviations from spec intent, missing implementation of specified behavior, contradictions between spec constraints and actual code. Output findings as a Markdown list. Each finding: one-line title, which AC/constraint it violates, and evidence from the diff.
+2. **Subagent failure handling**: If any subagent fails, times out, or returns empty results, append the layer name to `{failed_layers}` (comma-separated) and proceed with findings from the remaining layers.
 
-3. **Subagent failure handling**: If any subagent fails, times out, or returns empty results, append the layer name to `{failed_layers}` (comma-separated) and proceed with findings from the remaining layers.
+3. If `{review_mode}` = `"no-spec"`, note to the user: "Acceptance Auditor skipped — no spec file provided."
 
-4. Collect all findings from the completed layers.
+4. **Fallback** (if subagents are not available): Generate prompt files in `{implementation_artifacts}` -- one per active reviewer:
+   - `review-blind-hunter.md` (always)
+   - `review-edge-case-hunter.md` (always)
+   - `review-acceptance-auditor.md` (only if `{review_mode}` = `"full"`)
+
+   HALT. Tell the user to run each prompt in a separate session and paste back findings. When findings are pasted, resume from this point and proceed to step 3.
+
+5. Collect all findings from the completed layers.
 
 
 ## NEXT

src/bmm-skills/4-implementation/bmad-code-review/steps/step-03-triage.md

@@ -30,18 +30,19 @@
    - Set `source` to the merged sources (e.g., `blind+edge`).
 
 3. **Classify** each finding into exactly one bucket:
-   - **decision_needed** -- There is an ambiguous choice that requires human input. The code cannot be correctly patched without knowing the user's intent. Only possible if `{review_mode}` = `"full"`.
-   - **patch** -- Code issue that is fixable without human input. The correct fix is unambiguous.
+   - **intent_gap** -- The spec/intent is incomplete; cannot resolve from existing information. Only possible if `{review_mode}` = `"full"`.
+   - **bad_spec** -- The spec should have prevented this; spec is wrong or ambiguous. Only possible if `{review_mode}` = `"full"`.
+   - **patch** -- Code issue that is trivially fixable without human input. Just needs a code change.
    - **defer** -- Pre-existing issue not caused by the current change. Real but not actionable now.
-   - **dismiss** -- Noise, false positive, or handled elsewhere.
+   - **reject** -- Noise, false positive, or handled elsewhere.
 
-   If `{review_mode}` = `"no-spec"` and a finding would otherwise be `decision_needed`, reclassify it as `patch` (if the fix is unambiguous) or `defer` (if not).
+   If `{review_mode}` = `"no-spec"` and a finding would otherwise be `intent_gap` or `bad_spec`, reclassify it as `patch` (if code-fixable) or `defer` (if not).
 
-4. **Drop** all `dismiss` findings. Record the dismiss count for the summary.
+4. **Drop** all `reject` findings. Record the reject count for the summary.
 
-5. If `{failed_layers}` is non-empty, report which layers failed before announcing results. If zero findings remain after dropping dismissed AND `{failed_layers}` is non-empty, warn the user that the review may be incomplete rather than announcing a clean review.
+5. If `{failed_layers}` is non-empty, report which layers failed before announcing results. If zero findings remain after dropping rejects AND `{failed_layers}` is non-empty, warn the user that the review may be incomplete rather than announcing a clean review.
 
-6. If zero findings remain after triage (all rejected or none raised): state "✅ Clean review — all layers passed." (Step 3 already warned if any review layers failed via `{failed_layers}`.)
+6. If zero findings remain after dropping rejects and no layers failed, note clean review.
 
 
 ## NEXT

src/bmm-skills/4-implementation/bmad-code-review/steps/step-04-present.md

@@ -1,84 +1,38 @@
 ---
-deferred_work_file: '{implementation_artifacts}/deferred-work.md'
 ---
 
-# Step 4: Present and Act
+# Step 4: Present
 
 ## RULES
 
 - YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
-- When `{spec_file}` is set, always write findings to the story file before offering action choices.
-- `decision-needed` findings must be resolved before handling `patch` findings.
+- Do NOT auto-fix anything. Present findings and let the user decide next steps.
 
 ## INSTRUCTIONS
 
-### 1. Clean review shortcut
+1. Group remaining findings by category.
 
-If zero findings remain after triage (all dismissed or none raised): state that and end the workflow.
+2. Present to the user in this order (include a section only if findings exist in that category):
 
-### 2. Write findings to the story file
+   - **Intent Gaps**: "These findings suggest the captured intent is incomplete. Consider clarifying intent before proceeding."
+     - List each with title + detail.
 
-If `{spec_file}` exists and contains a Tasks/Subtasks section, append a `### Review Findings` subsection. Write all findings in this order:
+   - **Bad Spec**: "These findings suggest the spec should be amended. Consider regenerating or amending the spec with this context:"
+     - List each with title + detail + suggested spec amendment.
 
-1. **`decision-needed`** findings (unchecked):
-   `- [ ] [Review][Decision] <Title> — <Detail>`
+   - **Patch**: "These are fixable code issues:"
+     - List each with title + detail + location (if available).
 
-2. **`patch`** findings (unchecked):
-   `- [ ] [Review][Patch] <Title> [<file>:<line>]`
+   - **Defer**: "Pre-existing issues surfaced by this review (not caused by current changes):"
+     - List each with title + detail.
 
-3. **`defer`** findings (checked off, marked deferred):
-   `- [x] [Review][Defer] <Title> [<file>:<line>] — deferred, pre-existing`
+3. Summary line: **X** intent_gap, **Y** bad_spec, **Z** patch, **W** defer findings. **R** findings rejected as noise.
 
-Also append each `defer` finding to `{deferred_work_file}` under a heading `## Deferred from: code review ({date})`. If `{spec_file}` is set, include its basename in the heading (e.g., `code review of story-3.3 (2026-03-18)`). One bullet per finding with description.
+4. If clean review (zero findings across all layers after triage): state that N findings were raised but all were classified as noise, or that no findings were raised at all (as applicable).
 
-### 3. Present summary
+5. Offer the user next steps (recommendations, not automated actions):
+   - If `patch` findings exist: "These can be addressed in a follow-up implementation pass or manually."
+   - If `intent_gap` or `bad_spec` findings exist: "Consider running the planning workflow to clarify intent or amend the spec before continuing."
+   - If only `defer` findings remain: "No action needed for this change. Deferred items are noted for future attention."
 
-Announce what was written:
-
-> **Code review complete.** <D> `decision-needed`, <P> `patch`, <W> `defer`, <R> dismissed as noise.
-
-If `{spec_file}` is set, add: `Findings written to the review findings section in {spec_file}.`
-Otherwise add: `Findings are listed above. No story file was provided, so nothing was persisted.`
-
-### 4. Resolve decision-needed findings
-
-If `decision_needed` findings exist, present each one with its detail and the options available. The user must decide — the correct fix is ambiguous without their input. Walk through each finding (or batch related ones) and get the user's call. Once resolved, each becomes a `patch`, `defer`, or is dismissed.
-
-If the user chooses to defer, ask: Quick one-line reason for deferring this item? (helps future reviews): — then append that reason to both the story file bullet and the `{deferred_work_file}` entry.
-
-**HALT** — I am waiting for your numbered choice. Reply with only the number (or "0" for batch). Do not proceed until you select an option.
-
-### 5. Handle `patch` findings
-
-If `patch` findings exist (including any resolved from step 4), HALT. Ask the user:
-
-If `{spec_file}` is set, present all three options (if >3 `patch` findings exist, also show option 0):
-
-> **How would you like to handle the <Z> `patch` findings?**
-> 0. **Batch-apply all** — automatically fix every non-controversial patch (recommended when there are many)
-> 1. **Fix them automatically** — I will apply fixes now
-> 2. **Leave as action items** — they are already in the story file
-> 3. **Walk through each** — let me show details before deciding
-
-If `{spec_file}` is **not** set, present only options 1 and 3 (omit option 2 — findings were not written to a file). If >3 `patch` findings exist, also show option 0:
-
-> **How would you like to handle the <Z> `patch` findings?**
-> 0. **Batch-apply all** — automatically fix every non-controversial patch (recommended when there are many)
-> 1. **Fix them automatically** — I will apply fixes now
-> 2. **Walk through each** — let me show details before deciding
-
-**HALT** — I am waiting for your numbered choice. Reply with only the number (or "0" for batch). Do not proceed until you select an option.
-
-- **Option 0** (only when >3 findings): Apply all non-controversial patches without per-finding confirmation. Skip any finding that requires judgment. Present a summary of changes made and any skipped findings.
-- **Option 1**: Apply each fix. After all patches are applied, present a summary of changes made. If `{spec_file}` is set, check off the items in the story file.
-- **Option 2** (only when `{spec_file}` is set): Done — findings are already written to the story.
-- **Walk through each**: Present each finding with full detail, diff context, and suggested fix. After walkthrough, re-offer the applicable options above.
-
-  **HALT** — I am waiting for your numbered choice. Reply with only the number (or "0" for batch). Do not proceed until you select an option.
-
-**✅ Code review actions complete**
-
-- Decision-needed resolved: <D>
-- Patches handled: <P>
-- Deferred: <W>
-- Dismissed: <R>
+Workflow complete.

src/bmm-skills/module-help.csv

@@ -12,7 +12,7 @@ bmm,1-analysis,Brainstorm Project,BP,10,skill:bmad-brainstorming,bmad-brainstorm
 bmm,1-analysis,Market Research,MR,20,skill:bmad-market-research,bmad-bmm-market-research,false,analyst,Create Mode,"Market analysis competitive landscape customer needs and trends","planning_artifacts|project-knowledge","research documents",
 bmm,1-analysis,Domain Research,DR,21,skill:bmad-domain-research,bmad-bmm-domain-research,false,analyst,Create Mode,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project_knowledge","research documents",
 bmm,1-analysis,Technical Research,TR,22,skill:bmad-technical-research,bmad-bmm-technical-research,false,analyst,Create Mode,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project_knowledge","research documents",
-bmm,1-analysis,Create Brief,CB,30,skill:bmad-product-brief,bmad-bmm-product-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
+bmm,1-analysis,Create Brief,CB,30,skill:bmad-create-product-brief,bmad-bmm-create-product-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
 bmm,2-planning,Create PRD,CP,10,skill:bmad-create-prd,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
 bmm,2-planning,Validate PRD,VP,20,skill:bmad-validate-prd,bmad-bmm-validate-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report",
 bmm,2-planning,Edit PRD,EP,25,skill:bmad-edit-prd,bmad-bmm-edit-prd,false,pm,Edit Mode,"Improve and enhance an existing PRD",planning_artifacts,"updated prd",