BoMB updates

2025-10-04 00:22:59 -05:00
parent 9e8c7f3503
commit 5ee4cf535c
326 changed files with 39464 additions and 402 deletions
--- a/bmad/bmm/workflows/1-analysis/product-brief/README.md
+++ b/bmad/bmm/workflows/1-analysis/product-brief/README.md
@@ -0,0 +1,180 @@
+# Product Brief Workflow
+
+## Overview
+
+Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration. Supports both structured interactive mode and rapid "YOLO" mode for quick draft generation.
+
+## Key Features
+
+- **Dual Mode Operation** - Interactive step-by-step or rapid draft generation
+- **Multi-Input Support** - Integrates market research, competitive analysis, and brainstorming results
+- **Conversational Design** - Guides users through strategic thinking with probing questions
+- **Executive Summary Generation** - Creates compelling summaries for stakeholder communication
+- **Comprehensive Coverage** - Addresses all critical product planning dimensions
+- **Stakeholder Ready** - Generates professional briefs suitable for PM handoff
+
+## Usage
+
+### Basic Invocation
+
+```bash
+workflow product-brief
+```
+
+### With Input Documents
+
+```bash
+# With market research
+workflow product-brief --input market-research.md
+
+# With multiple inputs
+workflow product-brief --input market-research.md --input competitive-analysis.md
+```
+
+### Configuration
+
+- **brief_format**: "comprehensive" (full detail) or "executive" (3-page limit)
+- **autonomous**: false (requires user collaboration)
+- **output_folder**: Location for generated brief
+
+## Workflow Structure
+
+### Files Included
+
+```
+product-brief/
+├── workflow.yaml           # Configuration and metadata
+├── instructions.md         # Interactive workflow steps
+├── template.md            # Product brief document structure
+├── checklist.md           # Validation criteria
+└── README.md              # This file
+```
+
+## Workflow Process
+
+### Phase 1: Initialization and Context (Steps 0-2)
+
+- **Project Setup**: Captures project name and basic context
+- **Input Gathering**: Collects and analyzes available documents
+- **Mode Selection**: Chooses interactive or YOLO collaboration approach
+- **Context Extraction**: Identifies core problems and opportunities
+
+### Phase 2: Interactive Development (Steps 3-12) - Interactive Mode
+
+- **Problem Definition**: Deep dive into user pain points and market gaps
+- **Solution Articulation**: Develops clear value proposition and approach
+- **User Segmentation**: Defines primary and secondary target audiences
+- **Success Metrics**: Establishes measurable goals and KPIs
+- **MVP Scoping**: Ruthlessly defines minimum viable features
+- **Financial Planning**: Assesses ROI and strategic alignment
+- **Technical Context**: Captures platform and technology considerations
+- **Risk Assessment**: Identifies constraints, assumptions, and unknowns
+
+### Phase 3: Rapid Generation (Steps 3-4) - YOLO Mode
+
+- **Complete Draft**: Generates full brief based on initial context
+- **Iterative Refinement**: User-guided section improvements
+- **Quality Validation**: Ensures completeness and consistency
+
+### Phase 4: Finalization (Steps 13-15)
+
+- **Executive Summary**: Creates compelling overview for stakeholders
+- **Supporting Materials**: Compiles research summaries and references
+- **Final Review**: Quality check and handoff preparation
+
+## Output
+
+### Generated Files
+
+- **Primary output**: product-brief-{project_name}-{date}.md
+- **Supporting files**: Research summaries and stakeholder input documentation
+
+### Output Structure
+
+1. **Executive Summary** - High-level product concept and value proposition
+2. **Problem Statement** - Detailed problem analysis with evidence
+3. **Proposed Solution** - Core approach and key differentiators
+4. **Target Users** - Primary and secondary user segments with personas
+5. **Goals and Success Metrics** - Business objectives and measurable KPIs
+6. **MVP Scope** - Must-have features and out-of-scope items
+7. **Post-MVP Vision** - Phase 2 features and long-term roadmap
+8. **Financial Impact** - Investment requirements and ROI projections
+9. **Strategic Alignment** - Connection to company OKRs and initiatives
+10. **Technical Considerations** - Platform requirements and preferences
+11. **Constraints and Assumptions** - Resource limits and key assumptions
+12. **Risks and Open Questions** - Risk assessment and research needs
+13. **Supporting Materials** - Research summaries and references
+
+## Requirements
+
+No special requirements - designed to work with or without existing documentation.
+
+## Best Practices
+
+### Before Starting
+
+1. **Gather Available Research**: Collect any market research, competitive analysis, or user feedback
+2. **Define Stakeholder Audience**: Know who will use this brief for decision-making
+3. **Set Time Boundaries**: Interactive mode requires 60-90 minutes for quality results
+
+### During Execution
+
+1. **Be Specific**: Avoid generic statements - provide concrete examples and data
+2. **Think Strategically**: Focus on "why" and "what" rather than "how"
+3. **Challenge Assumptions**: Use the conversation to test and refine your thinking
+4. **Scope Ruthlessly**: Resist feature creep in MVP definition
+
+### After Completion
+
+1. **Validate with Checklist**: Use included criteria to ensure completeness
+2. **Stakeholder Review**: Share executive summary first, then full brief
+3. **Iterate Based on Feedback**: Product briefs should evolve with new insights
+
+## Troubleshooting
+
+### Common Issues
+
+**Issue**: Brief lacks specificity or contains vague statements
+
+- **Solution**: Restart problem definition with concrete examples and measurable impacts
+- **Check**: Ensure each section answers "so what?" and provides actionable insights
+
+**Issue**: MVP scope is too large or undefined
+
+- **Solution**: Use the "what's the minimum to validate core hypothesis?" filter
+- **Check**: Verify that each MVP feature is truly essential for initial value delivery
+
+**Issue**: Missing strategic context or business justification
+
+- **Solution**: Return to financial impact and strategic alignment sections
+- **Check**: Ensure connection to company goals and clear ROI potential
+
+## Customization
+
+To customize this workflow:
+
+1. **Modify Questions**: Update instructions.md to add industry-specific or company-specific prompts
+2. **Adjust Template**: Customize template.md sections for organizational brief standards
+3. **Add Validation**: Extend checklist.md with company-specific quality criteria
+4. **Configure Modes**: Adjust brief_format settings for different output styles
+
+## Version History
+
+- **v6.0.0** - Interactive conversational design with dual modes
+  - Interactive and YOLO mode support
+  - Multi-input document integration
+  - Executive summary generation
+  - Strategic alignment focus
+
+## Support
+
+For issues or questions:
+
+- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Validate output using `checklist.md`
+- Consider running market research workflow first if lacking business context
+- Consult BMAD documentation for product planning methodology
+
+---
+
+_Part of the BMad Method v6 - BMM (Method) Module_
--- a/bmad/bmm/workflows/1-analysis/product-brief/checklist.md
+++ b/bmad/bmm/workflows/1-analysis/product-brief/checklist.md
@@ -0,0 +1,115 @@
+# Product Brief Validation Checklist
+
+## Document Structure
+
+- [ ] All required sections are present (Executive Summary through Appendices)
+- [ ] No placeholder text remains (e.g., [TODO], [NEEDS CONFIRMATION], {{variable}})
+- [ ] Document follows the standard brief template format
+- [ ] Sections are properly numbered and formatted with headers
+- [ ] Cross-references between sections are accurate
+
+## Executive Summary Quality
+
+- [ ] Product concept is explained in 1-2 clear sentences
+- [ ] Primary problem is clearly identified
+- [ ] Target market is specifically named (not generic)
+- [ ] Value proposition is compelling and differentiated
+- [ ] Summary accurately reflects the full document content
+
+## Problem Statement
+
+- [ ] Current state pain points are specific and measurable
+- [ ] Impact is quantified where possible (time, money, opportunities)
+- [ ] Explanation of why existing solutions fall short is provided
+- [ ] Urgency for solving the problem now is justified
+- [ ] Problem is validated with evidence or data points
+
+## Solution Definition
+
+- [ ] Core approach is clearly explained without implementation details
+- [ ] Key differentiators from existing solutions are identified
+- [ ] Explanation of why this will succeed is compelling
+- [ ] Solution aligns directly with stated problems
+- [ ] Vision paints a clear picture of the user experience
+
+## Target Users
+
+- [ ] Primary user segment has specific demographic/firmographic profile
+- [ ] User behaviors and current workflows are documented
+- [ ] Specific pain points are tied to user segments
+- [ ] User goals are clearly articulated
+- [ ] Secondary segment (if applicable) is equally detailed
+- [ ] Avoids generic personas like "busy professionals"
+
+## Goals and Metrics
+
+- [ ] Business objectives include measurable outcomes with targets
+- [ ] User success metrics focus on behaviors, not features
+- [ ] 3-5 KPIs are defined with clear definitions
+- [ ] All goals follow SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound)
+- [ ] Success metrics align with problem statement
+
+## MVP Scope
+
+- [ ] Core features list contains only true must-haves
+- [ ] Each core feature includes rationale for why it's essential
+- [ ] Out of scope section explicitly lists deferred features
+- [ ] MVP success criteria are specific and measurable
+- [ ] Scope is genuinely minimal and viable
+- [ ] No feature creep evident in "must-have" list
+
+## Technical Considerations
+
+- [ ] Target platforms are specified (web/mobile/desktop)
+- [ ] Browser/OS support requirements are documented
+- [ ] Performance requirements are defined if applicable
+- [ ] Accessibility requirements are noted
+- [ ] Technology preferences are marked as preferences, not decisions
+- [ ] Integration requirements with existing systems are identified
+
+## Constraints and Assumptions
+
+- [ ] Budget constraints are documented if known
+- [ ] Timeline or deadline pressures are specified
+- [ ] Team/resource limitations are acknowledged
+- [ ] Technical constraints are clearly stated
+- [ ] Key assumptions are listed and testable
+- [ ] Assumptions will be validated during development
+
+## Risk Assessment (if included)
+
+- [ ] Key risks include potential impact descriptions
+- [ ] Open questions are specific and answerable
+- [ ] Research areas are identified with clear objectives
+- [ ] Risk mitigation strategies are suggested where applicable
+
+## Overall Quality
+
+- [ ] Language is clear and free of jargon
+- [ ] Terminology is used consistently throughout
+- [ ] Document is ready for handoff to Product Manager
+- [ ] All [PM-TODO] items are clearly marked if present
+- [ ] References and source documents are properly cited
+
+## Completeness Check
+
+- [ ] Document provides sufficient detail for PRD creation
+- [ ] All user inputs have been incorporated
+- [ ] Market research findings are reflected if provided
+- [ ] Competitive analysis insights are included if available
+- [ ] Brief aligns with overall product strategy
+
+## Final Validation
+
+### Critical Issues Found:
+
+- [ ] None identified
+
+### Minor Issues to Address:
+
+- [ ] List any minor issues here
+
+### Ready for PM Handoff:
+
+- [ ] Yes, brief is complete and validated
+- [ ] No, requires additional work (specify above)
--- a/bmad/bmm/workflows/1-analysis/product-brief/instructions.md
+++ b/bmad/bmm/workflows/1-analysis/product-brief/instructions.md
@@ -0,0 +1,353 @@
+# Product Brief - Interactive Workflow Instructions
+
+<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+
+<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>
+
+<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
+
+Please share any documents you have or select option 5.</ask>
+
+<action>Load and analyze any provided documents</action>
+<action>Extract key insights and themes from input documents</action>
+
+<ask>Based on what you've shared (or if starting fresh), please tell me:
+
+- What's the core problem you're trying to solve?
+- Who experiences this problem most acutely?
+- What sparked this product idea?</ask>
+
+<template-output>initial_context</template-output>
+</step>
+
+<step n="2" goal="Choose collaboration mode">
+<ask>How would you like to work through the brief?
+
+**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
+
+Which approach works best for you?</ask>
+
+<action>Store the user's preference for mode</action>
+<template-output>collaboration_mode</template-output>
+</step>
+
+<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>
+
+<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>
+
+<template-output>problem_statement</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>
+
+<action>Focus on the "what" and "why", not implementation details</action>
+<action>Help articulate key differentiators</action>
+<action>Craft a clear solution vision</action>
+
+<template-output>proposed_solution</template-output>
+</step>
+
+<step n="5" goal="Identify target users" if="collaboration_mode == 'interactive'">
+<ask>Who exactly will use this product? Let's get specific:
+
+For your PRIMARY users:
+
+- 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?
+
+Do you have a SECONDARY user segment? If so, let's define them too.</ask>
+
+<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>
+
+<template-output>primary_user_segment</template-output>
+<template-output>secondary_user_segment</template-output>
+</step>
+
+<step n="6" goal="Establish goals and success metrics" if="collaboration_mode == 'interactive'">
+<ask>What does success look like? Let's set SMART goals:
+
+Business objectives (with measurable outcomes):
+
+- Example: "Acquire 1000 paying users within 6 months"
+- Example: "Reduce customer support tickets by 40%"
+
+User success metrics (behaviors/outcomes, not features):
+
+- Example: "Users complete core task in under 2 minutes"
+- Example: "70% of users return weekly"
+
+What are your top 3-5 Key Performance Indicators?</ask>
+
+<action>Help formulate specific, measurable goals</action>
+<action>Distinguish between business and user success</action>
+
+<template-output>business_objectives</template-output>
+<template-output>user_success_metrics</template-output>
+<template-output>key_performance_indicators</template-output>
+</step>
+
+<step n="7" goal="Define MVP scope" if="collaboration_mode == 'interactive'">
+<ask>Let's be ruthless about MVP scope.
+
+What are the absolute MUST-HAVE features for launch?
+
+- Think: What's the minimum to validate your core hypothesis?
+- For each feature, why is it essential?
+
+What tempting features need to wait for v2?
+
+- What would be nice but isn't critical?
+- What adds complexity without core value?
+
+What would constitute a successful MVP launch?
+
+[VISUAL PLACEHOLDER: Consider a feature priority matrix or MoSCoW diagram]</ask>
+
+<action>Challenge scope creep aggressively</action>
+<action>Push for true minimum viability</action>
+<action>Clearly separate must-haves from nice-to-haves</action>
+
+<template-output>core_features</template-output>
+<template-output>out_of_scope</template-output>
+<template-output>mvp_success_criteria</template-output>
+</step>
+
+<step n="8" goal="Assess financial impact and ROI">
+<ask>Let's talk numbers and strategic value:
+
+**Financial Considerations:**
+
+- 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?
+
+**Strategic Alignment:**
+
+- 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>
+
+<action>Help quantify financial impact where possible</action>
+<action>Connect to broader company strategy</action>
+<action>Document both tangible and intangible value</action>
+
+<template-output>financial_impact</template-output>
+<template-output>company_objectives_alignment</template-output>
+<template-output>strategic_initiatives</template-output>
+</step>
+
+<step n="9" goal="Explore post-MVP vision" optional="true">
+<ask>Looking beyond MVP (optional but helpful):
+
+If the MVP succeeds, what comes next?
+
+- Phase 2 features?
+- Expansion opportunities?
+- Long-term vision (1-2 years)?
+
+This helps ensure MVP decisions align with future direction.</ask>
+
+<template-output>phase_2_features</template-output>
+<template-output>long_term_vision</template-output>
+<template-output>expansion_opportunities</template-output>
+</step>
+
+<step n="10" goal="Document technical considerations">
+<ask>Let's capture technical context. These are preferences, not final decisions:
+
+Platform requirements:
+
+- Web, mobile, desktop, or combination?
+- Browser/OS support needs?
+- Performance requirements?
+- Accessibility standards?
+
+Do you have technology preferences or constraints?
+
+- Frontend frameworks?
+- Backend preferences?
+- Database needs?
+- Infrastructure requirements?
+
+Any existing systems to integrate with?</ask>
+
+<action>Check for technical-preferences.yaml file if available</action>
+<action>Note these are initial thoughts for PM and architect to consider</action>
+
+<template-output>platform_requirements</template-output>
+<template-output>technology_preferences</template-output>
+<template-output>architecture_considerations</template-output>
+</step>
+
+<step n="11" goal="Identify constraints and assumptions">
+<ask>Let's set realistic expectations:
+
+What constraints are you working within?
+
+- Budget or resource limits?
+- Timeline or deadline pressures?
+- Team size and expertise?
+- Technical limitations?
+
+What assumptions are you making?
+
+- About user behavior?
+- About the market?
+- About technical feasibility?</ask>
+
+<action>Document constraints clearly</action>
+<action>List assumptions to validate during development</action>
+
+<template-output>constraints</template-output>
+<template-output>key_assumptions</template-output>
+</step>
+
+<step n="12" goal="Assess risks and open questions" optional="true">
+<ask>What keeps you up at night about this project?
+
+Key risks:
+
+- What could derail the project?
+- What's the impact if these risks materialize?
+
+Open questions:
+
+- What do you still need to figure out?
+- What needs more research?
+
+[VISUAL PLACEHOLDER: Risk/impact matrix could help prioritize]
+
+Being honest about unknowns helps us prepare.</ask>
+
+<template-output>key_risks</template-output>
+<template-output>open_questions</template-output>
+<template-output>research_areas</template-output>
+</step>
+
+<!-- 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>
+
+<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>
+</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 and Metrics
+5. MVP Scope
+6. Post-MVP Vision
+7. Financial Impact and Strategic Alignment
+8. Technical Considerations
+9. Constraints and Assumptions
+10. Risks and Questions
+11. Save and continue</ask>
+
+<action>Work with user to refine selected section</action>
+<action>Update relevant template outputs</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>
+
+<template-output>executive_summary</template-output>
+</step>
+
+<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>
+
+<template-output>research_summary</template-output>
+<template-output>stakeholder_input</template-output>
+<template-output>references</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>
+
+<ask>The product brief is complete! Would you like to:
+
+1. Review the entire document
+2. Make final adjustments
+3. Save and prepare for handoff to PM
+
+This brief will serve as the primary input for creating the Product Requirements Document (PRD).</ask>
+
+<template-output>final_brief</template-output>
+</step>
+
+</workflow>
--- a/bmad/bmm/workflows/1-analysis/product-brief/template.md
+++ b/bmad/bmm/workflows/1-analysis/product-brief/template.md
@@ -0,0 +1,165 @@
+# Product Brief: {{project_name}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+**Status:** Draft for PM Review
+
+---
+
+## Executive Summary
+
+{{executive_summary}}
+
+---
+
+## Problem Statement
+
+{{problem_statement}}
+
+---
+
+## Proposed Solution
+
+{{proposed_solution}}
+
+---
+
+## Target Users
+
+### Primary User Segment
+
+{{primary_user_segment}}
+
+### Secondary User Segment
+
+{{secondary_user_segment}}
+
+---
+
+## Goals and Success Metrics
+
+### Business Objectives
+
+{{business_objectives}}
+
+### User Success Metrics
+
+{{user_success_metrics}}
+
+### Key Performance Indicators (KPIs)
+
+{{key_performance_indicators}}
+
+---
+
+## Strategic Alignment and Financial Impact
+
+### Financial Impact
+
+{{financial_impact}}
+
+### Company Objectives Alignment
+
+{{company_objectives_alignment}}
+
+### Strategic Initiatives
+
+{{strategic_initiatives}}
+
+---
+
+## MVP Scope
+
+### Core Features (Must Have)
+
+{{core_features}}
+
+### Out of Scope for MVP
+
+{{out_of_scope}}
+
+### MVP Success Criteria
+
+{{mvp_success_criteria}}
+
+---
+
+## Post-MVP Vision
+
+### Phase 2 Features
+
+{{phase_2_features}}
+
+### Long-term Vision
+
+{{long_term_vision}}
+
+### Expansion Opportunities
+
+{{expansion_opportunities}}
+
+---
+
+## Technical Considerations
+
+### Platform Requirements
+
+{{platform_requirements}}
+
+### Technology Preferences
+
+{{technology_preferences}}
+
+### Architecture Considerations
+
+{{architecture_considerations}}
+
+---
+
+## Constraints and Assumptions
+
+### Constraints
+
+{{constraints}}
+
+### Key Assumptions
+
+{{key_assumptions}}
+
+---
+
+## Risks and Open Questions
+
+### Key Risks
+
+{{key_risks}}
+
+### Open Questions
+
+{{open_questions}}
+
+### Areas Needing Further Research
+
+{{research_areas}}
+
+---
+
+## Appendices
+
+### A. Research Summary
+
+{{research_summary}}
+
+### B. Stakeholder Input
+
+{{stakeholder_input}}
+
+### C. References
+
+{{references}}
+
+---
+
+_This Product Brief serves as the foundational input for Product Requirements Document (PRD) creation._
+
+_Next Steps: Handoff to Product Manager for PRD development using the `workflow prd` command._
--- a/bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml
+++ b/bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml
@@ -0,0 +1,30 @@
+# Product Brief - Interactive Workflow Configuration
+name: product-brief
+description: "Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration"
+author: "BMad"
+
+# Critical variables
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+date: system-generated
+
+# Optional input documents
+recommended_inputs:
+  - market_research: "Market research document (optional)"
+  - brainstorming_results: "Brainstorming session outputs (optional)"
+  - competitive_analysis: "Competitive analysis (optional)"
+  - initial_ideas: "Initial product ideas or notes (optional)"
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/product-brief"
+template: "{installed_path}/template.md"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Output configuration
+default_output_file: "{output_folder}/product-brief-{{project_name}}-{{date}}.md"
+
+# Workflow settings
+autonomous: false # This is an interactive workflow requiring user collaboration
+brief_format: "comprehensive" # Options: "comprehensive" (full detail) or "executive" (3-page limit)