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

package/src/modules/bmb/workflows/module-brief/README.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-The Module Brief workflow creates comprehensive blueprints for building new BMAD modules using strategic analysis and creative vision. It serves as the essential planning phase that transforms initial ideas into detailed, actionable specifications ready for implementation with the build-module workflow.
+The Module Brief workflow creates comprehensive blueprints for building new BMAD modules using strategic analysis and creative vision. It serves as the essential planning phase that transforms initial ideas into detailed, actionable specifications ready for implementation with the create-module workflow.
 
 ## Key Features
 
@@ -61,9 +61,9 @@ module-brief/
 
 ## Workflow Process
 
-### Phase 1: Foundation & Context (Steps 1-3)
+### Phase 1: Foundation and Context (Steps 1-3)
 
-**Mode Selection & Input Gathering**
+**Mode Selection and Input Gathering**
 
 - Choose operational mode (Interactive, Express, YOLO)
 - Check for and optionally load existing brainstorming results
@@ -101,7 +101,7 @@ module-brief/
 - Define input-process-output flows for each workflow
 - Assess complexity levels and implementation priorities
 
-### Phase 3: Validation & User Experience (Steps 6-7)
+### Phase 3: Validation and User Experience (Steps 6-7)
 
 **User Journey Mapping**
 
@@ -110,7 +110,7 @@ module-brief/
 - Validate end-to-end functionality and value delivery
 - Identify potential friction points and optimization opportunities
 
-**Technical Planning & Requirements**
+**Technical Planning and Requirements**
 
 - Assess data requirements and storage needs
 - Map integration points with other modules and external systems
@@ -133,27 +133,27 @@ module-brief/
 - Prioritize features and capabilities by value and complexity
 - Create clear milestones and success checkpoints
 
-### Phase 5: Enhancement & Risk Management (Steps 10-12)
+### Phase 5: Enhancement and Risk Management (Steps 10-12)
 
-**Creative Features & Special Touches** (Optional)
+**Creative Features and Special Touches** (Optional)
 
 - Design easter eggs and delightful user interactions
 - Plan module lore and thematic consistency
 - Add personality quirks and creative responses
 - Develop backstories and universe building
 
-**Risk Assessment & Mitigation**
+**Risk Assessment and Mitigation**
 
 - Identify technical, usability, and scope risks
 - Develop mitigation strategies for each risk category
 - Plan contingency approaches for potential challenges
 - Document decision points and alternative paths
 
-**Final Review & Export Preparation**
+**Final Review and Export Preparation**
 
 - Comprehensive review of all brief sections
 - Validation against quality and completeness criteria
-- Preparation for seamless handoff to build-module workflow
+- Preparation for seamless handoff to create-module workflow
 - Export readiness confirmation with actionable specifications
 
 ## Output
@@ -161,7 +161,7 @@ module-brief/
 ### Generated Files
 
 - **Module Brief Document**: Comprehensive planning document at `{output_folder}/module-brief-{module_code}-{date}.md`
-- **Strategic Specifications**: Ready-to-implement blueprint for build-module workflow
+- **Strategic Specifications**: Ready-to-implement blueprint for create-module workflow
 
 ### Output Structure
 
@@ -178,7 +178,7 @@ The module brief contains detailed specifications across multiple sections:
 9. **Creative Features** - Special touches, easter eggs, module lore
 10. **Risk Assessment** - Technical, usability, scope risks with mitigation
 11. **Implementation Notes** - Priority order, design decisions, open questions
-12. **Resources & References** - Inspiration sources, similar modules, technical references
+12. **Resources and References** - Inspiration sources, similar modules, technical references
 
 ## Requirements
 
@@ -203,7 +203,7 @@ The module brief contains detailed specifications across multiple sections:
 
 ### After Completion
 
-1. **Use as Blueprint** - Feed the brief directly into build-module workflow for implementation
+1. **Use as Blueprint** - Feed the brief directly into create-module workflow for implementation
 2. **Review with Stakeholders** - Validate assumptions and gather feedback before building
 3. **Update as Needed** - Treat as living document that evolves with implementation learnings
 4. **Reference During Development** - Use as north star for design decisions and scope management
