pig-farm-controller/bmad/bmm/workflows/1-analysis/product-brief/instructions.md

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 Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level} Generate all documents in {document_output_language}

DOCUMENT OUTPUT: Concise, professional, strategically focused. Use tables/lists over prose. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.

Check if {output_folder}/bmm-workflow-status.yaml exists No workflow status file found. Product Brief is optional - you can continue without status tracking. Set standalone_mode = true Load the FULL file: {output_folder}/bmm-workflow-status.yaml Parse workflow_status section Check status of "product-brief" workflow Get project_level from YAML metadata Find first non-completed workflow (next expected workflow) Note: Product Brief is most valuable for Level 2+ projects. Your project is Level {{project_level}}. You may want to skip directly to technical planning instead. ⚠️ Product Brief already completed: {{product-brief status}} Re-running will overwrite the existing brief. Continue? (y/n) Exiting. Use workflow-status to see your next step. Exit workflow ⚠️ Next expected workflow: {{next_workflow}}. Product Brief is out of sequence. Continue with Product Brief anyway? (y/n) Exiting. Run {{next_workflow}} instead. Exit workflow

Set standalone_mode = false

Welcome the user in {communication_language} to the Product Brief creation process Explain this is a collaborative process to define their product vision and strategic foundation Ask the user to provide the project name for this product brief project_name Explore what existing materials the user has available to inform the brief Offer options for input sources: market research, brainstorming results, competitive analysis, initial ideas, or starting fresh If documents are provided, load and analyze them to extract key insights, themes, and patterns Engage the user about their core vision: what problem they're solving, who experiences it most acutely, and what sparked this product idea Build initial understanding through conversational exploration rather than rigid questioning

initial_context

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 collaboration_mode

Guide deep exploration of the problem: current state frustrations, quantifiable impact (time/money/opportunities), why existing solutions fall short, urgency of solving now Challenge vague statements and push for specificity with probing questions Help the user articulate measurable pain points with evidence Craft a compelling, evidence-based problem statement

problem_statement

Shape the solution vision by exploring: core approach to solving the problem, key differentiators from existing solutions, why this will succeed, ideal user experience Focus on the "what" and "why", not implementation details - keep it strategic Help articulate compelling differentiators that make this solution unique Craft a clear, inspiring solution vision

proposed_solution

Guide detailed definition of primary users: demographic/professional profile, current problem-solving methods, specific pain points, goals they're trying to achieve Explore secondary user segments if applicable and define how their needs differ Push beyond generic personas like "busy professionals" - demand specificity and actionable details Create specific, actionable user profiles that inform product decisions

primary_user_segment secondary_user_segment

Guide establishment of SMART goals across business objectives and user success metrics Explore measurable business outcomes (user acquisition targets, cost reductions, revenue goals) Define user success metrics focused on behaviors and outcomes, not features (task completion time, return frequency) Help formulate specific, measurable goals that distinguish between business and user success Identify top 3-5 Key Performance Indicators that will track product success

business_objectives user_success_metrics key_performance_indicators

Be ruthless about MVP scope - identify absolute MUST-HAVE features for launch that validate the core hypothesis For each proposed feature, probe why it's essential vs nice-to-have Identify tempting features that need to wait for v2 - what adds complexity without core value Define what constitutes a successful MVP launch with clear criteria Challenge scope creep aggressively and push for true minimum viability Clearly separate must-haves from nice-to-haves

core_features out_of_scope mvp_success_criteria

Explore financial considerations: development investment, revenue potential, cost savings opportunities, break-even timing, budget alignment Investigate strategic alignment: company OKRs, strategic objectives, key initiatives supported, opportunity cost of NOT doing this Help quantify financial impact where possible - both tangible and intangible value Connect this product to broader company strategy and demonstrate strategic value

financial_impact company_objectives_alignment strategic_initiatives

Guide exploration of post-MVP future: Phase 2 features, expansion opportunities, long-term vision (1-2 years) Ensure MVP decisions align with future direction while staying focused on immediate goals

phase_2_features long_term_vision expansion_opportunities

Capture technical context as preferences, not final decisions Explore platform requirements: web/mobile/desktop, browser/OS support, performance needs, accessibility standards Investigate technology preferences or constraints: frontend/backend frameworks, database needs, infrastructure requirements Identify existing systems requiring integration Check for technical-preferences.yaml file if available Note these are initial thoughts for PM and architect to consider during planning

platform_requirements technology_preferences architecture_considerations

Guide realistic expectations setting around constraints: budget/resource limits, timeline pressures, team size/expertise, technical limitations Explore assumptions being made about: user behavior, market conditions, technical feasibility Document constraints clearly and list assumptions that need validation during development

constraints key_assumptions

Facilitate honest risk assessment: what could derail the project, impact if risks materialize Document open questions: what still needs figuring out, what needs more research Help prioritize risks by impact and likelihood Frame unknowns as opportunities to prepare, not just worries

key_risks open_questions research_areas

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

problem_statement proposed_solution primary_user_segment secondary_user_segment business_objectives user_success_metrics key_performance_indicators core_features out_of_scope mvp_success_criteria phase_2_features long_term_vision expansion_opportunities financial_impact company_objectives_alignment strategic_initiatives platform_requirements technology_preferences architecture_considerations constraints key_assumptions key_risks open_questions research_areas

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

executive_summary

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

research_summary stakeholder_input references

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:

1. Review the entire document
2. Make final adjustments
3. Generate an executive summary version (3-page limit)
4. Save and prepare for handoff to PM

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

Create condensed 3-page executive brief focusing on: problem statement, proposed solution, target users, MVP scope, financial impact, and strategic alignment Save as: {output_folder}/product-brief-executive-{{project_name}}-{{date}}.md

final_brief executive_brief

Load the FULL file: {output_folder}/bmm-workflow-status.yaml Find workflow_status key "product-brief" ONLY write the file path as the status value - no other text, notes, or metadata Update workflow_status["product-brief"] = "{output_folder}/bmm-product-brief-{{project_name}}-{{date}}.md" Save file, preserving ALL comments and structure including STATUS DEFINITIONS

Find first non-completed workflow in workflow_status (next workflow to do) Determine next agent from path file based on next workflow

✅ Product Brief Complete, {user_name}!

Brief Document:

• Product brief saved to {output_folder}/bmm-product-brief-{{project_name}}-{{date}}.md

{{#if standalone_mode != true}} Status Updated:

• Progress tracking updated: product-brief marked complete
• Next workflow: {{next_workflow}} {{else}} Note: Running in standalone mode (no progress tracking) {{/if}}

Next Steps:

{{#if standalone_mode != true}}

• Next workflow: {{next_workflow}} ({{next_agent}} agent)
• Optional: Gather additional stakeholder input or run research workflows before proceeding

Check status anytime with: workflow-status {{else}} Since no workflow is in progress:

• Refer to the BMM workflow guide if unsure what to do next
• Or run workflow-init to create a workflow path and get guided next steps {{/if}}