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

package/src/modules/bmgd/workflows/workflow-status/workflow-status-template.yaml

@@ -0,0 +1,24 @@
+# Workflow Status Template (BMGD)
+
+# This tracks progress through BMGD methodology Pre-production, Design, and Technical phases.
+# Implementation phase is tracked separately in sprint-status.yaml
+
+# STATUS DEFINITIONS:
+# ==================
+# Initial Status (before completion):
+#   - required: Must be completed to progress
+#   - optional: Can be completed but not required
+#   - recommended: Strongly suggested but not required
+#   - conditional: Required only if certain conditions met (e.g., if_narrative_focused)
+#
+# Completion Status:
+#   - {file-path}: File created/found (e.g., "docs/gdd.md")
+#   - skipped: Optional/conditional workflow that was skipped
+
+generated: "{{generated}}"
+project: "{{project_name}}"
+project_type: "{{project_type}}"
+selected_track: "{{selected_track}}"
+field_type: "{{field_type}}"
+workflow_path: "{{workflow_path_file}}"
+workflow_status: "{{workflow_items}}"

package/src/modules/bmgd/workflows/workflow-status/workflow.yaml

@@ -0,0 +1,30 @@
+# Workflow Status - Master Router and Status Tracker for BMGD
+name: workflow-status
+description: 'Lightweight status checker - answers "what should I do now?" for any game dev agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/_bmad/bmgd/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+game_dev_experience: "{config_source}:game_dev_experience"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/_bmad/bmgd/workflows/workflow-status"
+instructions: "{installed_path}/instructions.md"
+
+# Template for status file creation (used by workflow-init)
+template: "{installed_path}/workflow-status-template.yaml"
+
+# Path definitions for project types
+path_files: "{installed_path}/paths/"
+
+# Output configuration - reads existing status
+default_output_file: "{output_folder}/bmgd-workflow-status.yaml"
+
+standalone: true
+
+web_bundle: false

package/src/modules/bmm/README.md

@@ -1,141 +1,127 @@
 # 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.
+Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
 
-## 📚 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:
+## 📚 Complete Documentation
 
-- **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
+👉 **[BMM Documentation Hub](./docs/index.md)** - Start here for complete guides, tutorials, and references
 
-**Game Development Agents** (Optional):
-During installation, you can optionally include game development specialists:
+**Quick Links:**
 
-- **Game Designer** - Creative vision and game design documents (GDD)
-- **Game Developer** - Game-specific implementation
-- **Game Architect** - Game systems and technical infrastructure
+- **[Quick Start Guide](./docs/quick-start.md)** - New to BMM? Start here (15 min)
+- **[Agents Guide](./docs/agents-guide.md)** - Meet your 12 specialized AI agents (45 min)
+- **[Scale Adaptive System](./docs/scale-adaptive-system.md)** - How BMM adapts to project size (42 min)
+- **[FAQ](./docs/faq.md)** - Quick answers to common questions
+- **[Glossary](./docs/glossary.md)** - Key terminology reference
 
-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`
+## 🏗️ Module Structure
 
-The heart of BMM - structured workflows for the four development phases:
+This module contains:
 
-1. **Analysis Phase** (Optional)
-   - `brainstorm-project` - Project ideation
-   - `research` - Market/technical research
-   - `product-brief` - Product strategy
+```
+bmm/
+├── agents/          # 12 specialized AI agents (PM, Architect, SM, DEV, TEA, etc.)
+├── workflows/       # 34 workflows across 4 phases + testing
+├── teams/           # Pre-configured agent groups
+├── tasks/           # Atomic work units
+├── testarch/        # Comprehensive testing infrastructure
+└── docs/            # Complete user documentation
+```
 
-2. **Planning Phase** (Required)
-   - `prd` - Scale-adaptive project planning
-   - Routes to appropriate documentation based on project complexity
+### Agent Roster
 
-3. **Solutioning Phase** (Level 3-4 projects)
-   - `3-solutioning` - Architecture design
-   - `tech-spec` - Epic-specific technical specifications
+**Core Development:** PM, Analyst, Architect, SM, DEV, TEA, UX Designer, Technical Writer
+**Game Development:** Game Designer, Game Developer, Game Architect
+**Orchestration:** BMad Master (from Core)
 
-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
+👉 **[Full Agents Guide](./docs/agents-guide.md)** - Roles, workflows, and when to use each agent
 
-### 👥 `/teams`
+### Workflow Phases
 
-Pre-configured agent teams for different project types and phases. Teams coordinate multiple agents working together on complex tasks.
+**Phase 0:** Documentation (brownfield only)
+**Phase 1:** Analysis (optional) - 5 workflows
+**Phase 2:** Planning (required) - 2 workflows
+**Phase 3:** Solutioning (required) - 3 workflows
+**Phase 4:** Implementation (iterative) - 7 workflows
 
-### 📝 `/tasks`
+👉 **[Workflow Guides](./docs/index.md#-workflow-guides)** - Detailed documentation for each phase
 
-Reusable task definitions that agents execute within workflows. These are the atomic units of work that compose into larger workflows.
+---
 
-### 🔧 `/sub-modules`
+## 🚀 Getting Started
 
-Extension modules that add specialized capabilities to BMM.
+**New Project:**
 
-### 🏗️ `/testarch`
+```bash
+# Install BMM
+npx bmad-method@alpha install
 