@@ -254,11 +254,11 @@ To customize this workflow:
 
 For issues or questions:
 
-- Review the workflow creation guide at `/bmad/bmb/workflows/build-workflow/workflow-creation-guide.md`
+- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
 - Study existing module examples in `/bmad/` for patterns and inspiration
 - Validate output using `checklist.md`
-- Consult module structure guide at `build-module/module-structure.md`
+- Consult module structure guide at `create-module/module-structure.md`
 
 ---
 
-_Part of the BMad Method v5 - BMB (Builder) Module_
+_Part of the BMad Method v6 - BMB (Builder) Module_

package/src/modules/bmb/workflows/module-brief/checklist.md

@@ -8,7 +8,7 @@
 - [ ] Target users are clearly defined
 - [ ] Unique value proposition is articulated
 
-## Vision & Concept
+## Vision and Concept
 
 - [ ] Problem being solved is clearly stated
 - [ ] Solution approach is explained
@@ -80,9 +80,9 @@
 
 ## Implementation Readiness
 
-- [ ] Brief provides enough detail for build-module workflow
-- [ ] Agent specifications sufficient for build-agent workflow
-- [ ] Workflow descriptions ready for build-workflow
+- [ ] Brief provides enough detail for create-module workflow
+- [ ] Agent specifications sufficient for create-agent workflow
+- [ ] Workflow descriptions ready for create-workflow
 - [ ] Resource requirements are clear
 - [ ] Success metrics are measurable
 

package/src/modules/bmb/workflows/module-brief/instructions.md

@@ -1,7 +1,8 @@
 # Module Brief Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/module-brief/workflow.yaml</critical>
+<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/bmb/workflows/module-brief/workflow.yaml</critical>
+<critical>Communicate in {communication_language} throughout the module brief creation process</critical>
 
 <workflow>
 
@@ -248,16 +249,17 @@ For each risk, note mitigation strategy.
 </step>
 
 <step n="12" goal="Final review and export readiness">
-<action>Review all sections with user</action>
-<action>Ensure module brief is ready for build-module workflow</action>
+<action>Review all sections with {user_name}</action>
+<action>Ensure module brief is ready for create-module workflow</action>
 
-Ask if they want to:
+<ask>Would {user_name} like to:
 
-1. Proceed directly to build-module workflow
+1. Proceed directly to create-module workflow
 2. Save and refine later
 3. Generate additional planning documents
+   </ask>
 
-<action>Highlight that this brief can be fed directly into build-module workflow!</action>
+<action>Inform {user_name} in {communication_language} that this brief can be fed directly into create-module workflow</action>
 
 <template-output>final_brief</template-output>
 </step>

package/src/modules/bmb/workflows/module-brief/template.md

@@ -144,7 +144,7 @@ How we'll know the module is successful:
 **Deliverables:**
 {{phase2_deliverables}}
 
-### Phase 3: Polish & Optimization
+### Phase 3: Polish and Optimization
 
 **Timeline:** {{phase3_timeline}}
 
@@ -161,11 +161,11 @@ How we'll know the module is successful:
 
 {{creative_features}}
 
-### Easter Eggs & Delighters
+### Easter Eggs and Delighters
 
 {{easter_eggs}}
 
-### Module Lore & Theming
+### Module Lore and Theming
 
 {{module_lore}}
 
@@ -209,7 +209,7 @@ How we'll know the module is successful:
 
 ---
 
-## Resources & References
+## Resources and References
 
 ### Inspiration Sources
 
@@ -235,7 +235,7 @@ How we'll know the module is successful:
 
 {{detailed_workflow_specs}}
 
-### C. Data Structures & Schemas
+### C. Data Structures and Schemas
 
 {{data_schemas}}
 
@@ -248,14 +248,14 @@ How we'll know the module is successful:
 ## Next Steps
 
 1. **Review this brief** with stakeholders
-2. **Run build-module workflow** using this brief as input
-3. **Create first agent** using build-agent workflow
-4. **Develop initial workflows** using build-workflow
+2. **Run create-module workflow** using this brief as input
+3. **Create first agent** using create-agent workflow
+4. **Develop initial workflows** using create-workflow
 5. **Test MVP** with target users
 
 ---
 
