bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.10

package/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md

@@ -1,353 +1,524 @@
-# Product Brief - Interactive Workflow Instructions
+# Product Brief - Context-Adaptive Discovery Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.md</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>This workflow uses INTENT-DRIVEN FACILITATION - adapt organically to what emerges</critical>
+<critical>The goal is DISCOVERING WHAT MATTERS through natural conversation, not filling a template</critical>
+<critical>Communicate all responses in {communication_language} and adapt deeply to {user_skill_level}</critical>
+<critical>Generate all documents in {document_output_language}</critical>
+<critical>LIVING DOCUMENT: Write to the document continuously as you discover - never wait until the end</critical>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
+
+## Input Document Discovery
+
+This workflow may reference: market research, brainstorming documents, user specified other inputs, or brownfield project documentation.
+
+**All input files are discovered and loaded automatically via the `discover_inputs` protocol in Step 0.5**
+
+After discovery completes, the following content variables will be available:
+
+- `{research_content}` - Market research or domain research documents
+- `{brainstorming_content}` - Brainstorming session outputs
+- `{document_project_content}` - Brownfield project documentation (intelligently loaded via INDEX_GUIDED strategy)
 
 <workflow>
 
-<step n="0" goal="Initialize product brief session">
-<action>Welcome the user to the Product Brief creation process</action>
-<action>Explain this is a collaborative process to define their product vision</action>
-<ask>Ask the user to provide the project name for this product brief</ask>
-<template-output>project_name</template-output>
+<step n="0" goal="Validate workflow readiness" tag="workflow-status">
+<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
+
+<action if="status file not found">Set standalone_mode = true</action>
+
+<check if="status file found">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Parse workflow_status section</action>
+  <action>Check status of "product-brief" workflow</action>
+  <action>Get project_level from YAML metadata</action>
+  <action>Find first non-completed workflow (next expected workflow)</action>
+
+  <check if="project_level < 2">
+    <output>**Note: Level {{project_level}} Project**
+
+Product Brief is most valuable for Level 2+ projects, but can help clarify vision for any project.</output>
+</check>
+
+  <check if="product-brief status is file path (already completed)">
+    <output>⚠️ Product Brief already completed: {{product-brief status}}</output>
+    <ask>Re-running will overwrite the existing brief. Continue? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Use workflow-status to see your next step.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <check if="product-brief is not the next expected workflow">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. Product Brief is out of sequence.</output>
+    <ask>Continue with Product Brief anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+<action>Set standalone_mode = false</action>
+</check>
 </step>
 
-<step n="1" goal="Gather available inputs and context">
-<action>Check what inputs the user has available:</action>
-<ask>Do you have any of these documents to help inform the brief?
-1. Market research
-2. Brainstorming results
-3. Competitive analysis
-4. Initial product ideas or notes
-5. None - let's start fresh
+<step n="0.5" goal="Discover and load input documents">
+<invoke-protocol name="discover_inputs" />
+</step>
 
-Please share any documents you have or select option 5.</ask>
+<step n="1" goal="Begin the journey and understand context">
+<action>Welcome {user_name} warmly in {communication_language}
 
-<action>Load and analyze any provided documents</action>
-<action>Extract key insights and themes from input documents</action>
+Adapt your tone to {user_skill_level}:
 
-<ask>Based on what you've shared (or if starting fresh), please tell me:
+- Expert: "Let's define your product vision. What are you building?"
+- Intermediate: "I'm here to help shape your product vision. Tell me about your idea."
+- Beginner: "Hi! I'm going to help you figure out exactly what you want to build. Let's start with your idea - what got you excited about this?"
 
-- What's the core problem you're trying to solve?
-- Who experiences this problem most acutely?
-- What sparked this product idea?</ask>
+Start with open exploration:
 
-<template-output>initial_context</template-output>
-</step>
+- What sparked this idea?
+- What are you hoping to build?
+- Who is this for - yourself, a business, users you know?
 
