bmad-method 6.0.0-alpha.9 → 6.0.2

package/src/modules/bmgd/workflows/4-production/story-context/workflow.yaml

@@ -1,57 +0,0 @@
-# Story Context Creation Workflow
-name: story-context
-description: "Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story"
-author: "BMad"
-
-# Critical variables
-config_source: "{project-root}/{bmad_folder}/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"
-story_path: "{config_source}:sprint_artifacts/stories"
-date: system-generated
-sprint_artifacts: "{config_source}:sprint_artifacts"
-sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
-
-# Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context"
-template: "{installed_path}/context-template.xml"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Smart input file references - handles both whole docs and sharded docs
-# Priority: Whole document first, then sharded version
-# Strategy: SELECTIVE LOAD - only load the specific epic needed for this story
-input_file_patterns:
-  prd:
-    whole: "{output_folder}/*prd*.md"
-    sharded: "{output_folder}/*prd*/*.md"
-    load_strategy: "FULL_LOAD"
-  tech_spec:
-    whole: "{output_folder}/tech-spec.md"
-    load_strategy: "FULL_LOAD"
-  architecture:
-    whole: "{output_folder}/*architecture*.md"
-    sharded: "{output_folder}/*architecture*/*.md"
-    load_strategy: "FULL_LOAD"
-  ux_design:
-    whole: "{output_folder}/*ux*.md"
-    sharded: "{output_folder}/*ux*/*.md"
-    load_strategy: "FULL_LOAD"
-  epics:
-    whole: "{output_folder}/*epic*.md"
-    sharded_index: "{output_folder}/*epic*/index.md"
-    sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
-    load_strategy: "SELECTIVE_LOAD"
-  document_project:
-    sharded: "{output_folder}/docs/index.md"
-    load_strategy: "INDEX_GUIDED"
-
-# Output configuration
-# Uses story_key from sprint-status.yaml (e.g., "1-2-user-authentication")
-default_output_file: "{story_path}/{{story_key}}.context.xml"
-
-standalone: true
-
-web_bundle: false

package/src/modules/bmgd/workflows/4-production/story-done/instructions.md

