bmad-method 6.0.0-alpha.12 → 6.0.0-alpha.13

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md

@@ -0,0 +1,301 @@
+---
+name: 'step-08-generate-report'
+description: 'Generate comprehensive compliance report with fix recommendations'
+
+# Path Definitions
+workflow_path: '{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-08-generate-report.md'
+workflowFile: '{workflow_path}/workflow.md'
+complianceReportFile: '{output_folder}/workflow-compliance-report-{workflow_name}.md'
+targetWorkflowFile: '{target_workflow_path}'
+
+# Template References
+complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
+
+# Documentation References
+stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/step-template.md'
+workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/workflow-template.md'
+---
+
+# Step 8: Comprehensive Compliance Report Generation
+
+## STEP GOAL:
+
+Generate comprehensive compliance report compiling all validation findings, provide severity-ranked fix recommendations, and offer concrete next steps for achieving full compliance.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a compliance validator and quality assurance specialist
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring report generation and strategic recommendation expertise
+- ✅ User brings their validated workflow and needs actionable improvement plan
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on compiling comprehensive compliance report
+- 🚫 FORBIDDEN to generate report without including all findings from previous phases
+- 💬 Approach: Systematic compilation with clear, actionable recommendations
+- 📋 Ensure report is complete, accurate, and immediately useful
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Compile all findings from previous validation phases
+- 💾 Generate structured compliance report with clear sections
+- 📖 Provide severity-ranked recommendations with specific fixes
+- 🚫 FORBIDDEN to overlook any validation findings or recommendations
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Complete validation findings from all previous phases
+- Focus: Comprehensive report generation and strategic recommendations
+- Limits: Report generation only, no additional validation
+- Dependencies: Successful completion of all previous validation phases
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Initialize Report Generation
+
+"**Phase 5: Comprehensive Compliance Report Generation**
+Target: `{target_workflow_name}`
+
+Compiling all validation findings into structured compliance report with actionable recommendations..."
+
+### 2. Generate Compliance Report Structure
+
+Create comprehensive report at {complianceReportFile}:
+
+```markdown
+# Workflow Compliance Report
+
+**Workflow:** {target_workflow_name}
+**Date:** {current_date}
+**Standards:** BMAD workflow-template.md and step-template.md
+
+---
+
+## Executive Summary
+
+**Overall Compliance Status:** [PASS/FAIL/PARTIAL]
+**Critical Issues:** [number] - Must be fixed immediately
+**Major Issues:** [number] - Significantly impacts quality/maintainability
+**Minor Issues:** [number] - Standards compliance improvements
+
+**Compliance Score:** [percentage]% based on template adherence
+
+---
+
+## Phase 1: Workflow.md Validation Results
+
+### Critical Violations
+
+[Critical issues with template references and specific fixes]
+
+### Major Violations
+
+[Major issues with template references and specific fixes]
+
+### Minor Violations
+
+[Minor issues with template references and specific fixes]
+
+---
+
+## Phase 2: Step-by-Step Validation Results
+
+### Summary by Step
+
+[Each step file with its violation summary]
+
+### Most Common Violations
+
+1. [Most frequent violation type with count]
+2. [Second most frequent with count]
+3. [Third most frequent with count]
+
+### Workflow Type Assessment
+
+**Workflow Type:** [editing/creation/validation/etc.]
+**Template Appropriateness:** [appropriate/needs improvement]
+**Recommendations:** [specific suggestions]
+
+---
+
+## Phase 3: Holistic Analysis Results
+
+### Flow Validation
+
+[Flow analysis findings with specific issues]
+
+### Goal Alignment
+
+**Alignment Score:** [percentage]%
+**Stated vs. Actual:** [comparison with gaps]
+
+### Optimization Opportunities
+
+[Priority improvements with expected benefits]
+
+---
+
+## Meta-Workflow Failure Analysis
+
+### Issues That Should Have Been Prevented
+
+**By create-workflow:**
+
+- [Specific issues that should have been caught during creation]
+- [Suggested improvements to create-workflow]
+
+**By edit-workflow (if applicable):**
+
+- [Specific issues introduced during editing]
+- [Suggested improvements to edit-workflow]
+
+### Recommended Meta-Workflow Improvements
+
+[Specific actionable improvements for meta-workflows]
+
+---
+
+## Severity-Ranked Fix Recommendations
+
+### IMMEDIATE - Critical (Must Fix for Functionality)
+
+1. **[Issue Title]** - [File: filename.md]
+   - **Problem:** [Clear description]
+   - **Template Reference:** [Specific section]
+   - **Fix:** [Exact action needed]
+   - **Impact:** [Why this is critical]
+
+### HIGH PRIORITY - Major (Significantly Impacts Quality)
+
+1. **[Issue Title]** - [File: filename.md]
+   - **Problem:** [Clear description]
+   - **Template Reference:** [Specific section]
+   - **Fix:** [Exact action needed]
+   - **Impact:** [Quality/maintainability impact]
+
+### MEDIUM PRIORITY - Minor (Standards Compliance)
+
+1. **[Issue Title]** - [File: filename.md]
+   - **Problem:** [Clear description]
+   - **Template Reference:** [Specific section]
+   - **Fix:** [Exact action needed]
+   - **Impact:** [Standards compliance]
+
+---
+
+## Automated Fix Options
+
+### Fixes That Can Be Applied Automatically
+
+[List of violations that can be automatically corrected]
+
+### Fixes Requiring Manual Review
+
+[List of violations requiring human judgment]
+
+---
+
+## Next Steps Recommendation
+
+**Recommended Approach:**
+
+1. Fix all Critical issues immediately (workflow may not function)
+2. Address Major issues for reliability and maintainability
+3. Implement Minor issues for full standards compliance
+4. Update meta-workflows to prevent future violations
+
+**Estimated Effort:**
+
+- Critical fixes: [time estimate]
+- Major fixes: [time estimate]
+- Minor fixes: [time estimate]
+```
+
+### 3. Final Report Summary
+
+"**Compliance Report Generated:** `{complianceReportFile}`
+
+**Report Contents:**
+
+- ✅ Complete violation analysis from all validation phases
+- ✅ Severity-ranked recommendations with specific fixes
+- ✅ Meta-workflow failure analysis with improvement suggestions
+- ✅ Automated vs manual fix categorization
+- ✅ Strategic next steps and effort estimates
+
+**Key Findings:**
+
+- **Overall Compliance Score:** [percentage]%
+- **Critical Issues:** [number] requiring immediate attention
+- **Major Issues:** [number] impacting quality
+- **Minor Issues:** [number] for standards compliance
+
+**Meta-Workflow Improvements Identified:** [number] specific suggestions
+
+### 4. Offer Next Steps
+
+"**Phase 6 Complete:** Comprehensive compliance analysis finished
+All 8 validation phases completed with full report generation
+
+**Compliance Analysis Complete. What would you like to do next?**"
+
+**Available Options:**
+
+- **[A] Apply Automated Fixes** - I can automatically correct applicable violations
+- **[B] Launch edit-agent** - Edit the workflow with this compliance report as guidance
+- **[C] Manual Review** - Use the report for manual fixes at your pace
+- **[D] Update Meta-Workflows** - Strengthen create/edit workflows with identified improvements
+
+**Recommendation:** Start with Critical issues, then proceed through High and Medium priority items systematically."
+
+### 5. Report Completion Options
+
+Display: "**Select an Option:** [A] Apply Automated Fixes [B] Launch Edit-Agent [C] Manual Review [D] Update Meta-Workflows [X] Exit"
+
+## Menu Handling Logic:
+
+- IF A: Begin applying automated fixes from the report
+- IF B: Launch edit-agent workflow with this compliance report as context
+- IF C: End workflow with guidance for manual review using the report
+- IF D: Provide specific recommendations for meta-workflow improvements
+- IF X: Save report and end workflow gracefully
+
+## CRITICAL STEP COMPLETION NOTE
+
+The workflow is complete when the comprehensive compliance report has been generated and the user has selected their preferred next step. The report contains all findings, recommendations, and strategic guidance needed to achieve full BMAD compliance.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Comprehensive compliance report generated with all validation findings
+- Severity-ranked fix recommendations provided with specific actions
+- Meta-workflow failure analysis completed with improvement suggestions
+- Clear next steps offered based on user preferences
+- Report saved and accessible for future reference
+- User has actionable plan for achieving full compliance
+
+### ❌ SYSTEM FAILURE:
+
+- Generating incomplete report without all validation findings
+- Missing severity rankings or specific fix recommendations
+- Not providing clear next steps or options
+- Failing to include meta-workflow improvement suggestions
+- Creating report that is not immediately actionable
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmb/workflows/workflow-compliance-check/templates/compliance-report.md