-<step n="2" goal="Choose collaboration mode">
-<ask>How would you like to work through the brief?
+CRITICAL: Listen for context clues that reveal their situation:
 
-**1. Interactive Mode** - We'll work through each section together, discussing and refining as we go
-**2. YOLO Mode** - I'll generate a complete draft based on our conversation so far, then we'll refine it together
+- Personal/hobby project (fun, learning, small audience)
+- Startup/solopreneur (market opportunity, competition matters)
+- Enterprise/corporate (stakeholders, compliance, strategic alignment)
+- Technical enthusiasm (implementation focused)
+- Business opportunity (market/revenue focused)
+- Problem frustration (solution focused)
 
-Which approach works best for you?</ask>
+Based on their initial response, sense:
 
-<action>Store the user's preference for mode</action>
-<template-output>collaboration_mode</template-output>
-</step>
+- How formal/casual they want to be
+- Whether they think in business or technical terms
+- If they have existing materials to share
+- Their confidence level with the domain</action>
 
-<step n="3" goal="Define the problem statement" if="collaboration_mode == 'interactive'">
-<ask>Let's dig deeper into the problem. Tell me:
-- What's the current state that frustrates users?
-- Can you quantify the impact? (time lost, money spent, opportunities missed)
-- Why do existing solutions fall short?
-- Why is solving this urgent now?</ask>
+<ask>What's the project name, and what got you excited about building this?</ask>
 
-<action>Challenge vague statements and push for specificity</action>
-<action>Help the user articulate measurable pain points</action>
-<action>Create a compelling problem statement with evidence</action>
+<action>From even this first exchange, create initial document sections</action>
+<template-output>project_name</template-output>
+<template-output>executive_summary</template-output>
 
-<template-output>problem_statement</template-output>
+<action>If they mentioned existing documents (research, brainstorming, etc.):
+
+- Load and analyze these materials
+- Extract key themes and insights
+- Reference these naturally in conversation: "I see from your research that..."
+- Use these to accelerate discovery, not repeat questions</action>
+
+<template-output>initial_vision</template-output>
 </step>
 
-<step n="4" goal="Develop the proposed solution" if="collaboration_mode == 'interactive'">
-<ask>Now let's shape your solution vision:
-- What's your core approach to solving this problem?
-- What makes your solution different from what exists?
-- Why will this succeed where others haven't?
-- Paint me a picture of the ideal user experience</ask>
+<step n="2" goal="Discover the problem worth solving">
+<action>Guide problem discovery through natural conversation
 
-<action>Focus on the "what" and "why", not implementation details</action>
-<action>Help articulate key differentiators</action>
-<action>Craft a clear solution vision</action>
+DON'T ask: "What problem does this solve?"
 
-<template-output>proposed_solution</template-output>
-</step>
+DO explore conversationally based on their context:
 
-<step n="5" goal="Identify target users" if="collaboration_mode == 'interactive'">
-<ask>Who exactly will use this product? Let's get specific:
+For hobby projects:
 
-For your PRIMARY users:
+- "What's annoying you that this would fix?"
+- "What would this make easier or more fun?"
+- "Show me what the experience is like today without this"
 
-- What's their demographic/professional profile?
-- What are they currently doing to solve this problem?
-- What specific pain points do they face?
-- What goals are they trying to achieve?
+For business ventures:
 
-Do you have a SECONDARY user segment? If so, let's define them too.</ask>
+- "Walk me through the frustration your users face today"
+- "What's the cost of this problem - time, money, opportunities?"
+- "Who's suffering most from this? Tell me about them"
+- "What solutions have people tried? Why aren't they working?"
 
-<action>Push beyond generic personas like "busy professionals"</action>
-<action>Create specific, actionable user profiles</action>
-<action>[VISUAL PLACEHOLDER: User persona cards or journey map would be valuable here]</action>
+For enterprise:
 
