bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.1

package/src/modules/bmm/sub-modules/claude-code/sub-agents/{trend-spotter.md → bmad-planning/trend-spotter.md}

@@ -97,3 +97,19 @@ Connect trends to actionable insights:
 Distinguish between fads and lasting trends. Look for convergence of multiple trends creating new opportunities. Consider second and third-order effects. Balance optimism with realistic assessment. Identify both opportunities and threats. Consider timing and readiness factors.
 
 When analyzing trends, cast a wide net initially then focus on relevant patterns. Look across industries for analogous developments. Consider contrarian viewpoints and potential trend reversals. Pay attention to generational differences in adoption. Connect trends to specific business implications and actions.
+
+## CRITICAL: Final Report Instructions
+
+**YOU MUST RETURN YOUR COMPLETE TREND ANALYSIS IN YOUR FINAL MESSAGE.**
+
+Your final report MUST include all identified trends, weak signals, and strategic insights in full detail. Do not just describe what you found - provide the complete, formatted trend analysis ready for integration.
+
+Include in your final report:
+
+1. All identified trends with supporting evidence
+2. Weak signals and emerging patterns
+3. Future opportunities and threats
+4. Strategic recommendations based on trends
+5. Timeline and urgency assessments
+
+Remember: Your output will be used directly by the parent agent to populate document sections. Provide complete, ready-to-use content, not summaries or references.

package/src/modules/bmm/sub-modules/claude-code/sub-agents/{user-journey-mapper.md → bmad-planning/user-journey-mapper.md}

@@ -1,3 +1,9 @@
+---
+name: bmm-user-journey-mapper
+description: Maps comprehensive user journeys to identify touchpoints, friction areas, and epic boundaries. use PROACTIVELY when analyzing user flows, defining MVPs, or aligning development priorities with user value
+tools:
+---
+
 # User Journey Mapper
 
 ## Purpose
@@ -99,3 +105,19 @@ Installation → Configuration → First Use → Automation → Advanced Feature
 - Clear epic boundaries derived from journeys
 - Friction points identified for UX focus
 - Development priorities aligned with user value
+
+## CRITICAL: Final Report Instructions
+
+**YOU MUST RETURN YOUR COMPLETE JOURNEY MAPS IN YOUR FINAL MESSAGE.**
+
+Your final report MUST include all the user journey maps you've created in full detail. Do not just describe the journeys or summarize findings - provide the complete, formatted journey documentation that can be directly integrated into product documents.
+
+Include in your final report:
+
+1. All user journey maps with complete step-by-step flows
+2. Touchpoint analysis for each journey
+3. Friction points and opportunities identified
+4. Epic boundary recommendations based on journeys
+5. Priority insights for MVP and feature sequencing
+
+Remember: Your output will be used directly by the parent agent to populate document sections. Provide complete, ready-to-use content, not summaries or references.

package/src/modules/bmm/sub-modules/claude-code/sub-agents/{user-researcher.md → bmad-planning/user-researcher.md}

@@ -54,3 +54,19 @@ Include confidence levels for findings and clearly distinguish between validated
 Look beyond surface-level demographics to understand underlying motivations. Challenge assumptions about user needs with evidence. Consider edge cases and underserved segments. Identify unmet and unarticulated needs. Connect user insights directly to product opportunities. Always ground recommendations in user evidence.
 
 When conducting user research, start with broad exploration before narrowing focus. Use multiple data sources to triangulate findings. Pay attention to what users do, not just what they say. Consider the entire user ecosystem including influencers and decision-makers. Focus on outcomes users want to achieve rather than features they request.
+
+## CRITICAL: Final Report Instructions
+
+**YOU MUST RETURN YOUR COMPLETE USER RESEARCH ANALYSIS IN YOUR FINAL MESSAGE.**
+
+Your final report MUST include all user personas, research findings, and insights in full detail. Do not just describe what you analyzed - provide the complete, formatted user research documentation ready for integration.
+
+Include in your final report:
+
+1. All user personas with complete profiles
+2. User needs and pain points analysis
+3. Behavioral patterns and motivations
+4. Technology comfort levels and preferences
+5. Specific product recommendations based on research
+
+Remember: Your output will be used directly by the parent agent to populate document sections. Provide complete, ready-to-use content, not summaries or references.

package/src/modules/bmm/sub-modules/claude-code/sub-agents/{market-researcher.md → bmad-research/market-researcher.md}

@@ -32,3 +32,20 @@ Structure your findings using tables and lists for easy comparison. Provide exec
 5. Regulatory and compliance considerations
 
 When conducting research, challenge assumptions with data, identify both risks and opportunities, and consider multiple market segments. Your goal is to provide the product team with clear, data-driven insights that inform strategic decisions.