-_This Module Brief is ready to be fed directly into the build-module workflow for scaffolding and implementation._
+_This Module Brief is ready to be fed directly into the create-module workflow for scaffolding and implementation._
 
 **Module Viability Score:** {{viability_score}}/10
 **Estimated Development Effort:** {{effort_estimate}}

package/src/modules/bmb/workflows/module-brief/workflow.yaml

@@ -8,14 +8,13 @@ config_source: "{project-root}/bmad/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
-src_impact: "{config_source}:src_impact"
 date: system-generated
 
 # Optional input docs that enhance module planning
 recommended_inputs:
   - brainstorming_results: "{output_folder}/brainstorming-*.md"
   - existing_modules: "{project-root}/bmad/"
-  - module_examples: "{project-root}/bmad/bmb/workflows/build-module/module-structure.md"
+  - module_examples: "{project-root}/bmad/bmb/workflows/create-module/module-structure.md"
 
 # Module path and component files
 installed_path: "{project-root}/bmad/bmb/workflows/module-brief"
@@ -26,5 +25,7 @@ validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/module-brief-{{module_code}}-{{date}}.md"
 
-# No special tools required
-required_tools: []
+standalone: true
+
+# Web bundle configuration
+web_bundle: false # BMB workflows run locally in BMAD-METHOD project

package/src/modules/bmb/workflows/redoc/checklist.md

@@ -1,6 +1,6 @@
 # ReDoc Workflow Validation Checklist
 
-## Initialization & Setup
+## Initialization and Setup
 
 - [ ] All BMAD convention documents loaded and understood
 - [ ] Target path validated and exists
@@ -66,7 +66,7 @@
 - [ ] Frontmatter syntax is correct and dates are current
 - [ ] No redundant explanation of standard BMAD patterns
 
-## Validation & Reporting
+## Validation and Reporting
 
 - [ ] All planned documentation items created/updated
 - [ ] Frontmatter dates verified as current across all files

package/src/modules/bmb/workflows/redoc/instructions.md

@@ -1,10 +1,13 @@
 # ReDoc Workflow Instructions
 
-<workflow>
-
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-<critical>You MUST have already loaded and processed: {project_root}/src/modules/bmb/workflows/redoc/workflow.yaml</critical>
+<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}/src/modules/bmb/workflows/redoc/workflow.yaml</critical>
+<critical>Communicate in {communication_language} throughout the documentation process</critical>
 <critical>This is an AUTONOMOUS workflow - minimize user interaction unless clarification is absolutely required</critical>
+<critical>IMPORTANT: Process ONE document at a time to avoid token limits. Each README should be created individually, not batched.</critical>
+<critical>When using Task tool with sub-agents: Only request ONE workflow or agent documentation per invocation to prevent token overflow.</critical>
+
+<workflow>
 
 <step n="1" goal="Load BMAD conventions and initialize">
 <action>Load ALL BMAD convention documents from {bmad_conventions}:
@@ -69,7 +72,11 @@
 </step>
 
 <step n="3" goal="Process leaf-level documentation" repeat="for-each-leaf-item">
-<action>For each individual workflow folder in execution plan:
+<critical>TOKEN LIMIT WARNING: Process ONE item at a time to prevent token overflow issues.</critical>
+<critical>If using Task tool with sub-agents: NEVER batch multiple workflows/agents in a single invocation.</critical>
+<critical>Each README creation should be a separate operation with its own file save.</critical>
+<critical>Sequential processing is MANDATORY - do not attempt parallel documentation generation.</critical>
+<action>For each individual workflow folder in execution plan (PROCESS ONE AT A TIME):
 1. Read ALL files completely:
    - workflow.yaml (metadata, purpose, configuration)
    - instructions.md (step structure, goals)
@@ -94,9 +101,11 @@
    - Focus on DISTINCTIVE features, not boilerplate
 
 4. Save README.md to workflow folder
-   </action>
 
-<action>For each individual agent file in execution plan:
+<critical>If multiple workflows need documentation, process them SEQUENTIALLY not in parallel. Each workflow gets its own complete processing cycle.</critical>
+</action>
+
+<action>For each individual agent file in execution plan (PROCESS ONE AT A TIME):
 
 1. Read agent definition file completely:
    - XML structure and metadata