-<template-output>primary_user_segment</template-output>
-<template-output>secondary_user_segment</template-output>
-</step>
+- "What's driving the need for this internally?"
+- "Which teams/processes are most affected?"
+- "What's the business impact of not solving this?"
+- "Are there compliance or strategic drivers?"
 
-<step n="6" goal="Establish goals and success metrics" if="collaboration_mode == 'interactive'">
-<ask>What does success look like? Let's set SMART goals:
+Listen for depth cues:
 
-Business objectives (with measurable outcomes):
+- Brief answers → dig deeper with follow-ups
+- Detailed passion → let them flow, capture everything
+- Uncertainty → help them explore with examples
+- Multiple problems → help prioritize the core issue
 
-- Example: "Acquire 1000 paying users within 6 months"
-- Example: "Reduce customer support tickets by 40%"
+Adapt your response:
 
-User success metrics (behaviors/outcomes, not features):
+- If they struggle: offer analogies, examples, frameworks
+- If they're clear: validate and push for specifics
+- If they're technical: explore implementation challenges
+- If they're business-focused: quantify impact</action>
 
-- Example: "Users complete core task in under 2 minutes"
-- Example: "70% of users return weekly"
+<action>Immediately capture what emerges - even if preliminary</action>
+<template-output>problem_statement</template-output>
 
-What are your top 3-5 Key Performance Indicators?</ask>
+<check if="user mentioned metrics, costs, or business impact">
+  <action>Explore the measurable impact of the problem</action>
+  <template-output>problem_impact</template-output>
+</check>
 
-<action>Help formulate specific, measurable goals</action>
-<action>Distinguish between business and user success</action>
+<check if="user mentioned current solutions or competitors">
+  <action>Understand why existing solutions fall short</action>
+  <template-output>existing_solutions_gaps</template-output>
+</check>
 
-<template-output>business_objectives</template-output>
-<template-output>user_success_metrics</template-output>
-<template-output>key_performance_indicators</template-output>
+<action>Reflect understanding: "So the core issue is {{problem_summary}}, and {{impact_if_mentioned}}. Let me capture that..."</action>
 </step>
 
-<step n="7" goal="Define MVP scope" if="collaboration_mode == 'interactive'">
-<ask>Let's be ruthless about MVP scope.
+<step n="3" goal="Shape the solution vision">
+<action>Transition naturally from problem to solution
 
-What are the absolute MUST-HAVE features for launch?
+Based on their energy and context, explore:
 
-- Think: What's the minimum to validate your core hypothesis?
-- For each feature, why is it essential?
+For builders/makers:
 
-What tempting features need to wait for v2?
+- "How do you envision this working?"
+- "Walk me through the experience you want to create"
+- "What's the 'magic moment' when someone uses this?"
 
-- What would be nice but isn't critical?
-- What adds complexity without core value?
+For business minds:
 
-What would constitute a successful MVP launch?
+- "What's your unique approach to solving this?"
+- "How is this different from what exists today?"
+- "What makes this the RIGHT solution now?"
 
-[VISUAL PLACEHOLDER: Consider a feature priority matrix or MoSCoW diagram]</ask>
+For enterprise:
 
-<action>Challenge scope creep aggressively</action>
-<action>Push for true minimum viability</action>
-<action>Clearly separate must-haves from nice-to-haves</action>
+- "What would success look like for the organization?"
+- "How does this fit with existing systems/processes?"
+- "What's the transformation you're enabling?"
 
-<template-output>core_features</template-output>
-<template-output>out_of_scope</template-output>
-<template-output>mvp_success_criteria</template-output>
-</step>
+Go deeper based on responses:
 
-<step n="8" goal="Assess financial impact and ROI">
-<ask>Let's talk numbers and strategic value:
+- If innovative → explore the unique angle
+- If standard → focus on execution excellence
+- If technical → discuss key capabilities
+- If user-focused → paint the journey
 
-**Financial Considerations:**
+Web research when relevant:
 
