Product Brief - Interactive Workflow Instructions

The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {installed_path}/workflow.yaml

Search {output_folder}/ for files matching pattern: bmm-workflow-status.md Find the most recent file (by date in filename: bmm-workflow-status.md)

Load the status file Set status_file_found = true Store status_file_path for later updates

No workflow status file found.

This workflow creates a Product Brief document (optional Phase 1 workflow).

Options:

Run workflow-status first to create the status file (recommended for progress tracking)
Continue in standalone mode (no progress tracking)
Exit

What would you like to do? If user chooses option 1 → HALT with message: “Please run workflow-status first, then return to product-brief” If user chooses option 2 → Set standalone_mode = true and continue If user chooses option 3 → HALT

Welcome the user to the Product Brief creation process Explain this is a collaborative process to define their product vision Ask the user to provide the project name for this product brief <template-output>project_name</template-output>

Check what inputs the user has available: 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.

Load and analyze any provided documents Extract key insights and themes from input documents

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?

<template-output>initial_context</template-output>

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?

Store the user’s preference for mode <template-output>collaboration_mode</template-output>

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?

Challenge vague statements and push for specificity Help the user articulate measurable pain points Create a compelling problem statement with evidence

<template-output>problem_statement</template-output>

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

Focus on the “what” and “why”, not implementation details Help articulate key differentiators Craft a clear solution vision

<template-output>proposed_solution</template-output>

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.

Push beyond generic personas like “busy professionals” Create specific, actionable user profiles [VISUAL PLACEHOLDER: User persona cards or journey map would be valuable here]

<template-output>primary_user_segment</template-output> <template-output>secondary_user_segment</template-output>

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?

Help formulate specific, measurable goals Distinguish between business and user success

<template-output>business_objectives</template-output> <template-output>user_success_metrics</template-output> <template-output>key_performance_indicators</template-output>

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]

Challenge scope creep aggressively Push for true minimum viability Clearly separate must-haves from nice-to-haves

<template-output>core_features</template-output> <template-output>out_of_scope</template-output> <template-output>mvp_success_criteria</template-output>

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]

Help quantify financial impact where possible Connect to broader company strategy Document both tangible and intangible value

<template-output>financial_impact</template-output> <template-output>company_objectives_alignment</template-output> <template-output>strategic_initiatives</template-output>

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.

<template-output>phase_2_features</template-output> <template-output>long_term_vision</template-output> <template-output>expansion_opportunities</template-output>

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?

Check for technical-preferences.yaml file if available Note these are initial thoughts for PM and architect to consider

<template-output>platform_requirements</template-output> <template-output>technology_preferences</template-output> <template-output>architecture_considerations</template-output>

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?

Document constraints clearly List assumptions to validate during development

<template-output>constraints</template-output> <template-output>key_assumptions</template-output>

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.

<template-output>key_risks</template-output> <template-output>open_questions</template-output> <template-output>research_areas</template-output>

Based on initial context and any provided documents, generate a complete product brief covering all sections Make reasonable assumptions where information is missing Flag areas that need user validation with [NEEDS CONFIRMATION] tags

<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>

Present the complete draft to the user Here’s the complete brief draft. What would you like to adjust or refine?

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

Work with user to refine selected section Update relevant template outputs

Synthesize all sections into a compelling executive summary Include: - Product concept in 1-2 sentences - Primary problem being solved - Target market identification - Key value proposition

<template-output>executive_summary</template-output>

If research documents were provided, create a summary of key findings Document any stakeholder input received during the process Compile list of reference documents and resources

<template-output>research_summary</template-output> <template-output>stakeholder_input</template-output> <template-output>references</template-output>

Generate the complete product brief document Review all sections for completeness and consistency Flag any areas that need PM attention with [PM-TODO] tags

The product brief is complete! Would you like to:

Review the entire document
Make final adjustments
Save and prepare for handoff to PM

This brief will serve as the primary input for creating the Product Requirements Document (PRD).

<template-output>final_brief</template-output>

Search {output_folder}/ for files matching pattern: bmm-workflow-status.md Find the most recent file (by date in filename)

Load the status file

<template-output file=“{{status_file_path}}”>current_step</template-output> Set to: “product-brief”

<template-output file=“{{status_file_path}}”>current_workflow</template-output> Set to: “product-brief - Complete”

<template-output file=“{{status_file_path}}”>progress_percentage</template-output> Increment by: 10% (optional Phase 1 workflow)

<template-output file=“{{status_file_path}}”>decisions_log</template-output> Add entry:

- **{{date}}**: Completed product-brief workflow. Product brief document generated and saved. Next: Proceed to plan-project workflow to create Product Requirements Document (PRD).

✅ Product Brief Complete

Brief Document:

Product brief saved and ready for handoff

Status file updated:

Current step: product-brief ✓
Progress: {{new_progress_percentage}}%

Next Steps:

Review the product brief document
Gather any additional stakeholder input
Run plan-project workflow to create PRD from this brief

Check status anytime with: workflow-status

✅ Product Brief Complete

Brief Document:

Product brief saved and ready for handoff

Note: Running in standalone mode (no status file).

To track progress across workflows, run workflow-status first.

Next Steps:

Review the product brief document
Run plan-project workflow to create PRD