1-analysis intentionalized
This commit is contained in:
Brian Madison
@@ -1,9 +1,11 @@
|
||||
# Document Project Workflow Router
|
||||
|
||||
<workflow>
|
||||
|
||||
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
|
||||
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/document-project/workflow.yaml</critical>
|
||||
<critical>Communicate all responses in {communication_language}</critical>
|
||||
|
||||
<workflow>
|
||||
|
||||
<critical>This router determines workflow mode and delegates to specialized sub-workflows</critical>
|
||||
|
||||
<step n="1" goal="Check and load workflow status file">
|
||||
@@ -241,7 +243,7 @@ Your choice [1/2/3]:
|
||||
- **{{date}}**: Completed document-project workflow ({{workflow_mode}} mode, {{scan_level}} scan). Generated brownfield documentation in {output_folder}/. Next: {{next_step}}.
|
||||
```
|
||||
|
||||
<output>**✅ Document Project Workflow Complete**
|
||||
<output>**✅ Document Project Workflow Complete, {user_name}!**
|
||||
|
||||
**Documentation Generated:**
|
||||
|
||||
|
||||
@@ -30,69 +30,6 @@ recommended_inputs:
|
||||
- project_root: "User will specify or use current directory"
|
||||
- existing_readme: "README.md at project root (if exists)"
|
||||
- project_config: "package.json, go.mod, requirements.txt, etc. (auto-detected)"
|
||||
|
||||
# Output configuration - Multiple files generated in output folder
|
||||
# File naming depends on project structure (simple vs multi-part)
|
||||
# Simple projects: index.md, architecture.md, etc.
|
||||
# Multi-part projects: index.md, architecture-{part_id}.md, etc.
|
||||
|
||||
default_output_files:
|
||||
- index: "{output_folder}/index.md"
|
||||
- project_overview: "{output_folder}/project-overview.md"
|
||||
- architecture: "{output_folder}/architecture.md" # or architecture-{part_id}.md for multi-part
|
||||
- source_tree: "{output_folder}/source-tree-analysis.md"
|
||||
- component_inventory: "{output_folder}/component-inventory.md" # or component-inventory-{part_id}.md
|
||||
- development_guide: "{output_folder}/development-guide.md" # or development-guide-{part_id}.md
|
||||
- deployment_guide: "{output_folder}/deployment-guide.md" # optional, if deployment config found
|
||||
- contribution_guide: "{output_folder}/contribution-guide.md" # optional, if CONTRIBUTING.md found
|
||||
- api_contracts: "{output_folder}/api-contracts.md" # optional, per part if needed
|
||||
- data_models: "{output_folder}/data-models.md" # optional, per part if needed
|
||||
- integration_architecture: "{output_folder}/integration-architecture.md" # only for multi-part
|
||||
- project_parts: "{output_folder}/project-parts.json" # metadata for multi-part projects
|
||||
- deep_dive: "{output_folder}/deep-dive-{sanitized_target_name}.md" # deep-dive mode output
|
||||
- project_scan_report: "{output_folder}/project-scan-report.json" # state tracking for resumability
|
||||
|
||||
# Runtime variables (generated during workflow execution)
|
||||
runtime_variables:
|
||||
- workflow_mode: "initial_scan | full_rescan | deep_dive"
|
||||
- scan_level: "quick | deep | exhaustive (default: quick)"
|
||||
- project_type: "Detected project type (web, backend, cli, etc.)"
|
||||
- project_parts: "Array of project parts for multi-part projects"
|
||||
- architecture_match: "Matched architecture from registry"
|
||||
- doc_requirements: "Documentation requirements for project type"
|
||||
- tech_stack: "Detected technology stack"
|
||||
- existing_docs: "Discovered existing documentation"
|
||||
- deep_dive_target: "Target area for deep-dive analysis (if deep-dive mode)"
|
||||
- deep_dive_count: "Number of deep-dive docs generated"
|
||||
- resume_point: "Step to resume from (if resuming interrupted workflow)"
|
||||
- state_file: "Path to project-scan-report.json for state tracking"
|
||||
|
||||
# Scan Level Definitions
|
||||
scan_levels:
|
||||
quick:
|
||||
description: "Pattern-based scanning without reading source files"
|
||||
duration: "2-5 minutes"
|
||||
reads: "Config files, package manifests, directory structure only"
|
||||
use_case: "Quick project overview, initial understanding"
|
||||
default: true
|
||||
deep:
|
||||
description: "Reads files in critical directories per project type"
|
||||
duration: "10-30 minutes"
|
||||
reads: "Critical files based on documentation_requirements.csv patterns"
|
||||
use_case: "Comprehensive documentation for brownfield PRD"
|
||||
default: false
|
||||
exhaustive:
|
||||
description: "Reads ALL source files in project"
|
||||
duration: "30-120 minutes"
|
||||
reads: "Every source file (excluding node_modules, dist, build)"
|
||||
use_case: "Complete analysis, migration planning, detailed audit"
|
||||
default: false
|
||||
|
||||
# Resumability Settings
|
||||
resumability:
|
||||
enabled: true
|
||||
state_file_location: "{output_folder}/project-scan-report.json"
|
||||
state_file_max_age: "24 hours"
|
||||
auto_prompt_resume: true
|
||||
archive_old_state: true
|
||||
archive_location: "{output_folder}/.archive/"
|
||||
# Primary output: {output_folder}/index.md
|
||||
# Additional files generated by sub-workflows based on project structure
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
|
||||
<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>
|
||||
<critical>Communicate all responses in {communication_language}</critical>
|
||||
|
||||
<workflow>
|
||||
|
||||
@@ -34,31 +35,18 @@ What would you like to do?</ask>
|
||||
</step>
|
||||
|
||||
<step n="1" 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>
|
||||
<action>Welcome the user in {communication_language} to the Product Brief creation process</action>
|
||||
<action>Explain this is a collaborative process to define their product vision and strategic foundation</action>
|
||||
<action>Ask the user to provide the project name for this product brief</action>
|
||||
<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>
|
||||
<action>Explore what existing materials the user has available to inform the brief</action>
|
||||
<action>Offer options for input sources: market research, brainstorming results, competitive analysis, initial ideas, or starting fresh</action>
|
||||
<action>If documents are provided, load and analyze them to extract key insights, themes, and patterns</action>
|
||||
<action>Engage the user about their core vision: what problem they're solving, who experiences it most acutely, and what sparked this product idea</action>
|
||||
<action>Build initial understanding through conversational exploration rather than rigid questioning</action>
|
||||
|
||||
<template-output>initial_context</template-output>
|
||||
</step>
|
||||
@@ -76,70 +64,39 @@ Which approach works best for you?</ask>
|
||||
</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>
|
||||
<action>Guide deep exploration of the problem: current state frustrations, quantifiable impact (time/money/opportunities), why existing solutions fall short, urgency of solving now</action>
|
||||
<action>Challenge vague statements and push for specificity with probing questions</action>
|
||||
<action>Help the user articulate measurable pain points with evidence</action>
|
||||
<action>Craft a compelling, evidence-based problem statement</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>
|
||||
<action>Shape the solution vision by exploring: core approach to solving the problem, key differentiators from existing solutions, why this will succeed, ideal user experience</action>
|
||||
<action>Focus on the "what" and "why", not implementation details - keep it strategic</action>
|
||||
<action>Help articulate compelling differentiators that make this solution unique</action>
|
||||
<action>Craft a clear, inspiring 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>
|
||||
<action>Guide detailed definition of primary users: demographic/professional profile, current problem-solving methods, specific pain points, goals they're trying to achieve</action>
|
||||
<action>Explore secondary user segments if applicable and define how their needs differ</action>
|
||||
<action>Push beyond generic personas like "busy professionals" - demand specificity and actionable details</action>
|
||||
<action>Create specific, actionable user profiles that inform product decisions</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>
|
||||
<action>Guide establishment of SMART goals across business objectives and user success metrics</action>
|
||||
<action>Explore measurable business outcomes (user acquisition targets, cost reductions, revenue goals)</action>
|
||||
<action>Define user success metrics focused on behaviors and outcomes, not features (task completion time, return frequency)</action>
|
||||
<action>Help formulate specific, measurable goals that distinguish between business and user success</action>
|
||||
<action>Identify top 3-5 Key Performance Indicators that will track product success</action>
|
||||
|
||||
<template-output>business_objectives</template-output>
|
||||
<template-output>user_success_metrics</template-output>
|
||||
@@ -147,24 +104,11 @@ What are your top 3-5 Key Performance Indicators?</ask>
|
||||
</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>Be ruthless about MVP scope - identify absolute MUST-HAVE features for launch that validate the core hypothesis</action>
|
||||
<action>For each proposed feature, probe why it's essential vs nice-to-have</action>
|
||||
<action>Identify tempting features that need to wait for v2 - what adds complexity without core value</action>
|
||||
<action>Define what constitutes a successful MVP launch with clear criteria</action>
|
||||
<action>Challenge scope creep aggressively and push for true minimum viability</action>
|
||||
<action>Clearly separate must-haves from nice-to-haves</action>
|
||||
|
||||
<template-output>core_features</template-output>
|
||||
@@ -172,115 +116,53 @@ What would constitute a successful MVP launch?
|
||||
<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>
|
||||
<step n="8" goal="Assess financial impact and ROI" if="collaboration_mode == 'interactive'">
|
||||
<action>Explore financial considerations: development investment, revenue potential, cost savings opportunities, break-even timing, budget alignment</action>
|
||||
<action>Investigate strategic alignment: company OKRs, strategic objectives, key initiatives supported, opportunity cost of NOT doing this</action>
|
||||
<action>Help quantify financial impact where possible - both tangible and intangible value</action>
|
||||
<action>Connect this product to broader company strategy and demonstrate strategic 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>
|
||||
<step n="9" goal="Explore post-MVP vision" optional="true" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide exploration of post-MVP future: Phase 2 features, expansion opportunities, long-term vision (1-2 years)</action>
|
||||
<action>Ensure MVP decisions align with future direction while staying focused on immediate goals</action>
|
||||
|
||||
<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>
|
||||
|
||||
<step n="10" goal="Document technical considerations" if="collaboration_mode == 'interactive'">
|
||||
<action>Capture technical context as preferences, not final decisions</action>
|
||||
<action>Explore platform requirements: web/mobile/desktop, browser/OS support, performance needs, accessibility standards</action>
|
||||
<action>Investigate technology preferences or constraints: frontend/backend frameworks, database needs, infrastructure requirements</action>
|
||||
<action>Identify existing systems requiring integration</action>
|
||||
<action>Check for technical-preferences.yaml file if available</action>
|
||||
<action>Note these are initial thoughts for PM and architect to consider</action>
|
||||
<action>Note these are initial thoughts for PM and architect to consider during planning</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>
|
||||
<step n="11" goal="Identify constraints and assumptions" if="collaboration_mode == 'interactive'">
|
||||
<action>Guide realistic expectations setting around constraints: budget/resource limits, timeline pressures, team size/expertise, technical limitations</action>
|
||||
<action>Explore assumptions being made about: user behavior, market conditions, technical feasibility</action>
|
||||
<action>Document constraints clearly and list assumptions that need validation 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>
|
||||
<step n="12" goal="Assess risks and open questions" optional="true" if="collaboration_mode == 'interactive'">
|
||||
<action>Facilitate honest risk assessment: what could derail the project, impact if risks materialize</action>
|
||||
<action>Document open questions: what still needs figuring out, what needs more research</action>
|
||||
<action>Help prioritize risks by impact and likelihood</action>
|
||||
<action>Frame unknowns as opportunities to prepare, not just worries</action>
|
||||
|
||||
<template-output>key_risks</template-output>
|
||||
<template-output>open_questions</template-output>
|
||||
@@ -371,11 +253,17 @@ Being honest about unknowns helps us prepare.</ask>
|
||||
|
||||
1. Review the entire document
|
||||
2. Make final adjustments
|
||||
3. Save and prepare for handoff to PM
|
||||
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).</ask>
|
||||
|
||||
<check>If user chooses option 3 (executive summary):</check>
|
||||
<action>Create condensed 3-page executive brief focusing on: problem statement, proposed solution, target users, MVP scope, financial impact, and strategic alignment</action>
|
||||
<action>Save as: {output_folder}/product-brief-executive-{{project_name}}-{{date}}.md</action>
|
||||
|
||||
<template-output>final_brief</template-output>
|
||||
<template-output>executive_brief</template-output>
|
||||
</step>
|
||||
|
||||
<step n="16" goal="Update status file on completion">
|
||||
@@ -401,11 +289,11 @@ This brief will serve as the primary input for creating the Product Requirements
|
||||
- **{{date}}**: Completed product-brief workflow. Product brief document generated and saved. Next: Proceed to plan-project workflow to create Product Requirements Document (PRD).
|
||||
```
|
||||
|
||||
<output>**✅ Product Brief Complete**
|
||||
<output>**✅ Product Brief Complete, {user_name}!**
|
||||
|
||||
**Brief Document:**
|
||||
|
||||
- Product brief saved and ready for handoff
|
||||
- Product brief saved to {output_folder}/product-brief-{{project_name}}-{{date}}.md
|
||||
|
||||
**Status file updated:**
|
||||
|
||||
|
||||
@@ -28,7 +28,6 @@ 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)
|
||||
|
||||
web_bundle:
|
||||
name: "product-brief"
|
||||
|
||||
@@ -2,12 +2,14 @@
|
||||
|
||||
<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>
|
||||
<critical>This is a ROUTER that directs to specialized research instruction sets</critical>
|
||||
<critical>Communicate all responses in {communication_language}</critical>
|
||||
|
||||
<!-- IDE-INJECT-POINT: research-subagents -->
|
||||
|
||||
<workflow>
|
||||
|
||||
<critical>This is a ROUTER that directs to specialized research instruction sets</critical>
|
||||
|
||||
<step n="1" goal="Check and load workflow status file">
|
||||
<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
|
||||
<action>Find the most recent file (by date in filename: bmm-workflow-status.md)</action>
|
||||
|
||||
@@ -25,129 +25,8 @@ template_market: "{installed_path}/template-market.md"
|
||||
template_deep_prompt: "{installed_path}/template-deep-prompt.md"
|
||||
template_technical: "{installed_path}/template-technical.md"
|
||||
|
||||
# Output configuration (dynamic based on research type)
|
||||
# Output configuration (dynamic based on research type selected in router)
|
||||
default_output_file: "{output_folder}/research-{{research_type}}-{{date}}.md"
|
||||
market_output: "{output_folder}/market-research-{{product_name_slug}}-{{date}}.md"
|
||||
deep_prompt_output: "{output_folder}/deep-research-prompt-{{date}}.md"
|
||||
technical_output: "{output_folder}/technical-research-{{date}}.md"
|
||||
|
||||
# Research types supported
|
||||
research_types:
|
||||
market:
|
||||
name: "Market Research"
|
||||
description: "Comprehensive market analysis with TAM/SAM/SOM"
|
||||
instructions: "{instructions_market}"
|
||||
template: "{template_market}"
|
||||
output: "{market_output}"
|
||||
deep_prompt:
|
||||
name: "Deep Research Prompt Generator"
|
||||
description: "Generate optimized prompts for AI research platforms"
|
||||
instructions: "{instructions_deep_prompt}"
|
||||
template: "{template_deep_prompt}"
|
||||
output: "{deep_prompt_output}"
|
||||
technical:
|
||||
name: "Technical/Architecture Research"
|
||||
description: "Technology evaluation and architecture pattern research"
|
||||
instructions: "{instructions_technical}"
|
||||
template: "{template_technical}"
|
||||
output: "{technical_output}"
|
||||
competitive:
|
||||
name: "Competitive Intelligence"
|
||||
description: "Deep competitor analysis"
|
||||
instructions: "{instructions_market}" # Uses market with competitive focus
|
||||
template: "{template_market}"
|
||||
output: "{output_folder}/competitive-intelligence-{{date}}.md"
|
||||
user:
|
||||
name: "User Research"
|
||||
description: "Customer insights and persona development"
|
||||
instructions: "{instructions_market}" # Uses market with user focus
|
||||
template: "{template_market}"
|
||||
output: "{output_folder}/user-research-{{date}}.md"
|
||||
domain:
|
||||
name: "Domain/Industry Research"
|
||||
description: "Industry and domain deep dives"
|
||||
instructions: "{instructions_market}" # Uses market with domain focus
|
||||
template: "{template_market}"
|
||||
output: "{output_folder}/domain-research-{{date}}.md"
|
||||
|
||||
# Research parameters (can be overridden at runtime)
|
||||
research_depth: "comprehensive" # Options: quick, standard, comprehensive
|
||||
enable_web_research: true
|
||||
enable_competitor_analysis: true
|
||||
enable_financial_modeling: true
|
||||
|
||||
# Data sources and tools
|
||||
required_tools:
|
||||
- web_search: "For real-time data gathering across all research types"
|
||||
- calculator: "For calculations (TAM/SAM/SOM, TCO, etc.)"
|
||||
- data_analysis: "For trends, patterns, and comparative analysis"
|
||||
|
||||
# Recommended input documents (varies by research type)
|
||||
recommended_inputs:
|
||||
market:
|
||||
- product_brief: "Product or business description"
|
||||
- target_customers: "Customer segment hypotheses"
|
||||
- competitor_list: "Known competitors (optional)"
|
||||
technical:
|
||||
- requirements_doc: "Technical requirements"
|
||||
- architecture_doc: "Current architecture (if brownfield)"
|
||||
- constraints_list: "Technical constraints"
|
||||
deep_prompt:
|
||||
- research_question: "Initial research question or topic"
|
||||
- context_docs: "Background documents for context"
|
||||
|
||||
# Claude Code integration points
|
||||
claude_code_enhancements:
|
||||
- injection_point: "research-subagents"
|
||||
- available_subagents:
|
||||
- market-researcher: "Deep market intelligence gathering"
|
||||
- trend-spotter: "Emerging trends and weak signals"
|
||||
- data-analyst: "Quantitative analysis"
|
||||
- competitor-analyzer: "Competitive intelligence"
|
||||
- user-researcher: "Customer insights"
|
||||
- technical-evaluator: "Technology assessment"
|
||||
|
||||
# Workflow configuration
|
||||
interactive: true # User checkpoints throughout
|
||||
autonomous: false # Requires user input
|
||||
allow_parallel: true # Can run research tasks in parallel
|
||||
|
||||
# Research frameworks available (context dependent)
|
||||
frameworks:
|
||||
market:
|
||||
- "TAM/SAM/SOM Analysis"
|
||||
- "Porter's Five Forces"
|
||||
- "Jobs-to-be-Done"
|
||||
- "Technology Adoption Lifecycle"
|
||||
- "SWOT Analysis"
|
||||
- "Value Chain Analysis"
|
||||
technical:
|
||||
- "Trade-off Analysis"
|
||||
- "Architecture Decision Records (ADR)"
|
||||
- "Technology Radar"
|
||||
- "Comparison Matrix"
|
||||
- "Cost-Benefit Analysis"
|
||||
deep_prompt:
|
||||
- "ChatGPT Deep Research Best Practices"
|
||||
- "Gemini Deep Research Framework"
|
||||
- "Grok DeepSearch Optimization"
|
||||
- "Claude Projects Methodology"
|
||||
- "Iterative Prompt Refinement"
|
||||
|
||||
# Data sources (for web research)
|
||||
data_sources:
|
||||
- "Industry reports and publications"
|
||||
- "Government statistics and databases"
|
||||
- "Financial reports and SEC filings"
|
||||
- "News articles and press releases"
|
||||
- "Academic research papers"
|
||||
- "Technical documentation and RFCs"
|
||||
- "GitHub repositories and discussions"
|
||||
- "Stack Overflow and developer forums"
|
||||
- "Market research firm reports"
|
||||
- "Social media and communities"
|
||||
- "Patent databases"
|
||||
- "Benchmarking studies"
|
||||
|
||||
web_bundle:
|
||||
name: "research"
|
||||
@@ -164,82 +43,3 @@ web_bundle:
|
||||
- "bmad/bmm/workflows/1-analysis/research/template-deep-prompt.md"
|
||||
- "bmad/bmm/workflows/1-analysis/research/template-technical.md"
|
||||
- "bmad/bmm/workflows/1-analysis/research/checklist.md"
|
||||
# Workflow configuration
|
||||
interactive: true # User checkpoints throughout
|
||||
autonomous: false # Requires user input
|
||||
allow_parallel: true # Can run research tasks in parallel
|
||||
|
||||
# Research frameworks available (context dependent)
|
||||
frameworks:
|
||||
market:
|
||||
- "TAM/SAM/SOM Analysis"
|
||||
- "Porter's Five Forces"
|
||||
- "Jobs-to-be-Done"
|
||||
- "Technology Adoption Lifecycle"
|
||||
- "SWOT Analysis"
|
||||
- "Value Chain Analysis"
|
||||
technical:
|
||||
- "Trade-off Analysis"
|
||||
- "Architecture Decision Records (ADR)"
|
||||
- "Technology Radar"
|
||||
- "Comparison Matrix"
|
||||
- "Cost-Benefit Analysis"
|
||||
deep_prompt:
|
||||
- "ChatGPT Deep Research Best Practices"
|
||||
- "Gemini Deep Research Framework"
|
||||
- "Grok DeepSearch Optimization"
|
||||
- "Claude Projects Methodology"
|
||||
- "Iterative Prompt Refinement"
|
||||
|
||||
# Data sources (for web research)
|
||||
data_sources:
|
||||
- "Industry reports and publications"
|
||||
- "Government statistics and databases"
|
||||
- "Financial reports and SEC filings"
|
||||
- "News articles and press releases"
|
||||
- "Academic research papers"
|
||||
- "Technical documentation and RFCs"
|
||||
- "GitHub repositories and discussions"
|
||||
- "Stack Overflow and developer forums"
|
||||
- "Market research firm reports"
|
||||
- "Social media and communities"
|
||||
- "Patent databases"
|
||||
- "Benchmarking studies"
|
||||
# Research types supported
|
||||
research_types:
|
||||
market:
|
||||
name: "Market Research"
|
||||
description: "Comprehensive market analysis with TAM/SAM/SOM"
|
||||
instructions: "bmad/bmm/workflows/1-analysis/research/instructions-market.md"
|
||||
template: "bmad/bmm/workflows/1-analysis/research/template-market.md"
|
||||
output: "{market_output}"
|
||||
deep_prompt:
|
||||
name: "Deep Research Prompt Generator"
|
||||
description: "Generate optimized prompts for AI research platforms"
|
||||
instructions: "bmad/bmm/workflows/1-analysis/research/instructions-deep-prompt.md"
|
||||
template: "bmad/bmm/workflows/1-analysis/research/template-deep-prompt.md"
|
||||
output: "{deep_prompt_output}"
|
||||
technical:
|
||||
name: "Technical/Architecture Research"
|
||||
description: "Technology evaluation and architecture pattern research"
|
||||
instructions: "bmad/bmm/workflows/1-analysis/research/instructions-technical.md"
|
||||
template: "bmad/bmm/workflows/1-analysis/research/template-technical.md"
|
||||
output: "{technical_output}"
|
||||
competitive:
|
||||
name: "Competitive Intelligence"
|
||||
description: "Deep competitor analysis"
|
||||
instructions: "bmad/bmm/workflows/1-analysis/research/instructions-market.md" # Uses market with competitive focus
|
||||
template: "bmad/bmm/workflows/1-analysis/research/template-market.md"
|
||||
output: "{output_folder}/competitive-intelligence-{{date}}.md"
|
||||
user:
|
||||
name: "User Research"
|
||||
description: "Customer insights and persona development"
|
||||
instructions: "bmad/bmm/workflows/1-analysis/research/instructions-market.md" # Uses market with user focus
|
||||
template: "bmad/bmm/workflows/1-analysis/research/template-market.md"
|
||||
output: "{output_folder}/user-research-{{date}}.md"
|
||||
domain:
|
||||
name: "Domain/Industry Research"
|
||||
description: "Industry and domain deep dives"
|
||||
instructions: "bmad/bmm/workflows/1-analysis/research/instructions-market.md" # Uses market with domain focus
|
||||
template: "bmad/bmm/workflows/1-analysis/research/template-market.md"
|
||||
output: "{output_folder}/domain-research-{{date}}.md"
|
||||
|
||||
@@ -1,5 +1,9 @@
|
||||
# Workflow Status - Master Router and Status Tracker
|
||||
|
||||
<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
|
||||
<critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/1-analysis/workflow-status/workflow.yaml</critical>
|
||||
<critical>Communicate all responses in {communication_language}</critical>
|
||||
|
||||
<workflow>
|
||||
|
||||
<critical>This is the UNIVERSAL ENTRY POINT for all BMM workflows</critical>
|
||||
@@ -158,9 +162,9 @@ Or tell me: "load {{next_agent}} and {{next_command}}"
|
||||
|
||||
<step n="3" goal="Initial workflow planning - no status file exists" if="status_file_found == false">
|
||||
|
||||
<action>Display welcome message</action>
|
||||
<action>Display welcome message in {communication_language}</action>
|
||||
|
||||
**🚀 Welcome to BMad Method Workflows!**
|
||||
**🚀 Welcome to BMad Method Workflows, {user_name}!**
|
||||
|
||||
No workflow status file found. Let's plan your complete workflow journey.
|
||||
|
||||
@@ -568,7 +572,7 @@ Create status file? (y/n)</ask>
|
||||
<action>Set next_agent = planned_workflow[0].agent</action>
|
||||
<action>Include complete planned_workflow in status file</action>
|
||||
|
||||
<output>**✅ Status file created!**
|
||||
<output>**✅ Status file created, {user_name}!**
|
||||
|
||||
File: `bmm-workflow-status.md`
|
||||
|
||||
|
||||
@@ -14,13 +14,6 @@ date: system-generated
|
||||
installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/workflow-status"
|
||||
instructions: "{installed_path}/instructions.md"
|
||||
|
||||
# Variables and inputs
|
||||
variables:
|
||||
status_file_pattern: "bmm-workflow-status.md" # Searches for versioned files
|
||||
check_existing_status: true # Always check for existing status file
|
||||
display_menu: true # Display agent menu after status check
|
||||
suggest_next_action: true # Suggest next action based on current state
|
||||
|
||||
# Output configuration - no output file, reads existing status
|
||||
default_output_file: ""
|
||||
|
||||
|
||||
@@ -213,6 +213,69 @@ date: system-generated
|
||||
|
||||
**This serves as the reference implementation for converting prescriptive workflows to intent-based style.**
|
||||
|
||||
### 2025-10-16: Completed ALL 1-analysis Workflows (7/7 - 100%)
|
||||
|
||||
**✅ Phase 1-Analysis Module Complete!**
|
||||
|
||||
All 7 workflows in the 1-analysis folder have been audited, cleaned, and optimized:
|
||||
|
||||
1. ✅ **brainstorm-game** - FULL AUDIT (earlier session)
|
||||
- Removed use_advanced_elicitation bloat
|
||||
- Restored critical existing_workflows
|
||||
- Added {communication_language} and {user_name}
|
||||
|
||||
2. ✅ **brainstorm-project** - FULL AUDIT (earlier session)
|
||||
- Removed use_advanced_elicitation bloat
|
||||
- Restored critical existing_workflows
|
||||
- Added {communication_language} and {user_name}
|
||||
|
||||
3. ✅ **game-brief** - INTENT-BASED TRANSFORMATION
|
||||
- **Before:** 617 lines → **After:** 370 lines (40% reduction)
|
||||
- Removed brief_format bloat
|
||||
- Transformed all prescriptive steps to intent-based
|
||||
- Added executive summary option
|
||||
- Added {communication_language} and {user_name}
|
||||
|
||||
4. ✅ **product-brief** - INTENT-BASED TRANSFORMATION
|
||||
- **Before:** 444 lines → **After:** 332 lines (25% reduction)
|
||||
- Removed brief_format bloat
|
||||
- Transformed steps 3-12 to intent-based guidance
|
||||
- Added executive summary option
|
||||
- Added {communication_language} and {user_name}
|
||||
|
||||
5. ✅ **research** - ROUTER CLEANUP
|
||||
- **YAML Before:** 245 lines → **After:** 46 lines (81% reduction!)
|
||||
- Removed massive bloat: research_types, frameworks, data_sources, claude_code_enhancements (duplicated in web_bundle)
|
||||
- Added {communication_language} to router
|
||||
- Router appropriately deterministic for type selection
|
||||
|
||||
6. ✅ **document-project** - ROUTER CLEANUP
|
||||
- **YAML:** Removed runtime_variables, scan_levels, resumability bloat (documentation, not config)
|
||||
- Added {communication_language}
|
||||
- Added {user_name} personalization
|
||||
- Router appropriately deterministic for mode selection
|
||||
|
||||
7. ✅ **workflow-status** - DETERMINISTIC VALIDATION
|
||||
- **YAML:** Removed unused variables bloat (status_file_pattern, check_existing_status, display_menu, suggest_next_action)
|
||||
- Added missing critical headers
|
||||
- Added {user_name} personalization
|
||||
- Appropriately deterministic/structured (this is a menu/orchestration workflow)
|
||||
|
||||
**Instruction Style Decisions Applied:**
|
||||
|
||||
- **Intent-Based:** game-brief, product-brief (conversational, adaptive)
|
||||
- **Deterministic/Prescriptive:** workflow-status (menu/orchestration)
|
||||
- **Router Pattern:** document-project, research (appropriate for delegation workflows)
|
||||
|
||||
**Total Lines Saved:**
|
||||
|
||||
- game-brief: 247 lines
|
||||
- product-brief: 112 lines
|
||||
- research YAML: 199 lines
|
||||
- document-project YAML: ~100 lines
|
||||
- workflow-status YAML: ~10 lines
|
||||
- **Total:** ~668 lines removed across 1-analysis workflows
|
||||
|
||||
---
|
||||
|
||||
## Summary Statistics
|
||||
|
||||
Reference in New Issue
Block a user