From 1fe405eb648028a13115cf34f931e79747188fd9 Mon Sep 17 00:00:00 2001 From: Brian Madison Date: Thu, 16 Oct 2025 08:11:22 -0500 Subject: [PATCH] 1-analysis intentionalized --- .../document-project/instructions.md | 8 +- .../1-analysis/document-project/workflow.yaml | 67 +---- .../1-analysis/product-brief/instructions.md | 238 +++++------------- .../1-analysis/product-brief/workflow.yaml | 1 - .../research/instructions-router.md | 4 +- .../1-analysis/research/workflow.yaml | 202 +-------------- .../workflow-status/instructions.md | 10 +- .../1-analysis/workflow-status/workflow.yaml | 7 - workflow-cleanup-progress.md | 63 +++++ 9 files changed, 144 insertions(+), 456 deletions(-) diff --git a/src/modules/bmm/workflows/1-analysis/document-project/instructions.md b/src/modules/bmm/workflows/1-analysis/document-project/instructions.md index 55300505..29640929 100644 --- a/src/modules/bmm/workflows/1-analysis/document-project/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/document-project/instructions.md @@ -1,9 +1,11 @@ # Document Project Workflow Router - - The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/document-project/workflow.yaml +Communicate all responses in {communication_language} + + + This router determines workflow mode and delegates to specialized sub-workflows @@ -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}}. ``` -**✅ Document Project Workflow Complete** +**✅ Document Project Workflow Complete, {user_name}!** **Documentation Generated:** diff --git a/src/modules/bmm/workflows/1-analysis/document-project/workflow.yaml b/src/modules/bmm/workflows/1-analysis/document-project/workflow.yaml index fc3591ea..b618e33b 100644 --- a/src/modules/bmm/workflows/1-analysis/document-project/workflow.yaml +++ b/src/modules/bmm/workflows/1-analysis/document-project/workflow.yaml @@ -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 diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md b/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md index 57d02f01..7ded6269 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md @@ -2,6 +2,7 @@ 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} @@ -34,31 +35,18 @@ What would you like to do? -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 +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 -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? +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 @@ -76,70 +64,39 @@ Which approach works best for you? -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 +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 -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 +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 -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] +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 -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 +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 @@ -147,24 +104,11 @@ What are your top 3-5 Key Performance Indicators? -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 +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 @@ -172,115 +116,53 @@ What would constitute a successful MVP launch? mvp_success_criteria - -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 + +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 - -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. + +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 - -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? - + +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 +Note these are initial thoughts for PM and architect to consider during planning platform_requirements technology_preferences architecture_considerations - -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 + +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 - -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. + +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 @@ -371,11 +253,17 @@ Being honest about unknowns helps us prepare. 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). +If user chooses option 3 (executive summary): +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 @@ -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). ``` -**✅ Product Brief Complete** +**✅ 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:** diff --git a/src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml b/src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml index 8c4cc52d..c4550bac 100644 --- a/src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml +++ b/src/modules/bmm/workflows/1-analysis/product-brief/workflow.yaml @@ -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" diff --git a/src/modules/bmm/workflows/1-analysis/research/instructions-router.md b/src/modules/bmm/workflows/1-analysis/research/instructions-router.md index 79e1f9db..46560ad0 100644 --- a/src/modules/bmm/workflows/1-analysis/research/instructions-router.md +++ b/src/modules/bmm/workflows/1-analysis/research/instructions-router.md @@ -2,12 +2,14 @@ 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 -This is a ROUTER that directs to specialized research instruction sets +Communicate all responses in {communication_language} +This is a ROUTER that directs to specialized research instruction sets + Search {output_folder}/ for files matching pattern: bmm-workflow-status.md Find the most recent file (by date in filename: bmm-workflow-status.md) diff --git a/src/modules/bmm/workflows/1-analysis/research/workflow.yaml b/src/modules/bmm/workflows/1-analysis/research/workflow.yaml index 7fcb7b20..b31a9404 100644 --- a/src/modules/bmm/workflows/1-analysis/research/workflow.yaml +++ b/src/modules/bmm/workflows/1-analysis/research/workflow.yaml @@ -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" diff --git a/src/modules/bmm/workflows/1-analysis/workflow-status/instructions.md b/src/modules/bmm/workflows/1-analysis/workflow-status/instructions.md index d2a054fc..bf8f70ce 100644 --- a/src/modules/bmm/workflows/1-analysis/workflow-status/instructions.md +++ b/src/modules/bmm/workflows/1-analysis/workflow-status/instructions.md @@ -1,5 +1,9 @@ # Workflow Status - Master Router and Status Tracker +The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml +You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/1-analysis/workflow-status/workflow.yaml +Communicate all responses in {communication_language} + This is the UNIVERSAL ENTRY POINT for all BMM workflows @@ -158,9 +162,9 @@ Or tell me: "load {{next_agent}} and {{next_command}}" -Display welcome message +Display welcome message in {communication_language} -**🚀 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) Set next_agent = planned_workflow[0].agent Include complete planned_workflow in status file -**✅ Status file created!** +**✅ Status file created, {user_name}!** File: `bmm-workflow-status.md` diff --git a/src/modules/bmm/workflows/1-analysis/workflow-status/workflow.yaml b/src/modules/bmm/workflows/1-analysis/workflow-status/workflow.yaml index 9e2b65a0..68d71731 100644 --- a/src/modules/bmm/workflows/1-analysis/workflow-status/workflow.yaml +++ b/src/modules/bmm/workflows/1-analysis/workflow-status/workflow.yaml @@ -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: "" diff --git a/workflow-cleanup-progress.md b/workflow-cleanup-progress.md index 0ab66ae5..d8e60eac 100644 --- a/workflow-cleanup-progress.md +++ b/workflow-cleanup-progress.md @@ -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