@@ -1,111 +0,0 @@
-# Story Approved Workflow Instructions (DEV Agent)
-
-<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>Communicate all responses in {communication_language}</critical>
-
-<workflow>
-
-<critical>This workflow is run by DEV agent AFTER user confirms a story is approved (Definition of Done is complete)</critical>
-<critical>Workflow: Update story file status to Done</critical>
-
-<step n="1" goal="Find reviewed story to mark done" tag="sprint-status">
-
-<check if="{story_path} is provided">
-  <action>Use {story_path} directly</action>
-  <action>Read COMPLETE story file and parse sections</action>
-  <action>Extract story_key from filename or story metadata</action>
-  <action>Verify Status is "review" - if not, HALT with message: "Story status must be 'review' to mark as done"</action>
-</check>
-
-<check if="{story_path} is NOT provided">
-  <critical>MUST read COMPLETE sprint-status.yaml file from start to end to preserve order</critical>
-  <action>Load the FULL file: {output_folder}/sprint-status.yaml</action>
-  <action>Read ALL lines from beginning to end - do not skip any content</action>
-  <action>Parse the development_status section completely</action>
-
-<action>Find FIRST story (reading in order from top to bottom) where: - Key matches pattern: number-number-name (e.g., "1-2-user-auth") - NOT an epic key (epic-X) or retrospective (epic-X-retrospective) - Status value equals "review"
-</action>
-
-  <check if="no story with status 'review' found">
-    <output>📋 No stories with status "review" found
-
-All stories are either still in development or already done.
-
-**Next Steps:**
-
-1. Run `dev-story` to implement stories
-2. Run `code-review` if stories need review first
-3. Check sprint-status.yaml for current story states
-   </output>
-   <action>HALT</action>
-   </check>
-
-<action>Use the first reviewed story found</action>
-<action>Find matching story file in {story_dir} using story_key pattern</action>
-<action>Read the COMPLETE story file</action>
-</check>
-
-<action>Extract story_id and story_title from the story file</action>
-
-<action>Find the "Status:" line (usually at the top)</action>
-<action>Update story file: Change Status to "done"</action>
-
-<action>Add completion notes to Dev Agent Record section:</action>
-<action>Find "## Dev Agent Record" section and add:
-
-```
-### Completion Notes
-**Completed:** {date}
-**Definition of Done:** All acceptance criteria met, code reviewed, tests passing
-```
-
-</action>
-
-<action>Save the story file</action>
-</step>
-
-<step n="2" goal="Update sprint status to done" tag="sprint-status">
-<action>Load the FULL file: {output_folder}/sprint-status.yaml</action>
-<action>Find development_status key matching {story_key}</action>
-<action>Verify current status is "review" (expected previous state)</action>
-<action>Update development_status[{story_key}] = "done"</action>
-<action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-<check if="story key not found in file">
-  <output>⚠️ Story file updated, but could not update sprint-status: {story_key} not found
-
-Story is marked Done in file, but sprint-status.yaml may be out of sync.
-</output>
-</check>
-
-</step>
-
-<step n="3" goal="Confirm completion to user">
-
-<output>**Story Approved and Marked Done, {user_name}!**
-
-✅ Story file updated → Status: done
-✅ Sprint status updated: review → done
-
-**Completed Story:**
-
-- **ID:** {story_id}
-- **Key:** {story_key}
-- **Title:** {story_title}
-- **Completed:** {date}
-
-**Next Steps:**
-
-1. Continue with next story in your backlog
-   - Run `create-story` for next backlog story
-   - Or run `dev-story` if ready stories exist
-2. Check epic completion status
-   - Run `retrospective` workflow to check if epic is complete
-   - Epic retrospective will verify all stories are done
-     </output>
-
-</step>
-
-</workflow>
-```

package/src/modules/bmgd/workflows/4-production/story-done/workflow.yaml

@@ -1,28 +0,0 @@
-# Story Done Workflow (DEV Agent)
-name: story-done
-description: "Marks a story as done (DoD complete) and moves it from its current status → DONE in the status file. Advances the story queue. Simple status-update workflow with no searching required."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-date: system-generated
-sprint_artifacts: "{config_source}:sprint_artifacts"
-sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
-
-# Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done"
-instructions: "{installed_path}/instructions.md"
-
-# Variables and inputs
-variables:
-  story_dir: "{config_source}:sprint_artifacts" # Directory where stories are stored
-
-# Output configuration - no output file, just status updates
-default_output_file: ""
-
-standalone: true
-
-web_bundle: false

package/src/modules/bmgd/workflows/4-production/story-ready/instructions.md

@@ -1,117 +0,0 @@
-# Story Ready Workflow Instructions (SM Agent)
-
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-
-<workflow>
-
-<critical>This workflow is run by SM agent AFTER user reviews a drafted story and confirms it's ready for development</critical>
-<critical>Simple workflow: Update story file status to Ready</critical>
-
-<step n="1" goal="Find drafted story to mark ready" tag="sprint-status">
-
-<action>If {{story_path}} is provided → use it directly; extract story_key from filename or metadata; GOTO mark_ready</action>
-
-<critical>MUST read COMPLETE {sprint_status} file from start to end to preserve order</critical>
-<action>Load the FULL file: {sprint_status}</action>
-<action>Read ALL lines from beginning to end - do not skip any content</action>
-<action>Parse the development_status section completely</action>
-
-<action>Find ALL stories (reading in order from start to end) where:
-
-- Key matches pattern: number-number-name (e.g., "1-2-user-auth")
-- NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
-- Status value equals "drafted"
-  </action>
-
-<action>Collect up to 10 drafted story keys in order (limit for display purposes)</action>
-<action>Count total drafted stories found</action>
-
-<check if="no drafted stories found">
-  <output>📋 No drafted stories found in {sprint_status}
-
-All stories are either still in backlog or already marked ready/in-progress/done.
-
-**Options:**
-
-1. Run `create-story` to draft more stories
-2. Run `sprint-planning` to refresh story tracking
-   </output>
-   <action>HALT</action>
-   </check>
-
-<action>Display available drafted stories:
-
-**Drafted Stories Available ({{drafted_count}} found):**
-
-{{list_of_drafted_story_keys}}
-
-</action>
-
-<ask if="{{non_interactive}} == false">Select the drafted story to mark as Ready (enter story key or number):</ask>
-<action if="{{non_interactive}} == true">Auto-select first story from the list</action>
-
-<action>Resolve selected story_key from user input or auto-selection</action>
-<action>Find matching story file in {{story_dir}} using story_key pattern</action>
-
-<anchor id="mark_ready" />
-
-<action>Read the story file from resolved path</action>
-<action>Extract story_id and story_title from the file</action>
-
-<action>Find the "Status:" line (usually at the top)</action>
-<action>Update story file: Change Status to "ready-for-dev"</action>
-<action>Save the story file</action>
-</step>
-
-<step n="2" goal="Update sprint status to ready-for-dev" tag="sprint-status">
-<action>Load the FULL file: {sprint_status}</action>
-<action>Find development_status key matching {{story_key}}</action>
-<action>Verify current status is "drafted" (expected previous state)</action>
-<action>Update development_status[{{story_key}}] = "ready-for-dev"</action>
-<action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-<check if="story key not found in file">
-  <output>⚠️ Story file updated, but could not update sprint-status: {{story_key}} not found
-
-You may need to run sprint-planning to refresh tracking.
-</output>
-</check>
-
-</step>
-
-<step n="3" goal="Confirm completion to user">
-
-<output>**Story Marked Ready for Development, {user_name}!**
-
-✅ Story file updated: `{{story_file}}` → Status: ready-for-dev
-✅ Sprint status updated: drafted → ready-for-dev
-
-**Story Details:**
-
-- **ID:** {{story_id}}
-- **Key:** {{story_key}}
-- **Title:** {{story_title}}
-- **File:** `{{story_file}}`
-- **Status:** ready-for-dev
-
-**Next Steps:**
-
-1. **Recommended:** Run `story-context` workflow to generate implementation context
-   - This creates a comprehensive context XML for the DEV agent
-   - Includes relevant architecture, dependencies, and existing code
-
-2. **Alternative:** Skip context generation and go directly to `dev-story` workflow
-   - Faster, but DEV agent will have less context
-   - Only recommended for simple, well-understood stories
-
-**To proceed:**
-
-- For context generation: Stay with SM agent and run `story-context` workflow
-- For direct implementation: Load DEV agent and run `dev-story` workflow
-
-</step>
-
-</workflow>

package/src/modules/bmgd/workflows/4-production/story-ready/workflow.yaml

@@ -1,25 +0,0 @@
-# Story Ready Workflow (SM Agent)
-name: story-ready
-description: "Marks a drafted story as ready for development and moves it from TODO → IN PROGRESS in the status file. Simple status-update workflow with no searching required."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-date: system-generated
-sprint_artifacts: "{config_source}:sprint_artifacts"
-sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
-
-# Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready"
-instructions: "{installed_path}/instructions.md"
-
-# Variables and inputs
-variables:
-  story_dir: "{config_source}:sprint_artifacts"
-
-standalone: true
-
-web_bundle: false

package/src/modules/bmm/README.md

@@ -1,128 +0,0 @@
-# BMM - BMad Method Module
-
-Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
-
----
-
-## 📚 Complete Documentation
-
-👉 **[BMM Documentation Hub](./docs/README.md)** - Start here for complete guides, tutorials, and references
-
-**Quick Links:**
-
-- **[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
-
----
-
-## 🏗️ Module Structure
-
-This module contains:
-
-```
-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
-```
-
-### Agent Roster
-
-**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)
-
-👉 **[Full Agents Guide](./docs/agents-guide.md)** - Roles, workflows, and when to use each agent
-
-### Workflow Phases
-
-**Phase 0:** Documentation (brownfield only)
-**Phase 1:** Analysis (optional) - 5 workflows
-**Phase 2:** Planning (required) - 6 workflows
-**Phase 3:** Solutioning (Level 3-4) - 2 workflows
-**Phase 4:** Implementation (iterative) - 10 workflows
-**Testing:** Quality assurance (parallel) - 9 workflows
-
-👉 **[Workflow Guides](./docs/README.md#-workflow-guides)** - Detailed documentation for each phase
-
----
-
-## 🚀 Getting Started
-
-**New Project:**
-
-```bash
-# Install BMM
-npx bmad-method@alpha install
-
-# Load Analyst agent in your IDE, then:
-*workflow-init
-```
-
-**Existing Project (Brownfield):**
-
-```bash
-# Document your codebase first
-*document-project
-
-# Then initialize
-*workflow-init
-```
-
-👉 **[Quick Start Guide](./docs/quick-start.md)** - Complete setup and first project walkthrough
-
----
-
-## 🎯 Key Concepts
-
-### Scale-Adaptive Design
-
-BMM automatically adjusts to project complexity (Levels 0-4):
-
-- **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
-
-👉 **[Scale Adaptive System](./docs/scale-adaptive-system.md)** - Complete level breakdown
-
-### Story-Centric Implementation
-
-Stories move through a defined lifecycle: `backlog → drafted → ready → in-progress → review → done`
-
-Just-in-time epic context and story context provide exact expertise when needed.
-
-👉 **[Implementation Workflows](./docs/workflows-implementation.md)** - Complete story lifecycle guide
-
-### Multi-Agent Collaboration
-
-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.
-
-👉 **[Party Mode Guide](./docs/party-mode.md)** - How to orchestrate multi-agent collaboration
-
----
-
-## 📖 Additional Resources
-
-- **[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.
-
----
-
-## 🤝 Community
-
-- **[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
-
----
-
-**Ready to build?** → [Start with the Quick Start Guide](./docs/quick-start.md)

package/src/modules/bmm/_module-installer/assets/bmm-kb.md

@@ -1 +0,0 @@
-# BMad Method Master Knowledge Base Index

package/src/modules/bmm/_module-installer/assets/technical-decisions.md

@@ -1,30 +0,0 @@
-# Technical Decisions Log
-
-_Auto-updated during discovery and planning sessions - you can also add information here yourself_
-
-## Purpose
-
-This document captures technical decisions, preferences, and constraints discovered during project discussions. It serves as input for architecture.md and solution design documents.
-
-## Confirmed Decisions
-
-<!-- Technical choices explicitly confirmed by the team/user -->
-
-## Preferences
-
-<!-- Non-binding preferences mentioned during discussions -->
-
-## Constraints
-
-<!-- Hard requirements from infrastructure, compliance, or integration needs -->
-
-## To Investigate
-
-<!-- Technical questions that need research or architect input -->
-
-## Notes
-
-- This file is automatically updated when technical information is mentioned
-- Decisions here are inputs, not final architecture
-- Final technical decisions belong in architecture.md
-- Implementation details belong in solutions/\*.md and story context or dev notes.

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

@@ -1,60 +0,0 @@
-# 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
-
-header: "BMad Method™: Breakthrough Method of Agile-Ai Driven-Dev"
-subheader: "Agent and Workflow Configuration for this module"
-
-# Variables from Core Config inserted:
-## user_name
-## communication_language
-## output_folder
-## bmad_folder
-## install_user_docs
-## kb_install
-
-project_name:
-  prompt: "What is the title of your project you will be working on?"
-  default: "{directory_name}"
-  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"
-
-sprint_artifacts:
-  prompt: "Where should Sprint Artifacts be stored (sprint status, stories, story context, temp context, etc...)?"
-  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)?"
-  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"