@@ -121,7 +130,7 @@
 4. Save README.md
    </action>
 
-<check>If clarification needed about purpose or unique features → Ask user briefly, then continue</check>
+<action if="clarification needed about purpose or unique features">Ask user briefly, then continue</action>
 </step>
 
 <step n="4" goal="Process mid-level folder documentation" if="target_type requires folder docs">
@@ -229,6 +238,7 @@
 - Any catalog files created
 - Files skipped or requiring manual review (if any)
 - Coverage: X% of items documented
+- Processing notes: Confirm sequential processing was used to avoid token limits
   </action>
 
 <action>Display summary to user</action>
@@ -247,9 +257,9 @@ For each README with last-redoc-date frontmatter:
 </step>
 
 <step n="8" goal="Completion">
-<action>Confirm autonomous workflow execution complete</action>
+<action>Confirm to {user_name} in {communication_language} that autonomous workflow execution is complete</action>
 <action>Provide path to all updated documentation</action>
-<action>Suggest next steps if needed (e.g., "Run redoc on parent module to update references")</action>
+<action>Suggest next steps if needed</action>
 </step>
 
 </workflow>

package/src/modules/bmb/workflows/redoc/workflow.yaml

@@ -5,9 +5,8 @@ author: "BMad"
 
 # Critical variables
 config_source: "{project-root}/bmad/bmb/config.yaml"
-output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
-date: system-generated
+communication_language: "{config_source}:communication_language"
 
 # Required knowledge base - BMAD conventions and patterns
 bmad_conventions:
@@ -29,5 +28,7 @@ validation: "{installed_path}/checklist.md"
 # Configuration
 autonomous: true # Runs without user checkpoints unless clarification needed
 
-# Tool Requirements - Using built-in file system tools
-required_tools: []
+standalone: true
+
+# Web bundle configuration
+web_bundle: false # BMB workflows run locally in BMAD-METHOD project

package/src/modules/bmm/README.md