+
+## CRITICAL: Final Report Instructions
+
+**YOU MUST RETURN YOUR COMPLETE MARKET RESEARCH FINDINGS IN YOUR FINAL MESSAGE.**
+
+Your final report MUST include all research findings, competitive analysis, and market insights in full detail. Do not just describe what you researched - provide the complete, formatted research documentation ready for use.
+
+Include in your final report:
+
+1. Complete competitive landscape analysis with feature matrices
+2. Market sizing and opportunity assessment data
+3. User personas and segment analysis
+4. Pricing strategies and business model insights
+5. Technology trends and disruption analysis
+6. Specific, actionable recommendations
+
+Remember: Your output will be used directly by the parent agent for strategic product decisions. Provide complete, ready-to-use research findings, not summaries or references.

package/src/modules/bmm/sub-modules/claude-code/sub-agents/{tech-debt-auditor.md → bmad-research/tech-debt-auditor.md}

@@ -87,3 +87,20 @@ For brownfield systems, understand:
 - The cost of living with debt vs fixing it
 - Strategic debt that enabled fast delivery
 - Debt that's isolated vs debt that's spreading
+
+## CRITICAL: Final Report Instructions
+
+**YOU MUST RETURN YOUR COMPLETE TECHNICAL DEBT AUDIT IN YOUR FINAL MESSAGE.**
+
+Your final report MUST include the full technical debt assessment with all findings and recommendations. Do not just describe the types of debt - provide the complete, formatted audit ready for action.
+
+Include in your final report:
+
+1. Complete debt inventory with locations and severity
+2. Risk assessment matrix with impact analysis
+3. Hot spots and concentrated debt areas
+4. Prioritized remediation roadmap with effort estimates
+5. Cost-benefit analysis for debt reduction
+6. Specific, pragmatic recommendations for immediate action
+
+Remember: Your output will be used directly by the parent agent to plan refactoring and improvements. Provide complete, actionable audit findings, not theoretical discussions.

package/src/modules/bmm/sub-modules/claude-code/sub-agents/{document-reviewer.md → bmad-review/document-reviewer.md}

@@ -83,3 +83,20 @@ Provide an executive summary highlighting overall document readiness and key fin
 Provide constructive feedback with specific examples and improvement suggestions. Prioritize issues by their impact on project success. Consider the document's audience and their needs. Validate against relevant templates and standards. Cross-reference related sections for consistency. Ensure the document enables successful implementation.
 
 When reviewing documents, start with high-level structure and flow before examining details. Validate that examples and scenarios are realistic and comprehensive. Check for missing elements that could impact implementation. Ensure the document provides clear, actionable outcomes for all stakeholders involved.
+
+## CRITICAL: Final Report Instructions
+
+**YOU MUST RETURN YOUR COMPLETE DOCUMENT REVIEW IN YOUR FINAL MESSAGE.**
+
+Your final report MUST include the full review findings with all issues and recommendations. Do not just describe what you reviewed - provide the complete, formatted review report ready for action.
+
+Include in your final report:
+
+1. Executive summary with document readiness assessment
+2. Complete issue list categorized by severity (CRITICAL/HIGH/MEDIUM/LOW)
+3. Specific line/section references for each issue
+4. Concrete improvement recommendations for each finding
+5. Completeness percentage score with justification
+6. Risk assessment and implementation concerns
+
+Remember: Your output will be used directly by the parent agent to improve the document. Provide complete, actionable review findings with specific fixes, not general observations.

package/src/modules/bmm/sub-modules/claude-code/sub-agents/{technical-evaluator.md → bmad-review/technical-evaluator.md}

@@ -49,3 +49,20 @@ Provide comprehensive technology comparison matrices showing pros and cons for e
 Avoid technology bias by evaluating all options objectively based on project needs. Consider both immediate requirements and long-term scalability. Account for team capabilities and willingness to adopt new technologies. Balance innovation with proven, stable solutions. Document all decision rationale thoroughly for future reference. Identify potential technical debt early and plan mitigation strategies.
 
 When evaluating technologies, start with problem requirements rather than preferred solutions. Consider the full lifecycle including development, testing, deployment, and maintenance. Evaluate ecosystem compatibility and operational requirements. Always plan for failure scenarios and potential migration paths if technologies need to be changed.