-- What's the expected development investment (budget/resources)?
-- What's the revenue potential or cost savings opportunity?
-- When do you expect to reach break-even?
-- How does this align with available budget?
+- If they mention competitors → research current solutions
+- If they claim innovation → verify uniqueness
+- If they reference trends → get current data</action>
 
-**Strategic Alignment:**
+<action if="competitor or market mentioned">
+  <WebSearch>{{competitor/market}} latest features 2024</WebSearch>
+  <action>Use findings to sharpen differentiation discussion</action>
+</action>
 
-- Which company OKRs or strategic objectives does this support?
-- How does this advance key strategic initiatives?
-- What's the opportunity cost of NOT doing this?
-
-[VISUAL PLACEHOLDER: Consider adding a simple ROI projection chart here]</ask>
+<template-output>proposed_solution</template-output>
 
-<action>Help quantify financial impact where possible</action>
-<action>Connect to broader company strategy</action>
-<action>Document both tangible and intangible value</action>
+<check if="unique differentiation discussed">
+  <template-output>key_differentiators</template-output>
+</check>
 
-<template-output>financial_impact</template-output>
-<template-output>company_objectives_alignment</template-output>
-<template-output>strategic_initiatives</template-output>
+<action>Continue building the living document</action>
 </step>
 
-<step n="9" goal="Explore post-MVP vision" optional="true">
-<ask>Looking beyond MVP (optional but helpful):
+<step n="4" goal="Understand the people who need this">
+<action>Discover target users through storytelling, not demographics
 
-If the MVP succeeds, what comes next?
+Facilitate based on project type:
 
-- Phase 2 features?
-- Expansion opportunities?
-- Long-term vision (1-2 years)?
+Personal/hobby:
 
-This helps ensure MVP decisions align with future direction.</ask>
+- "Who else would love this besides you?"
+- "Tell me about someone who would use this"
+- Keep it light and informal
 
-<template-output>phase_2_features</template-output>
-<template-output>long_term_vision</template-output>
-<template-output>expansion_opportunities</template-output>
-</step>
+Startup/business:
+
+- "Describe your ideal first customer - not demographics, but their situation"
+- "What are they doing today without your solution?"
+- "What would make them say 'finally, someone gets it!'?"
+- "Are there different types of users with different needs?"
 
-<step n="10" goal="Document technical considerations">
-<ask>Let's capture technical context. These are preferences, not final decisions:
+Enterprise:
 
-Platform requirements:
+- "Which roles/departments will use this?"
+- "Walk me through their current workflow"
+- "Who are the champions vs skeptics?"
+- "What about indirect stakeholders?"
 
-- Web, mobile, desktop, or combination?
-- Browser/OS support needs?
-- Performance requirements?
-- Accessibility standards?
+Push beyond generic personas:
 
-Do you have technology preferences or constraints?
+- Not: "busy professionals" → "Sales reps who waste 2 hours/day on data entry"
+- Not: "tech-savvy users" → "Developers who know Docker but hate configuring it"
+- Not: "small businesses" → "Shopify stores doing $10-50k/month wanting to scale"
 
-- Frontend frameworks?
-- Backend preferences?
-- Database needs?
-- Infrastructure requirements?
+For each user type that emerges:
 
-Any existing systems to integrate with?</ask>
+- Current behavior/workflow
+- Specific frustrations
+- What they'd value most
+- Their technical comfort level</action>
+
+<template-output>primary_user_segment</template-output>
 
-<action>Check for technical-preferences.yaml file if available</action>
-<action>Note these are initial thoughts for PM and architect to consider</action>
+<check if="multiple user types mentioned">
+  <action>Explore secondary users only if truly different needs</action>
+  <template-output>secondary_user_segment</template-output>
+</check>
 
-<template-output>platform_requirements</template-output>
-<template-output>technology_preferences</template-output>
-<template-output>architecture_considerations</template-output>
+<check if="user journey or workflow discussed">
+  <template-output>user_journey</template-output>
+</check>
 </step>
 