@@ -0,0 +1,141 @@
+# BMM - BMad Method Module
+
+The BMM (BMad Method Module) is the core orchestration system for the BMad Method, providing comprehensive software development lifecycle management through specialized agents, workflows, teams, and tasks.
+
+## 📚 Essential Reading
+
+**Before using BMM, you MUST read the [BMM v6 Workflows Guide](./workflows/README.md).** This document explains the revolutionary v6a workflow system and how all components work together.
+
+## Module Structure
+
+### 🤖 `/agents`
+
+Specialized AI agents for different development roles:
+
+- **PM** (Product Manager) - Product planning and requirements
+- **Analyst** - Business analysis and research
+- **Architect** - Technical architecture and design
+- **SM** (Scrum Master) - Sprint and story management
+- **DEV** (Developer) - Code implementation
+- **TEA** (Test Architect) - Test Architect
+- **UX** - User experience design
+- And more specialized roles
+
+**Game Development Agents** (Optional):
+During installation, you can optionally include game development specialists:
+
+- **Game Designer** - Creative vision and game design documents (GDD)
+- **Game Developer** - Game-specific implementation
+- **Game Architect** - Game systems and technical infrastructure
+
+These agents come with specialized workflows (`brainstorm-game`, `game-brief`, `gdd`) and are only installed if you select "Include Game Planning Agents and Workflows" during BMM installation.
+
+### 📋 `/workflows`
+
+The heart of BMM - structured workflows for the four development phases:
+
+1. **Analysis Phase** (Optional)
+   - `brainstorm-project` - Project ideation
+   - `research` - Market/technical research
+   - `product-brief` - Product strategy
+
+2. **Planning Phase** (Required)
+   - `prd` - Scale-adaptive project planning
+   - Routes to appropriate documentation based on project complexity
+
+3. **Solutioning Phase** (Level 3-4 projects)
+   - `3-solutioning` - Architecture design
+   - `tech-spec` - Epic-specific technical specifications
+
+4. **Implementation Phase** (Iterative)
+   - `create-story` - Story drafting (SM agent)
+   - `story-ready` - Approve story for development (SM agent)
+   - `story-context` - Expertise injection (SM agent)
+   - `dev-story` - Implementation (DEV agent)
+   - `story-done` - Mark story done (DEV agent)
+   - `code-review` - Quality validation (DEV/SR agent)
+   - `correct-course` - Issue resolution
+   - `retrospective` - Continuous improvement
+
+### 👥 `/teams`
+
+Pre-configured agent teams for different project types and phases. Teams coordinate multiple agents working together on complex tasks.
+
+### 📝 `/tasks`
+
+Reusable task definitions that agents execute within workflows. These are the atomic units of work that compose into larger workflows.
+
+### 🔧 `/sub-modules`
+
+Extension modules that add specialized capabilities to BMM.
+
+### 🏗️ `/testarch`
+
+Test architecture and quality assurance components. The **[Test Architect (TEA) Guide](./testarch/README.md)** provides comprehensive testing strategy across 9 workflows: framework setup, CI/CD, test design, ATDD, automation, traceability, NFR assessment, quality gates, and test review.
+
+## Quick Start
+
+```bash
+# Load the PM agent - either via slash command or drag and drop or @ the agent file.
+# Once loaded, the agent should greet you and offer a menu of options. You can enter:
+`*prd`
+```
+
+## Key Concepts
+
+### Scale Levels
+
+BMM automatically adapts to project complexity:
+
+- **Level 0**: Single atomic change
+- **Level 1**: 1-10 stories, minimal documentation
+- **Level 2**: 5-15 stories, focused PRD
+- **Level 3**: 12-40 stories, full architecture
+- **Level 4**: 40+ stories, enterprise scale
+
+### Just-In-Time Design
+
+Technical specifications are created one epic at a time during implementation, not all upfront, allowing for learning and adaptation.
+
+### Story State Machine
+
+Stories flow through a 4-state lifecycle tracked in the status file:
+
+```
+BACKLOG → TODO → IN PROGRESS → DONE
+```
+
+- **BACKLOG**: Ordered list of stories to be drafted (populated at phase transition)
+- **TODO**: Single story ready for SM to draft (or drafted, awaiting approval)
+- **IN PROGRESS**: Single story approved for DEV to implement
+- **DONE**: Completed stories with dates and points
+
+Agents never search for "next story" - they always read the exact story from the status file. Simple workflows (`story-ready`, `story-done`) advance the queue automatically.
+
+### Context Injection
+
+Story-specific technical guidance is generated dynamically, providing developers with exactly the expertise needed for each task.
+
+## Integration with BMad Core
+
+BMM integrates seamlessly with the BMad Core framework, leveraging:
+
+- The agent execution engine
+- Workflow orchestration
+- Task management
+- Team coordination
+
+## Related Documentation
+
+- [BMM Workflows Guide](./workflows/README.md) - **Start here!**
+- [Test Architect (TEA) Guide](./testarch/README.md) - Quality assurance and testing strategy
+
+## Best Practices
+
+1. **Always start with the workflows** - Let workflows guide your process
+2. **Respect the scale** - Don't over-document small projects
+3. **Trust the process** - The methodology has been carefully designed
+
+---
+
+For detailed information about the complete BMad Method workflow system, see the [BMM Workflows README](./workflows/README.md).

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

@@ -0,0 +1,74 @@
+# BMAD™ Method Core Configuration
+
+code: bmm
+name: "BMM: BMad Method Agile-AI Driven-Development"
+default_selected: true # This module will be selected by default for new installations
+
+prompt:
+  - "Thank you for choosing the BMAD™ Method, your gateway to dreaming, planning"
+  - "and building with real world proven techniques."
+  - "All paths are relative to project root, with no leading slash."
+
+# Variables from Core Config inserted:
+## user_name
+## communication_language
+## output_folder
+
+project_name:
+  prompt: "What is the title of your project you will be working on?"
+  default: "{directory_name}"
+  result: "{value}"
+
+include_game_planning:
+  prompt: "Include Game Planning Agents and Workflows?"
+  default: false
+  result: "{value}"
+
+user_skill_level:
+  prompt:
+    - "What is your technical experience level?"
+    - "This affects how agents explain concepts to you (NOT document content)."
+    - "Documents are always concise for LLM efficiency."
+  default: "intermediate"
+  result: "{value}"
+  single-select:
+    - value: "beginner"
+      label: "Beginner - New to development, explain concepts clearly"
+    - value: "intermediate"
+      label: "Intermediate - Familiar with development, balance explanation with efficiency"
+    - value: "expert"
+      label: "Expert - Deep technical knowledge, be direct and technical"
+
+tech_docs:
+  prompt: "Where is Technical Documentation located within the project?"
+  default: "docs"
+  result: "{project-root}/{value}"
+
+dev_story_location:
+  prompt: "Where should development stories be stored?"
+  default: "docs/stories"
+  result: "{project-root}/{value}"
+
+# TEA Agent Configuration
+tea_use_mcp_enhancements:
+  prompt: "Enable Playwright MCP capabilities (healing, exploratory, verification)?"
+  default: false
+  result: "{value}"
+# kb_location:
+#   prompt: "Where should bmad knowledge base articles be stored?"
+#   default: "~/bmad/bmm/kb.md"
+#   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/_module-installer/installer.js