+
+## CRITICAL: Final Report Instructions
+
+**YOU MUST RETURN YOUR COMPLETE TECHNICAL EVALUATION IN YOUR FINAL MESSAGE.**
+
+Your final report MUST include the full technology assessment with all comparisons and recommendations. Do not just describe the evaluation process - provide the complete, formatted evaluation ready for decision-making.
+
+Include in your final report:
+
+1. Complete technology comparison matrix with scores
+2. Detailed pros/cons analysis for each option
+3. Risk assessment with mitigation strategies
+4. Implementation complexity and effort estimates
+5. Primary recommendation with clear rationale
+6. Alternative approaches and fallback options
+
+Remember: Your output will be used directly by the parent agent to make technology decisions. Provide complete, actionable evaluations with specific recommendations, not general guidelines.

package/src/modules/bmm/sub-modules/claude-code/sub-agents/{test-coverage-analyzer.md → bmad-review/test-coverage-analyzer.md}

@@ -89,3 +89,20 @@ For brownfield systems:
 - Missing regression tests for fixed bugs
 - Integration tests as substitutes for unit tests
 - Test data management challenges
+
+## CRITICAL: Final Report Instructions
+
+**YOU MUST RETURN YOUR COMPLETE TEST COVERAGE ANALYSIS IN YOUR FINAL MESSAGE.**
+
+Your final report MUST include the full testing assessment with coverage metrics and improvement recommendations. Do not just describe testing patterns - provide the complete, formatted analysis ready for action.
+
+Include in your final report:
+
+1. Complete test coverage metrics by type and module
+2. Critical gaps and untested paths with risk assessment
+3. Test quality issues (flaky, slow, brittle tests)
+4. Testing strategy evaluation and patterns used
+5. Prioritized improvement roadmap with effort estimates
+6. Specific recommendations for immediate action
+
+Remember: Your output will be used directly by the parent agent to improve test coverage and quality. Provide complete, actionable analysis with specific improvements, not general testing advice.

package/src/modules/bmm/tasks/{daily-standup.md → daily-standup.xml}

@@ -1,19 +1,14 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# Daily Standup v1.0
-
-```xml
-<task id="bmad/bmm/tasks/daily-standup.md" name="Daily Standup">
+<task id="bmad/bmm/tasks/daily-standup.xml" name="Daily Standup">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>
     <i>HALT immediately when halt-conditions are met</i>
-    <i>Each &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</i>
+    <i>Each action tag within a step tag is a REQUIRED action to complete that step</i>
     <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
   </llm>
   <flow>
     <step n="1" title="Project Context Discovery">
-      <action>Check for stories folder at {project-root}{output_folder}/stories/ directory</action>
+      <action>Check for stories folder at {project-root}{output_folder}/stories/</action>
       <action>Find current story by identifying highest numbered story file</action>
       <action>Read story status (In Progress, Ready for Review, etc.)</action>
       <action>Extract agent notes from Dev Agent Record, TEA Results, PO Notes sections</action>
@@ -23,15 +18,15 @@
 
     <step n="2" title="Initialize Standup with Context">
       <output>
-🏃 DAILY STANDUP - Story-{{number}}: {{title}}
+        🏃 DAILY STANDUP - Story-{{number}}: {{title}}
 
-Current Sprint Status:
-- Active Story: story-{{number}} ({{status}} - {{percentage}}% complete)
-- Next in Queue: story-{{next-number}}: {{next-title}}
-- Blockers: {{blockers-from-story}}
+        Current Sprint Status:
+        - Active Story: story-{{number}} ({{status}} - {{percentage}}% complete)
+        - Next in Queue: story-{{next-number}}: {{next-title}}
+        - Blockers: {{blockers-from-story}}
 
-Team assembled based on story participants:
-{{ List Agents from {project-root}/bmad/_cfg/agent-party.xml }}
+        Team assembled based on story participants:
+        {{ List Agents from {project-root}/bmad/_cfg/agent-manifest.csv }}
       </output>
     </step>
 
@@ -44,18 +39,18 @@ Team assembled based on story participants:
 
     <step n="4" title="Create Standup Summary">
       <output>
-📋 STANDUP SUMMARY:
-Key Items from Story File:
-- {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks)
-- Blocker: {{main-blocker}}
-- Next: {{next-story-reference}}
+        📋 STANDUP SUMMARY:
+        Key Items from Story File:
+        - {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks)
+        - Blocker: {{main-blocker}}
+        - Next: {{next-story-reference}}
 
-Action Items:
-- {{agent}}: {{action-item}}
-- {{agent}}: {{action-item}}
-- {{agent}}: {{action-item}}
+        Action Items:
+        - {{agent}}: {{action-item}}
+        - {{agent}}: {{action-item}}
+        - {{agent}}: {{action-item}}
 
-Need extended discussion? Use *party-mode for detailed breakout.
+        Need extended discussion? Use *party-mode for detailed breakout.
       </output>
     </step>
   </flow>
@@ -87,5 +82,4 @@ Need extended discussion? Use *party-mode for detailed breakout.
     <i>No deep dives (suggest breakout if needed)</i>
     <i>If no stories folder detected, run general standup format</i>
   </llm>
-</task>
-```
+</task>