-<step n="11" goal="Identify constraints and assumptions">
-<ask>Let's set realistic expectations:
+<step n="5" goal="Define what success looks like" repeat="adapt-to-context">
+<action>Explore success measures that match their context
+
+For personal projects:
+
+- "How will you know this is working well?"
+- "What would make you proud of this?"
+- Keep metrics simple and meaningful
+
+For startups:
 
-What constraints are you working within?
+- "What metrics would convince you this is taking off?"
+- "What user behaviors show they love it?"
+- "What business metrics matter most - users, revenue, retention?"
+- Push for specific targets: "100 users" not "lots of users"
 
-- Budget or resource limits?
-- Timeline or deadline pressures?
-- Team size and expertise?
-- Technical limitations?
+For enterprise:
 
-What assumptions are you making?
+- "How will the organization measure success?"
+- "What KPIs will stakeholders care about?"
+- "What are the must-hit metrics vs nice-to-haves?"
 
-- About user behavior?
-- About the market?
-- About technical feasibility?</ask>
+Only dive deep into metrics if they show interest
+Skip entirely for pure hobby projects
+Focus on what THEY care about measuring</action>
 
-<action>Document constraints clearly</action>
-<action>List assumptions to validate during development</action>
+<check if="metrics or goals discussed">
+  <template-output>success_metrics</template-output>
 
-<template-output>constraints</template-output>
-<template-output>key_assumptions</template-output>
+  <check if="business objectives mentioned">
+    <template-output>business_objectives</template-output>
+  </check>
+
+  <check if="KPIs matter to them">
+    <template-output>key_performance_indicators</template-output>
+  </check>
+</check>
+
+<action>Keep the document growing with each discovery</action>
 </step>
 
-<step n="12" goal="Assess risks and open questions" optional="true">
-<ask>What keeps you up at night about this project?
+<step n="6" goal="Discover the MVP scope">
+<critical>Focus on FEATURES not epics - that comes in Phase 2</critical>
 
-Key risks:
+<action>Guide MVP scoping based on their maturity
 
-- What could derail the project?
-- What's the impact if these risks materialize?
+For experimental/hobby:
 
-Open questions:
+- "What's the ONE thing this must do to be useful?"
+- "What would make a fun first version?"
+- Embrace simplicity
 
-- What do you still need to figure out?
-- What needs more research?
+For business ventures:
 
-[VISUAL PLACEHOLDER: Risk/impact matrix could help prioritize]
+- "What's the smallest version that proves your hypothesis?"
+- "What features would make early adopters say 'good enough'?"
+- "What's tempting to add but would slow you down?"
+- Be ruthless about scope creep
 
-Being honest about unknowns helps us prepare.</ask>
+For enterprise:
 
-<template-output>key_risks</template-output>
-<template-output>open_questions</template-output>
-<template-output>research_areas</template-output>
-</step>
+- "What's the pilot scope that demonstrates value?"
+- "Which capabilities are must-have for initial rollout?"
+- "What can we defer to Phase 2?"
 
-<!-- YOLO Mode - Generate everything then refine -->
-<step n="3" goal="Generate complete brief draft" if="collaboration_mode == 'yolo'">
-<action>Based on initial context and any provided documents, generate a complete product brief covering all sections</action>
-<action>Make reasonable assumptions where information is missing</action>
-<action>Flag areas that need user validation with [NEEDS CONFIRMATION] tags</action>
+Use this framing:
+
+- Core features: "Without this, the product doesn't work"
+- Nice-to-have: "This would be great, but we can launch without it"
+- Future vision: "This is where we're headed eventually"
+
+Challenge feature creep:
+
+- "Do we need that for launch, or could it come later?"
+- "What if we started without that - what breaks?"
+- "Is this core to proving the concept?"</action>
 