@@ -9,7 +9,7 @@ const platformCodes = require(path.join(__dirname, '../../../../tools/cli/lib/pl
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-menu-config.yaml
+ * @param {Object} options.config - Module configuration from install-config.yaml
  * @param {Array<string>} options.installedIDEs - Array of IDE codes that were installed
  * @param {Object} options.logger - Logger instance for output
  * @returns {Promise<boolean>} - Success status

package/src/modules/bmm/_module-installer/platform-specifics/claude-code.js

@@ -5,7 +5,7 @@ const chalk = require('chalk');
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-menu-config.yaml
+ * @param {Object} options.config - Module configuration from install-config.yaml
  * @param {Object} options.logger - Logger instance for output
  * @param {Object} options.platformInfo - Platform metadata from global config
  * @returns {Promise<boolean>} - Success status

package/src/modules/bmm/_module-installer/platform-specifics/windsurf.js

@@ -5,7 +5,7 @@ const chalk = require('chalk');
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-menu-config.yaml
+ * @param {Object} options.config - Module configuration from install-config.yaml
  * @param {Object} options.logger - Logger instance for output
  * @returns {Promise<boolean>} - Success status
  */

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

@@ -0,0 +1,43 @@
+# Business Analyst Agent Definition
+
+agent:
+  metadata:
+    id: bmad/bmm/agents/analyst.md
+    name: Mary
+    title: Business Analyst
+    icon: 📊
+    module: bmm
+
+  persona:
+    role: Strategic Business Analyst + Requirements Expert
+    identity: Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague business needs into actionable technical specifications. Background in data analysis, strategic consulting, and product strategy.
+    communication_style: Analytical and systematic in approach - presents findings with clear data support. Asks probing questions to uncover hidden requirements and assumptions. Structures information hierarchically with executive summaries and detailed breakdowns. Uses precise, unambiguous language when documenting requirements. Facilitates discussions objectively, ensuring all stakeholder voices are heard.
+    principles:
+      - I believe that every business challenge has underlying root causes waiting to be discovered through systematic investigation and data-driven analysis.
+      - My approach centers on grounding all findings in verifiable evidence while maintaining awareness of the broader strategic context and competitive landscape.
+      - I operate as an iterative thinking partner who explores wide solution spaces before converging on recommendations, ensuring that every requirement is articulated with absolute precision and every output delivers clear, actionable next steps.
+
+  menu:
+    - trigger: workflow-init
+      workflow: "{project-root}/bmad/bmm/workflows/workflow-status/init/workflow.yaml"
+      description: Start a new sequenced workflow path
+
+    - trigger: workflow-status
+      workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
+      description: Check workflow status and get recommendations (START HERE!)
+
+    - trigger: brainstorm-project
+      workflow: "{project-root}/bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml"
+      description: Guide me through Brainstorming
+
+    - trigger: product-brief
+      workflow: "{project-root}/bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml"
+      description: Produce Project Brief
+
+    - trigger: document-project
+      workflow: "{project-root}/bmad/bmm/workflows/document-project/workflow.yaml"
+      description: Generate comprehensive documentation of an existing Project
+
+    - trigger: research
+      workflow: "{project-root}/bmad/bmm/workflows/1-analysis/research/workflow.yaml"
+      description: Guide me through Research