bmad-odoo 1.0.0

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

@@ -0,0 +1,166 @@
+---
+name: 'step-01b-continue'
+description: 'Resume the product brief workflow from where it was left off, ensuring smooth continuation'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+workflowFile: '{workflow_path}/workflow.md'
+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: Load, read entire file, then execute 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 load and read fully 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.

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

@@ -0,0 +1,204 @@
+---
+name: 'step-02-vision'
+description: 'Discover and define the core product vision, problem statement, and unique value proposition'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-02-vision.md'
+nextStepFile: '{workflow_path}/steps/step-03-users.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.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}`
+
+### 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: Execute {advancedElicitationTask} with current vision content to dive deeper and refine
+- IF P: Execute {partyModeWorkflow} to bring different perspectives to positioning and differentiation
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then only then load, read entire file, then execute {nextStepFile}
+- IF 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 load and read fully `{nextStepFile}` to execute and 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.

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

@@ -0,0 +1,207 @@
+---
+name: 'step-03-users'
+description: 'Define target users with rich personas and map their key interactions with the product'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-users.md'
+nextStepFile: '{workflow_path}/steps/step-04-metrics.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.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}`
+
+### 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: Execute {advancedElicitationTask} with current user content to dive deeper into personas and journeys
+- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate user understanding
+- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then only then load, read entire file, then execute {nextStepFile}
+- IF 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 load and read fully `{nextStepFile}` to execute and 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.