-<template-output>problem_statement</template-output>
-<template-output>proposed_solution</template-output>
-<template-output>primary_user_segment</template-output>
-<template-output>secondary_user_segment</template-output>
-<template-output>business_objectives</template-output>
-<template-output>user_success_metrics</template-output>
-<template-output>key_performance_indicators</template-output>
 <template-output>core_features</template-output>
-<template-output>out_of_scope</template-output>
-<template-output>mvp_success_criteria</template-output>
-<template-output>phase_2_features</template-output>
-<template-output>long_term_vision</template-output>
-<template-output>expansion_opportunities</template-output>
-<template-output>financial_impact</template-output>
-<template-output>company_objectives_alignment</template-output>
-<template-output>strategic_initiatives</template-output>
-<template-output>platform_requirements</template-output>
-<template-output>technology_preferences</template-output>
-<template-output>architecture_considerations</template-output>
-<template-output>constraints</template-output>
-<template-output>key_assumptions</template-output>
-<template-output>key_risks</template-output>
-<template-output>open_questions</template-output>
-<template-output>research_areas</template-output>
-
-<action>Present the complete draft to the user</action>
-<ask>Here's the complete brief draft. What would you like to adjust or refine?</ask>
+
+<check if="scope creep discussed">
+  <template-output>out_of_scope</template-output>
+</check>
+
+<check if="future features mentioned">
+  <template-output>future_vision_features</template-output>
+</check>
+
+<check if="success criteria for MVP mentioned">
+  <template-output>mvp_success_criteria</template-output>
+</check>
 </step>
 
-<step n="4" goal="Refine brief sections" repeat="until-approved" if="collaboration_mode == 'yolo'">
-<ask>Which section would you like to refine?
-1. Problem Statement
-2. Proposed Solution
-3. Target Users
-4. Goals & Metrics
-5. MVP Scope
-6. Post-MVP Vision
-7. Financial Impact & Strategic Alignment
-8. Technical Considerations
-9. Constraints & Assumptions
-10. Risks & Questions
-11. Save and continue</ask>
-
-<action>Work with user to refine selected section</action>
-<action>Update relevant template outputs</action>
+<step n="7" goal="Explore relevant context dimensions" repeat="until-natural-end">
+<critical>Only explore what emerges naturally - skip what doesn't matter</critical>
+
+<action>Based on the conversation so far, selectively explore:
+
+IF financial aspects emerged:
+
+- Development investment needed
+- Revenue potential or cost savings
+- ROI timeline
+- Budget constraints
+  <check if="discussed">
+  <template-output>financial_considerations</template-output>
+  </check>
+
+IF market competition mentioned:
+
+- Competitive landscape
+- Market opportunity size
+- Differentiation strategy
+- Market timing
+  <check if="discussed">
+  <WebSearch>{{market}} size trends 2024</WebSearch>
+  <template-output>market_analysis</template-output>
+  </check>
+
+IF technical preferences surfaced:
+
+- Platform choices (web/mobile/desktop)
+- Technology stack preferences
+- Integration needs
+- Performance requirements
+  <check if="discussed">
+  <template-output>technical_preferences</template-output>
+  </check>
+
+IF organizational context emerged:
+
+- Strategic alignment
+- Stakeholder buy-in needs
+- Change management considerations
+- Compliance requirements
+  <check if="discussed">
+  <template-output>organizational_context</template-output>
+  </check>
+
+IF risks or concerns raised:
+
+- Key risks and mitigation
+- Critical assumptions
+- Open questions needing research
+  <check if="discussed">
+  <template-output>risks_and_assumptions</template-output>
+  </check>
+
+IF timeline pressures mentioned:
+
+- Launch timeline
+- Critical milestones
+- Dependencies
+  <check if="discussed">
+  <template-output>timeline_constraints</template-output>
+  </check>
+
+Skip anything that hasn't naturally emerged
+Don't force sections that don't fit their context</action>
 </step>
 