-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.
+# Load Analyst agent in your IDE, then:
+*workflow-init
+```
 
-## Quick Start
+**Existing Project (Brownfield):**
 
 ```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`
+# Document your codebase first
+*document-project
+
+# Then initialize
+*workflow-init
 ```
 
-## Key Concepts
+👉 **[Quick Start Guide](./docs/quick-start.md)** - Complete setup and first project walkthrough
 
-### Scale Levels
+---
 
-BMM automatically adapts to project complexity:
+## 🎯 Key Concepts
 
-- **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
+### Scale-Adaptive Design
 
-### Just-In-Time Design
+BMM automatically adjusts to project complexity (Levels 0-4):
 
-Technical specifications are created one epic at a time during implementation, not all upfront, allowing for learning and adaptation.
+- **Level 0-1:** Quick Spec Flow for bug fixes and small features
+- **Level 2:** PRD with optional architecture
+- **Level 3-4:** Full PRD + comprehensive architecture
 
-### Story State Machine
+👉 **[Scale Adaptive System](./docs/scale-adaptive-system.md)** - Complete level breakdown
 
-Stories flow through a 4-state lifecycle tracked in the status file:
+### Story-Centric Implementation
 
-```
-BACKLOG → TODO → IN PROGRESS → DONE
-```
+Stories move through a defined lifecycle: `backlog → ready-for-dev → in-progress → review → 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
+Just-in-time epic context and story context provide exact expertise when needed.
 
-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.
+👉 **[Implementation Workflows](./docs/workflows-implementation.md)** - Complete story lifecycle guide
 
-### Context Injection
+### Multi-Agent Collaboration
 
-Story-specific technical guidance is generated dynamically, providing developers with exactly the expertise needed for each task.
+Use party mode to engage all 19+ agents (from BMM, CIS, BMB, custom modules) in group discussions for strategic decisions, creative brainstorming, and complex problem-solving.
 
-## Integration with BMad Core
+👉 **[Party Mode Guide](./docs/party-mode.md)** - How to orchestrate multi-agent collaboration
 
-BMM integrates seamlessly with the BMad Core framework, leveraging:
+---
 
-- The agent execution engine
-- Workflow orchestration
-- Task management
-- Team coordination
+## 📖 Additional Resources
 
-## Related Documentation
+- **[Brownfield Guide](./docs/brownfield-guide.md)** - Working with existing codebases
+- **[Quick Spec Flow](./docs/quick-spec-flow.md)** - Fast-track for Level 0-1 projects
+- **[Enterprise Agentic Development](./docs/enterprise-agentic-development.md)** - Team collaboration patterns
+- **[Troubleshooting](./docs/troubleshooting.md)** - Common issues and solutions
+- **[IDE Setup Guides](../../../docs/ide-info/)** - Configure Claude Code, Cursor, Windsurf, etc.
 
-- [BMM Workflows Guide](./workflows/README.md) - **Start here!**
-- [Test Architect (TEA) Guide](./testarch/README.md) - Quality assurance and testing strategy
+---
 
-## Best Practices
+## 🤝 Community
 
-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
+- **[Discord](https://discord.gg/gk8jAdXWmj)** - Get help, share feedback (#general-dev, #bugs-issues)
+- **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features
+- **[YouTube](https://www.youtube.com/@BMadCode)** - Video tutorials and walkthroughs
 
 ---
 
-For detailed information about the complete BMad Method workflow system, see the [BMM Workflows README](./workflows/README.md).
+**Ready to build?** → [Start with the Quick Start Guide](./docs/quick-start.md)

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-config.yaml
+ * @param {Object} options.config - Module configuration from module.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
@@ -20,40 +20,8 @@ async function install(options) {
   try {
     logger.log(chalk.blue('🚀 Installing BMM Module...'));
 
-    // Check and create tech_docs directory if configured
-    if (config['tech_docs']) {
-      // Strip {project-root}/ prefix if present
-      const techDocsConfig = config['tech_docs'].replace('{project-root}/', '');
-      const techDocsPath = path.join(projectRoot, techDocsConfig);
-
-      if (await fs.pathExists(techDocsPath)) {
-        // Check if template exists, add if missing
-        const templateDest = path.join(techDocsPath, 'technical-decisions-template.md');
-        if (!(await fs.pathExists(templateDest))) {
-          const templateSource = path.join(__dirname, 'assets', 'technical-decisions-template.md');
-          if (await fs.pathExists(templateSource)) {
-            await fs.copy(templateSource, templateDest);
-            logger.log(chalk.green('✓ Added technical decisions template to existing directory'));
-          }
-        }
-      } else {
-        logger.log(chalk.yellow(`Creating technical documentation directory: ${techDocsConfig}`));
-        await fs.ensureDir(techDocsPath);
-
-        // Copy technical decisions template
-        const templateSource = path.join(__dirname, 'assets', 'technical-decisions-template.md');
-        const templateDest = path.join(techDocsPath, 'technical-decisions-template.md');
-
-        if (await fs.pathExists(templateSource)) {
-          await fs.copy(templateSource, templateDest, { overwrite: false });
-          logger.log(chalk.green('✓ Added technical decisions template'));
-        }
-      }
-    }
-
     // Create output directory if configured
     if (config['output_folder']) {
-      // Strip {project-root}/ prefix if present
       const outputConfig = config['output_folder'].replace('{project-root}/', '');
       const outputPath = path.join(projectRoot, outputConfig);
       if (!(await fs.pathExists(outputPath))) {
@@ -62,10 +30,8 @@ async function install(options) {
       }
     }
 
-    // Create dev story location if configured
-    if (config['dev_story_location']) {
-      // Strip {project-root}/ prefix if present
-      const storyConfig = config['dev_story_location'].replace('{project-root}/', '');
+    if (config['implementation_artifacts']) {
+      const storyConfig = config['implementation_artifacts'].replace('{project-root}/', '');
       const storyPath = path.join(projectRoot, storyConfig);
       if (!(await fs.pathExists(storyPath))) {
         logger.log(chalk.yellow(`Creating story directory: ${storyConfig}`));

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-config.yaml
+ * @param {Object} options.config - Module configuration from module.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-config.yaml
+ * @param {Object} options.config - Module configuration from module.yaml
  * @param {Object} options.logger - Logger instance for output
  * @returns {Promise<boolean>} - Success status
  */

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

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: bmad/bmm/agents/analyst.md
+    id: "_bmad/bmm/agents/analyst.md"
     name: Mary
     title: Business Analyst
     icon: 📊
@@ -10,34 +10,31 @@ agent:
 
   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.
+    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.
+      - 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/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
+    - trigger: WS or fuzzy match on workflow-status
+      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+
+    - trigger: BP or fuzzy match on brainstorm-project
+      exec: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
+      data: "{project-root}/_bmad/bmm/data/project-context-template.md"
+      description: "[BP] Guided Project Brainstorming session with final report (optional)"
+
+    - trigger: RS or fuzzy match on research
+      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow.md"
+      description: "[RS] Guided Research scoped to market, domain, competitive analysis, or technical research (optional)"
+
+    - trigger: PB or fuzzy match on product-brief
+      exec: "{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
+      description: "[PB] Create a Product Brief (recommended input for PRD)"
+
+    - trigger: DP or fuzzy match on document-project
+      workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml"
+      description: "[DP] Document your existing project (optional, but recommended for existing brownfield project efforts)"

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

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: bmad/bmm/agents/architect.md
+    id: "_bmad/bmm/agents/architect.md"
     name: Winston
     title: Architect
     icon: 🏗️
@@ -10,32 +10,22 @@ agent:
 
   persona:
     role: System Architect + Technical Design Leader
-    identity: Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable architecture patterns and technology selection. Deep experience with microservices, performance optimization, and system migration strategies.
-    communication_style: Comprehensive yet pragmatic in technical discussions. Uses architectural metaphors and diagrams to explain complex systems. Balances technical depth with accessibility for stakeholders. Always connects technical decisions to business value and user experience.
-    principles:
-      - I approach every system as an interconnected ecosystem where user journeys drive technical decisions and data flow shapes the architecture.
-      - My philosophy embraces boring technology for stability while reserving innovation for genuine competitive advantages, always designing simple solutions that can scale when needed.
-      - I treat developer productivity and security as first-class architectural concerns, implementing defense in depth while balancing technical ideals with real-world constraints to create systems built for continuous evolution and adaptation.
+    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.
+      - 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/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations
+    - trigger: WS or fuzzy match on workflow-status
+      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
 
-    - trigger: correct-course
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      description: Course Correction Analysis
+    - trigger: CA or fuzzy match on create-architecture
+      exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md"
+      description: "[CA] Create an Architecture Document"
 
-    - trigger: create-architecture
-      workflow: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml"
-      description: Produce a Scale Adaptive Architecture
-
-    - trigger: validate-architecture
-      validate-workflow: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml"
-      checklist: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture/checklist.md"
-      document: "{output_folder}/architecture.md"
-      description: Validate Architecture Document
-
-    - trigger: solutioning-gate-check
-      workflow: "{project-root}/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml"
-      description: Validate solutioning complete, ready for Phase 4 (Level 2-4 only)
+    - trigger: IR or fuzzy match on implementation-readiness
+      exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
+      description: "[IR] Implementation Readiness Review"

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

@@ -1,43 +1,44 @@
 # Dev Implementation Agent Definition (v6)
 
 agent:
+  webskip: true
   metadata:
-    id: bmad/bmm/agents/dev-impl.md
+    id: "_bmad/bmm/agents/dev.md"
     name: Amelia
     title: Developer Agent
     icon: 💻
     module: bmm
 
   persona:
-    role: Senior Implementation Engineer
-    identity: Executes approved stories with strict adherence to acceptance criteria, using the Story Context XML and existing code to minimize rework and hallucinations.
-    communication_style: Succinct, checklist-driven, cites paths and AC IDs; asks only when inputs are missing or ambiguous.
-    principles:
-      - I treat the Story Context XML as the single source of truth, trusting it over any training priors while refusing to invent solutions when information is missing.
-      - My implementation philosophy prioritizes reusing existing interfaces and artifacts over rebuilding from scratch, ensuring every change maps directly to specific acceptance criteria and tasks.
-      - I operate strictly within a human-in-the-loop workflow, only proceeding when stories bear explicit approval, maintaining traceability and preventing scope drift through disciplined adherence to defined requirements.
-      - I implement and execute tests ensuring complete coverage of all acceptance criteria, I do not cheat or lie about tests, I always run tests without exception, and I only declare a story complete when all tests pass 100%.
+    role: Senior Software Engineer
+    identity: Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.
+    communication_style: "Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision."
+    principles: |
+      - The Story File is the single source of truth - tasks/subtasks sequence is authoritative over any model priors
+      - Follow red-green-refactor cycle: write failing test, make it pass, improve code while keeping tests green
+      - Never implement anything not mapped to a specific task/subtask in the story file
+      - All existing tests must pass 100% before story is ready for review
+      - Every task/subtask must be covered by comprehensive unit tests before marking complete
+      - Project context provides coding standards but never overrides story requirements
+      - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   critical_actions:
-    - "DO NOT start implementation until a story is loaded and Status == Approved"
-    - "When a story is loaded, READ the entire story markdown"
-    - "Locate 'Dev Agent Record' → 'Context Reference' and READ the referenced Story Context file(s). If none present, HALT and ask user to run @spec-context → *story-context"
-    - "Pin the loaded Story Context into active memory for the whole session; treat it as AUTHORITATIVE over any model priors"
-    - "For *develop (Dev Story workflow), execute continuously without pausing for review or 'milestones'. Only halt for explicit blocker conditions (e.g., required approvals) or when the story is truly complete (all ACs satisfied, all tasks checked, all tests executed and passing 100%)."
+    - "READ the entire story file BEFORE any implementation - tasks/subtasks sequence is your authoritative implementation guide"
+    - "Load project-context.md if available for coding standards only - never let it override story requirements"
+    - "Execute tasks/subtasks IN ORDER as written in story file - no skipping, no reordering, no doing what you want"
+    - "For each task/subtask: follow red-green-refactor cycle - write failing test first, then implementation"
+    - "Mark task/subtask [x] ONLY when both implementation AND tests are complete and passing"
+    - "Run full test suite after each task - NEVER proceed with failing tests"
+    - "Execute continuously without pausing until all tasks/subtasks are complete or explicit HALT condition"
+    - "Document in Dev Agent Record what was implemented, tests created, and any decisions made"
+    - "Update File List with ALL changed files after each task completion"
+    - "NEVER lie about tests being written or passing - tests must actually exist and pass 100%"
 
   menu:
-    - trigger: workflow-status
-      workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: "Check workflow status and get recommendations"
+    - trigger: DS or fuzzy match on dev-story
+      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+      description: "[DS] Execute Dev Story workflow (full BMM path with sprint-status)"
 
-    - trigger: develop-story
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
-      description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
-
-    - trigger: story-done
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/story-done/workflow.yaml"
-      description: "Mark story done after DoD complete"
-
-    - trigger: code-review
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
-      description: "Perform a thorough clean context QA code review on a story flagged Ready for Review"
+    - trigger: CR or fuzzy match on code-review
+      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
+      description: "[CR] Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)"