@@ -0,0 +1,140 @@
+# Workflow Compliance Report Template
+
+**Workflow:** {workflow_name}
+**Date:** {validation_date}
+**Standards:** BMAD workflow-template.md and step-template.md
+**Report Type:** Comprehensive Compliance Validation
+
+---
+
+## Executive Summary
+
+**Overall Compliance Status:** {compliance_status}
+**Critical Issues:** {critical_count} - Must be fixed immediately
+**Major Issues:** {major_count} - Significantly impacts quality/maintainability
+**Minor Issues:** {minor_count} - Standards compliance improvements
+
+**Compliance Score:** {compliance_score}% based on template adherence
+
+**Workflow Type Assessment:** {workflow_type} - {type_appropriateness}
+
+---
+
+## Phase 1: Workflow.md Validation Results
+
+### Template Adherence Analysis
+
+**Reference Standard:** {workflow_template_path}
+
+### Critical Violations
+
+{critical_violations}
+
+### Major Violations
+
+{major_violations}
+
+### Minor Violations
+
+{minor_violations}
+
+---
+
+## Phase 2: Step-by-Step Validation Results
+
+### Summary by Step
+
+{step_validation_summary}
+
+### Most Common Violations
+
+1. {most_common_violation_1}
+2. {most_common_violation_2}
+3. {most_common_violation_3}
+
+### Workflow Type Appropriateness
+
+**Analysis:** {workflow_type_analysis}
+**Recommendations:** {type_recommendations}
+
+---
+
+## Phase 3: Holistic Analysis Results
+
+### Flow Validation
+
+{flow_validation_results}
+
+### Goal Alignment
+
+**Stated Goal:** {stated_goal}
+**Actual Implementation:** {actual_implementation}
+**Alignment Score:** {alignment_score}%
+**Gap Analysis:** {gap_analysis}
+
+### Optimization Opportunities
+
+{optimization_opportunities}
+
+---
+
+## Meta-Workflow Failure Analysis
+
+### Issues That Should Have Been Prevented
+
+**By create-workflow:**
+{create_workflow_failures}
+
+**By edit-workflow:**
+{edit_workflow_failures}
+
+### Recommended Meta-Workflow Improvements
+
+{meta_workflow_improvements}
+
+---
+
+## Severity-Ranked Fix Recommendations
+
+### IMMEDIATE - Critical (Must Fix for Functionality)
+
+{critical_recommendations}
+
+### HIGH PRIORITY - Major (Significantly Impacts Quality)
+
+{major_recommendations}
+
+### MEDIUM PRIORITY - Minor (Standards Compliance)
+
+{minor_recommendations}
+
+---
+
+## Automated Fix Options
+
+### Fixes That Can Be Applied Automatically
+
+{automated_fixes}
+
+### Fixes Requiring Manual Review
+
+{manual_fixes}
+
+---
+
+## Next Steps Recommendation
+
+**Recommended Approach:**
+{recommended_approach}
+
+**Estimated Effort:**
+
+- Critical fixes: {critical_effort}
+- Major fixes: {major_effort}
+- Minor fixes: {minor_effort}
+
+---
+
+**Report Generated:** {timestamp}
+**Validation Engine:** BMAD Workflow Compliance Checker
+**Next Review Date:** {next_review_date}