-<!-- Final steps for both modes -->
-<step n="13" goal="Create executive summary">
-<action>Synthesize all sections into a compelling executive summary</action>
-<action>Include:
-- Product concept in 1-2 sentences
-- Primary problem being solved
-- Target market identification
-- Key value proposition</action>
+<step n="8" goal="Refine and complete the living document">
+<action>Review what's been captured with the user
+
+"Let me show you what we've built together..."
+
+Present the actual document sections created so far
+
+- Not a summary, but the real content
+- Shows the document has been growing throughout
 
+Ask:
+"Looking at this, what stands out as most important to you?"
+"Is there anything critical we haven't explored?"
+"Does this capture your vision?"
+
+Based on their response:
+
+- Refine sections that need more depth
+- Add any missing critical elements
+- Remove or simplify sections that don't matter
+- Ensure the document fits THEIR needs, not a template</action>
+
+<action>Make final refinements based on feedback</action>
+<template-output>final_refinements</template-output>
+
+<action>Create executive summary that captures the essence</action>
 <template-output>executive_summary</template-output>
 </step>
+<step n="9" goal="Complete and save the product brief">
+<action>The document has been building throughout our conversation
+Now ensure it's complete and well-organized</action>
+
+<check if="research documents were provided">
+  <action>Append summary of incorporated research</action>
+  <template-output>supporting_materials</template-output>
+</check>
+
+<action>Ensure the document structure makes sense for what was discovered:
+
+- Hobbyist projects might be 2-3 pages focused on problem/solution/features
+- Startup ventures might be 5-7 pages with market analysis and metrics
+- Enterprise briefs might be 10+ pages with full strategic context
 
-<step n="14" goal="Compile supporting materials">
-<action>If research documents were provided, create a summary of key findings</action>
-<action>Document any stakeholder input received during the process</action>
-<action>Compile list of reference documents and resources</action>
+The document should reflect their world, not force their world into a template</action>
 
-<template-output>research_summary</template-output>
-<template-output>stakeholder_input</template-output>
-<template-output>references</template-output>
+<ask>Your product brief is ready! Would you like to:
+
+1. Review specific sections together
+2. Make any final adjustments
+3. Save and move forward
+
+What feels right?</ask>
+
+<action>Make any requested refinements</action>
+<template-output>final_document</template-output>
 </step>
 
-<step n="15" goal="Final review and handoff">
-<action>Generate the complete product brief document</action>
-<action>Review all sections for completeness and consistency</action>
-<action>Flag any areas that need PM attention with [PM-TODO] tags</action>
+<check if="standalone_mode != true">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Find workflow_status key "product-brief"</action>
+  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+  <action>Update workflow_status["product-brief"] = "{output_folder}/bmm-product-brief-{{project_name}}-{{date}}.md"</action>
+  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+<action>Determine next agent from path file based on next workflow</action>
+</check>
+
+<output>**✅ Product Brief Complete, {user_name}!**
+
+Your product vision has been captured in a document that reflects what matters most for your {{context_type}} project.
+
+**Document saved:** {output_folder}/bmm-product-brief-{{project_name}}-{{date}}.md
 
-<ask>The product brief is complete! Would you like to:
+{{#if standalone_mode != true}}
+**What's next:** {{next_workflow}} ({{next_agent}} agent)
 
-1. Review the entire document
-2. Make final adjustments
-3. Save and prepare for handoff to PM
+The next phase will take your brief and create the detailed planning artifacts needed for implementation.
+{{else}}
+**Next steps:**
 
-This brief will serve as the primary input for creating the Product Requirements Document (PRD).</ask>
+- Run `workflow-init` to set up guided workflow tracking
+- Or proceed directly to the PRD workflow if you know your path
+  {{/if}}
 
-<template-output>final_brief</template-output>
+Remember: This brief captures YOUR vision. It grew from our conversation, not from a rigid template. It's ready to guide the next phase of bringing your idea to life.
+</output>
 </step>
 
 </workflow>