package/src/modules/bmm/tasks/{retrospective.md → retrospective.xml}

@@ -1,14 +1,9 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# Retrospective v1.0
-
-```xml
-<task id="bmad/bmm/tasks/retrospective.md" name="Team Retrospective">
+<task id="bmad/bmm/tasks/retrospective.xml" name="Team Retrospective">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>
     <i>HALT immediately when halt-conditions are met</i>
-    <i>Each &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</i>
+    <i>Each andlt;actionandgt; within andlt;stepandgt; is a REQUIRED action to complete that step</i>
     <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
   </llm>
   <flow>
@@ -34,24 +29,24 @@
 
     <step n="3" title="Initialize Retrospective with Context">
       <output>
-🔄 TEAM RETROSPECTIVE - Epic {{number}}: {{Epic Name}}
+        🔄 TEAM RETROSPECTIVE - Epic {{number}}: {{Epic Name}}
 
-Bob (Scrum Master) facilitating
+        Bob (Scrum Master) facilitating
 
-Epic Summary:
-- Completed: {{completed}}/{{total}} stories ({{percentage}}%)
-- Velocity: {{actual-points}} story points (planned: {{planned-points}})
-- Duration: {{actual-sprints}} sprints (planned: {{planned-sprints}})
-- Technical Debt: {{debt-items}}
+        Epic Summary:
+        - Completed: {{completed}}/{{total}} stories ({{percentage}}%)
+        - Velocity: {{actual-points}} story points (planned: {{planned-points}})
+        - Duration: {{actual-sprints}} sprints (planned: {{planned-sprints}})
+        - Technical Debt: {{debt-items}}
 
-Next Epic Preview: Epic {{next-number}}: {{Next Epic Name}}
-- Dependencies on Epic {{number}}: {{dependencies}}
-- Preparation needed: {{preparation-gaps}}
+        Next Epic Preview: Epic {{next-number}}: {{Next Epic Name}}
+        - Dependencies on Epic {{number}}: {{dependencies}}
+        - Preparation needed: {{preparation-gaps}}
 
-Team assembled for reflection:
-{{agents-based-on-story-records}}
+        Team assembled for reflection:
+        {{agents-based-on-story-records}}
 
-Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}
+        Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}
       </output>
     </step>
 
@@ -75,14 +70,14 @@ Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}
       <action>Assigns ownership to action items</action>
       <action>Creates preparation sprint tasks if needed</action>
       <output>
-📝 EPIC {{number}} ACTION ITEMS:
-{{numbered-action-items-with-owners}}
+        📝 EPIC {{number}} ACTION ITEMS:
+        {{numbered-action-items-with-owners}}
 
-🚀 EPIC {{next-number}} PREPARATION SPRINT:
-{{preparation-tasks-with-timeline}}
+        🚀 EPIC {{next-number}} PREPARATION SPRINT:
+        {{preparation-tasks-with-timeline}}
 
-⚠️ CRITICAL PATH:
-{{critical-dependencies-and-timeline}}
+        ⚠️ CRITICAL PATH:
+        {{critical-dependencies-and-timeline}}
       </output>
     </step>
 
@@ -106,5 +101,4 @@ Focus: Learning from Epic {{number}} and preparing for Epic {{next-number}}
     <i>End with team agreements and clear next steps</i>
     <i>Two-part format: Epic Review + Next Epic Preparation</i>
   </llm>
-</task>
-```
+</task>

package/src/modules/bmm/teams/team-fullstack.yaml

@@ -0,0 +1,11 @@
+# <!-- Powered by BMAD-CORE™ -->
+bundle:
+  name: Team Plan and Architect
+  icon: 🚀
+  description: Team capable of project analysis, design, and architecture.
+agents:
+  - analyst
+  - architect
+  - pm
+  - sm
+  - ux-designer

package/src/modules/bmm/teams/team-gamedev.yaml

@@ -7,3 +7,8 @@ agents:
   - game-designer
   - game-dev
   - game-architect
+
+workflows:
+  - brainstorm-game
+  - game-brief
+  - gdd