package/src/modules/bmb/workflows/workflow-compliance-check/workflow.md

@@ -0,0 +1,58 @@
+---
+name: Workflow Compliance Check
+description: Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting
+web_bundle: false
+---
+
+# Workflow Compliance Check
+
+**Goal:** Systematically validate workflows against BMAD standards through adversarial analysis, generating detailed compliance reports with severity-ranked violations and improvement recommendations.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a compliance validator and quality assurance specialist collaborating with a workflow owner. This is a partnership, not a client-vendor relationship. You bring expertise in BMAD standards, workflow architecture, and systematic validation, while the user brings their workflow and specific compliance concerns. Work together as equals.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in context for compliance checking (no output file frontmatter needed)
+- **Append-Only Building**: Build compliance reports by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {project-root}/{bmad_folder}/bmb/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `{workflow_path}/steps/step-01-validate-goal.md` to begin the workflow. If the path to a workflow was provided, set `user_provided_path` to that path.

package/src/modules/bmgd/agents/game-architect.agent.yaml

@@ -25,7 +25,7 @@ agent:
       description: Produce a Scale Adaptive Game Architecture
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation

package/src/modules/bmgd/agents/game-designer.agent.yaml

@@ -32,7 +32,7 @@ agent:
       description: 5. Create Narrative Design Document (story-driven games)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation

package/src/modules/bmgd/agents/game-dev.agent.yaml

@@ -32,7 +32,7 @@ agent:
       description: "Mark story done after DoD complete"
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation

package/src/modules/bmgd/agents/game-scrum-master.agent.yaml

@@ -67,7 +67,7 @@ agent:
       description: (Optional) Navigate significant changes during game dev sprint
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Consult with other expert agents from the party
 
     - trigger: advanced-elicitation

package/src/modules/bmm/_module-installer/install-config.yaml

@@ -40,21 +40,15 @@ sprint_artifacts:
   default: "{output_folder}/sprint-artifacts"
   result: "{project-root}/{value}"
 
-# TEA Agent Configuration
 tea_use_mcp_enhancements:
-  prompt: "Enable Test Architect Playwright MCP capabilities (healing, exploratory, verification)?"
+  prompt: "Enable Test Architect Playwright MCP capabilities (healing, exploratory, verification)? You have to setup your MCPs yourself; refer to test-architecture.md for hints."
+  default: false
+  result: "{value}"
+
+tea_use_playwright_utils:
+  prompt:
+    - "Are you using playwright-utils (@seontechnologies/playwright-utils) in your project?"
+    - "This adds fixture-based utilities for auth, API requests, network recording, polling, intercept, recurse, logging, file download handling, and burn-in."
+    - "You must install packages yourself, or use test architect's *framework command."
   default: false
   result: "{value}"
-# desired_mcp_tools:
-#   prompt:
-#     - "Which MCP Tools will you be using? (Select all that apply)"
-#     - "Note: You will need to install these separately. Bindings will come post ALPHA along with other choices."
-#   result: "{value}"
-#   multi-select:
-#     - "Chrome Official MCP"
-#     - "Playwright"
-#     - "Context 7"
-#     - "Tavily"
-#     - "Perplexity"
-#     - "Jira"
-#     - "Trello"

package/src/modules/bmm/agents/analyst.agent.yaml

@@ -12,35 +12,35 @@ agent:
     role: Strategic Business Analyst + Requirements Expert
     identity: Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.
     communication_style: "Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark 'aha!' moments while structuring insights with precision."
-    principles: Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision. Ensure all stakeholder voices heard.
+    principles: |
+      - Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence.
+      - Articulate requirements with absolute precision. Ensure all stakeholder voices heard.
+      - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   menu:
-    - trigger: workflow-init
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml"
-      description: Start a new sequenced workflow path (START HERE!)
-
     - trigger: workflow-status
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations
+      description: Get workflow status or initialize a workflow if not already done (optional)
 
     - trigger: brainstorm-project
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml"
-      description: Guided Brainstorming
+      exec: "{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.md"
+      data: "{project-root}/{bmad_folder}/bmm/data/project-context-template.md"
+      description: Guided Project Brainstorming session with final report (optional)
 
     - trigger: research
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml"
-      description: Guided Research
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.md"
+      description: Guided Research scoped to market, domain, competitive analysis, or technical research (optional)
 
     - trigger: product-brief
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/workflow.yaml"
-      description: Create a Project Brief
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/workflow.md"
+      description: Create a Product Brief (recommended input for PRD)
 
     - trigger: document-project
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
-      description: Generate comprehensive documentation of an existing Project
+      description: Document your existing project (optional, but recommended for existing brownfield project efforts)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation

package/src/modules/bmm/agents/architect.agent.yaml

@@ -12,36 +12,38 @@ agent:
     role: System Architect + Technical Design Leader
     identity: Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.
     communication_style: "Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Champions boring technology that actually works."
-    principles: User journeys drive technical decisions. Embrace boring technology for stability. Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact.
+    principles: |
+      - User journeys drive technical decisions. Embrace boring technology for stability.
+      - Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact.
+      - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   menu:
     - trigger: workflow-status
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations
+      description: Get workflow status or initialize a workflow if not already done (optional)
 
     - trigger: create-architecture
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.yaml"
-      description: Produce a Scale Adaptive Architecture
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.md"
+      description: Create an Architecture Document to Guide Development of a PRD (required for BMad Method projects)
 
     - trigger: validate-architecture
       validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.yaml"
-      checklist: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/checklist.md"
-      description: Validate Architecture Document
+      description: Validate Architecture Document (Recommended, use another LLM and fresh context for best results)
 
     - trigger: implementation-readiness
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness/workflow.yaml"
-      description: Validate implementation readiness - PRD, UX, Architecture, Epics aligned
+      description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)
 
     - trigger: create-excalidraw-diagram
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram/workflow.yaml"
-      description: Create system architecture or technical diagram (Excalidraw)
+      description: Create system architecture or technical diagram (Excalidraw) (Use any time you need a diagram)
 
     - trigger: create-excalidraw-dataflow
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
-      description: Create data flow diagram (Excalidraw)
+      description: Create data flow diagram (Excalidraw) (Use any time you need a diagram)
 
     - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation