bmad-method 6.0.0-alpha.19 → 6.0.0-alpha.20

package/src/modules/bmm/docs/bmad-quick-flow.md

@@ -8,15 +8,16 @@
 
 ## Overview
 
-BMAD Quick Flow is the fastest path from idea to production in the BMAD Method ecosystem. It's a streamlined 3-step process designed for rapid development without sacrificing quality. Perfect for experienced teams who need to move fast or for smaller features that don't require extensive planning.
+BMAD Quick Flow is the fastest path from idea to production in the BMAD Method ecosystem. It's a streamlined 3-step process designed for rapid spec driven development without sacrificing quality. Perfect for experienced teams who need to move fast or for smaller features or 1 off efforts that don't require extensive planning.
 
 ### When to Use Quick Flow
 
 **Perfect For:**
 
 - Bug fixes and patches
-- Small feature additions (1-3 days of work)
+- Small feature additions
 - Proof of concepts and prototypes
+- Mid course corrections or additions of something missed in BMM full planning
 - Performance optimizations
 - API endpoint additions
 - UI component enhancements
@@ -31,42 +32,19 @@ BMAD Quick Flow is the fastest path from idea to production in the BMAD Method e
 - Projects requiring extensive UX design
 - Enterprise-wide initiatives
 - Mission-critical systems with compliance requirements
+- Ideas with many 'moving pieces'
 
 ---
 
 ## The Quick Flow Process
 
-```mermaid
-flowchart TD
-    START[Idea/Requirement] --> DECIDE{Planning Needed?}
-
-    DECIDE -->|Yes| CREATE[create-tech-spec]
-    DECIDE -->|No| DIRECT[Direct Development]
-
-    CREATE --> SPEC[Technical Specification]
-    SPEC --> DEV[quick-dev]
-    DIRECT --> DEV
-
-    DEV --> COMPLETE{Implementation Complete}
+Utilizing the Quick Flow Solo Dev, this one agent can do it all!
 
-    COMPLETE -->|Success| REVIEW{Code Review?}
-    COMPLETE -->|Issues| DEBUG[Debug & Fix]
-    DEBUG --> DEV
+1. Create an (option) Technical Specification
+2. Develop with Tests
+3. AI Driven Code Review
 
-    REVIEW -->|Yes| CODE_REVIEW[code-review]
-    REVIEW -->|No| DONE[Production Ready]
-
-    CODE_REVIEW --> FIXES{Fixes Needed?}
-    FIXES -->|Yes| DEBUG
-    FIXES -->|No| DONE
-
-    style START fill:#e1f5fe
-    style CREATE fill:#f3e5f5
-    style SPEC fill:#e8f5e9
-    style DEV fill:#fff3e0
-    style CODE_REVIEW fill:#f1f8e9
-    style DONE fill:#e0f2f1
-```
+That's it! Lets look at each step in more detail though.
 
 ### Step 1: Optional Technical Specification
 
@@ -103,7 +81,7 @@ The `create-tech-spec` workflow transforms requirements into implementation-read
    - Make adjustments as needed
    - Save to sprint artifacts
 
-**Output:** `{sprint_artifacts}/tech-spec-{slug}.md`
+**Output:** `{implementation_artifacts}/tech-spec-{slug}.md`
 
 ### Step 2: Development
 

package/src/modules/bmm/docs/brownfield-guide.md

@@ -726,7 +726,7 @@ flowchart TD
 - **[Glossary](./glossary.md)** - Key terminology
 - **[FAQ](./faq.md)** - Common questions
 - **[Troubleshooting](./troubleshooting.md)** - Problem resolution
-- **[Workflow Documentation](./README.md#-workflow-guides)** - Complete workflow reference
+- **[Workflow Documentation](./index.md#-workflow-guides)** - Complete workflow reference
 
 ---
 

package/src/modules/bmm/docs/enterprise-agentic-development.md

@@ -678,7 +678,7 @@ PMs write BMad PRDs → Stories auto-fed to cloud AI agents → Parallel impleme
 - [FAQ](./faq.md) - Common questions
 - [Scale Adaptive System](./scale-adaptive-system.md) - Project levels explained
 - [Quick Start Guide](./quick-start.md) - Getting started
-- [Workflow Documentation](./README.md#-workflow-guides) - Complete workflow reference
+- [Workflow Documentation](./index.md#-workflow-guides) - Complete workflow reference
 - [Agents Guide](./agents-guide.md) - Understanding BMad agents
 
 ---

package/src/modules/bmm/docs/{README.md → index.md}

@@ -8,7 +8,7 @@ Complete guides for the BMad Method Module (BMM) - AI-powered agile development
 
 **New to BMM?** Start here:
 
-- **[Quick Start Guide](./quick-start.md)** - Step-by-step guide to building your first project (15 min read)
+- **[Quick Start Guide](./quick-start.md)** - Step-by-step guide to building your first project
   - Installation and setup
   - Understanding the four phases
   - Running your first workflows
@@ -20,44 +20,40 @@ Complete guides for the BMad Method Module (BMM) - AI-powered agile development
 
 **[Complete Workflow Diagram](./images/workflow-method-greenfield.svg)** - Visual flowchart showing all phases, agents (color-coded), and decision points for the BMad Method standard greenfield track.
 
----
-
 ## 📖 Core Concepts
 
 Understanding how BMM adapts to your needs:
 
-- **[Scale Adaptive System](./scale-adaptive-system.md)** - How BMM adapts to project size and complexity (42 min read)
+- **[Scale Adaptive System](./scale-adaptive-system.md)** - How BMM adapts to project size and complexity
   - Three planning tracks (Quick Flow, BMad Method, Enterprise Method)
   - Automatic track recommendation
   - Documentation requirements per track
   - Planning workflow routing
 
-- **[BMAD Quick Flow](./bmad-quick-flow.md)** - Fast-track development workflow (32 min read)
+- **[BMAD Quick Flow](./bmad-quick-flow.md)** - Fast-track development workflow
   - 3-step process: spec → dev → optional review
   - Perfect for bug fixes and small features
   - Rapid prototyping with production quality
   - Hours to implementation, not days
   - Barry (Quick Flow Solo Dev) agent owned
 
-- **[Quick Flow Solo Dev Agent](./quick-flow-solo-dev.md)** - Elite solo developer for rapid development (18 min read)
+- **[Quick Flow Solo Dev Agent](./quick-flow-solo-dev.md)** - Elite solo developer for rapid development
   - Barry is an elite developer who thrives on autonomous execution
   - Lives and breathes the BMAD Quick Flow workflow
   - Takes projects from concept to deployment with ruthless efficiency
   - No handoffs, no delays - just pure focused development
 
----
-
 ## 🤖 Agents and Collaboration
 
 Complete guide to BMM's AI agent team:
 
-- **[Agents Guide](./agents-guide.md)** - Comprehensive agent reference (45 min read)
+- **[Agents Guide](./agents-guide.md)** - Comprehensive agent reference
   - 12 specialized BMM agents + BMad Master
   - Agent roles, workflows, and when to use them
   - Agent customization system
   - Best practices and common patterns
 
-- **[Party Mode Guide](./party-mode.md)** - Multi-agent collaboration (20 min read)
+- **[Party Mode Guide](./party-mode.md)** - Multi-agent collaboration
   - How party mode works (19+ agents collaborate in real-time)
   - When to use it (strategic, creative, cross-functional, complex)
   - Example party compositions
@@ -65,21 +61,17 @@ Complete guide to BMM's AI agent team:
   - Agent customization in party mode
   - Best practices
 
----
-
 ## 🔧 Working with Existing Code
 
 Comprehensive guide for brownfield development:
 
-- **[Brownfield Development Guide](./brownfield-guide.md)** - Complete guide for existing codebases (53 min read)
+- **[Brownfield Development Guide](./brownfield-guide.md)** - Complete guide for existing codebases
   - Documentation phase strategies
   - Track selection for brownfield
   - Integration with existing patterns
   - Phase-by-phase workflow guidance
   - Common scenarios
 
----
-
 ## 📚 Quick References
 
 Essential reference materials:
@@ -88,8 +80,6 @@ Essential reference materials:
 - **[FAQ](./faq.md)** - Frequently asked questions across all topics
 - **[Enterprise Agentic Development](./enterprise-agentic-development.md)** - Team collaboration strategies
 
----
-
 ## 🎯 Choose Your Path
 
 ### I need to...
@@ -109,11 +99,6 @@ Essential reference materials:
 **Understand planning tracks and methodology**
 → See [Scale Adaptive System](./scale-adaptive-system.md)
 
-**Find specific commands or answers**
-→ Check [FAQ](./faq.md)
-
----
-
 ## 📋 Workflow Guides
 
 Comprehensive documentation for all BMM workflows organized by phase:
@@ -162,18 +147,6 @@ For detailed technical documentation on specific complex workflows:
   - Implementation patterns for agent consistency
   - Adaptive facilitation approach
 
----
-
-## 🧪 Testing and Quality
-
-Quality assurance guidance:
-
-<!-- Test Architect documentation to be added -->
-
-- Test design workflows
-- Quality gates
-- Risk assessment
-
 ## 🏗️ Module Structure
 
 Understanding BMM components:
@@ -184,8 +157,6 @@ Understanding BMM components:
   - Teams and collaboration
   - Best practices
 
----
-
 ## 🌐 External Resources
 
 ### Community and Support
@@ -194,56 +165,4 @@ Understanding BMM components:
 - **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features
 - **[YouTube Channel](https://www.youtube.com/@BMadCode)** - Video tutorials and walkthroughs
 
-### Additional Documentation
-
-- **[IDE Setup Guides](../../../docs/ide-info/)** - Configure your development environment
-  - Claude Code
-  - Cursor
-  - Windsurf
-  - VS Code
-  - Other IDEs
-
----
-
-## 📊 Documentation Map
-
-```mermaid
-flowchart TD
-    START[New to BMM?]
-    START --> QS[Quick Start Guide]
-
-    QS --> DECIDE{What are you building?}
-
-    DECIDE -->|Bug fix or<br/>small feature| QF[BMAD Quick Flow]
-    DECIDE -->|Need rapid<br/>development| PE[Principal Engineer]
-    DECIDE -->|New project| SAS[Scale Adaptive System]
-    DECIDE -->|Existing codebase| BF[Brownfield Guide]
-
-    QF --> IMPL[Implementation]
-    PE --> IMPL
-    SAS --> IMPL
-    BF --> IMPL
-
-    IMPL --> REF[Quick References<br/>Glossary, FAQ]
-
-    style START fill:#bfb,stroke:#333,stroke-width:2px,color:#000
-    style QS fill:#bbf,stroke:#333,stroke-width:2px,color:#000
-    style DECIDE fill:#ffb,stroke:#333,stroke-width:2px,color:#000
-    style QF fill:#e1f5fe,stroke:#333,stroke-width:2px,color:#000
-    style PE fill:#fff3e0,stroke:#333,stroke-width:2px,color:#000
-    style IMPL fill:#f9f,stroke:#333,stroke-width:2px,color:#000
-```
-
----
-
-## 💡 Tips for Using This Documentation
-
-1. **Start with Quick Start** if you're new - it provides the essential foundation
-2. **Use the FAQ** to find quick answers without reading entire guides
-3. **Bookmark Glossary** for terminology references while reading other docs
-4. **Follow the suggested paths** above based on your specific situation
-5. **Join Discord** for interactive help and community insights
-
----
-
 **Ready to begin?** → [Start with the Quick Start Guide](./quick-start.md)

package/src/modules/bmm/docs/quick-spec-flow.md

@@ -629,7 +629,7 @@ Quick Spec Flow is your **fast path from idea to implementation** for:
 ## Next Steps
 
 - **Try it now:** Load PM agent and describe a small change
-- **Learn more:** See the [BMM Workflow Guides](./README.md#-workflow-guides) for comprehensive workflow documentation
+- **Learn more:** See the [BMM Workflow Guides](./index.md#-workflow-guides) for comprehensive workflow documentation
 - **Need help deciding?** Run `workflow-init` to get a recommendation
 - **Have questions?** Join us on Discord: <https://discord.gg/gk8jAdXWmj>
 

package/src/modules/bmm/docs/quick-start.md

@@ -6,12 +6,12 @@ Get started with BMad Method v6 for your new greenfield project. This guide walk
 
 1. **Install**: `npx bmad-method@alpha install`
 2. **Initialize**: Load Analyst agent → Run "workflow-init"
-3. **Plan**: Load PM agent → Run "prd" (or "tech-spec" for small projects)
-4. **Architect**: Load Architect agent → Run "create-architecture" (10+ stories only)
-5. **Build**: Load SM agent → Run workflows for each story → Load DEV agent → Implement
-6. **Always use fresh chats** for each workflow to avoid hallucinations
-
----
+3. **Plan**: Load PM agent to create a PRD
+4. **Plan UX**: Load UX Expert to create a UX-Design if your application will have a UX/UI element
+5. **Architect**: Load Architect agent → Run "create-architecture"
+6. **Epic Plan**: The PM steps back in to help run the create-epics-and-stories
+7. **Build**: Load SM agent → Run workflows for each story → Load DEV agent → Implement
+8. **Always use fresh chats** for each workflow to avoid context issues
 
 ## What is BMad Method?
 
@@ -350,7 +350,7 @@ A: Yes, once you learn the flow. Use the Quick Reference in Step 2 to go directl
 
 - **During workflows**: Agents guide you with questions and explanations
 - **Community**: [Discord](https://discord.gg/gk8jAdXWmj) - #general-dev, #bugs-issues
-- **Complete guide**: [BMM Workflow Documentation](./README.md#-workflow-guides)
+- **Complete guide**: [BMM Workflow Documentation](./index.md#-workflow-guides)
 - **YouTube tutorials**: [BMad Code Channel](https://www.youtube.com/@BMadCode)
 
 ---

package/src/modules/bmm/docs/scale-adaptive-system.md

@@ -611,7 +611,7 @@ Run `workflow-init` on existing projects to migrate to new tracking system. It d
 - **[Brownfield Guide](./brownfield-guide.md)** - Existing codebase workflows
 - **[Glossary](./glossary.md)** - Complete terminology
 - **[FAQ](./faq.md)** - Common questions
-- **[Workflows Guide](./README.md#-workflow-guides)** - Complete workflow reference
+- **[Workflows Guide](./index.md#-workflow-guides)** - Complete workflow reference
 
 ---
 

package/src/modules/bmm/docs/test-architecture.md

@@ -228,6 +228,9 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
 - Use `*atdd` before coding when the team can adopt ATDD; share its checklist with the dev agent.
 - Post-implementation, keep `*trace` current, expand coverage with `*automate`, optionally review test quality with `*test-review`. For release gate, run `*trace` with Phase 2 enabled to get deployment decision.
 - Use `*test-review` after `*atdd` to validate generated tests, after `*automate` to ensure regression quality, or before gate for final audit.
+- Clarification: `*test-review` is optional and only audits existing tests; run it after `*atdd` or `*automate` when you want a quality review, not as a required step.
+- Clarification: `*atdd` outputs are not auto-consumed; share the ATDD doc/tests with the dev workflow. `*trace` does not run `*atdd`—it evaluates existing artifacts for coverage and gate readiness.
+- Clarification: `*ci` is a one-time setup; recommended early (Phase 3 or before feature work), but it can be done later if it was skipped.
 
 </details>
 
@@ -440,15 +443,13 @@ Provides fixture-based utilities that integrate into TEA's test generation and r
 
 <br></br>
 
-| Command        | Workflow README                                   | Primary Outputs                                                                               | Notes                                                | With Playwright MCP Enhancements                                                                             |
-| -------------- | ------------------------------------------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
-| `*framework`   | [📖](../workflows/testarch/framework/README.md)   | Playwright/Cypress scaffold, `.env.example`, `.nvmrc`, sample specs                           | Use when no production-ready harness exists          | -                                                                                                            |
-| `*ci`          | [📖](../workflows/testarch/ci/README.md)          | CI workflow, selective test scripts, secrets checklist                                        | Platform-aware (GitHub Actions default)              | -                                                                                                            |
-| `*test-design` | [📖](../workflows/testarch/test-design/README.md) | Combined risk assessment, mitigation plan, and coverage strategy                              | Risk scoring + optional exploratory mode             | **+ Exploratory**: Interactive UI discovery with browser automation (uncover actual functionality)           |
-| `*atdd`        | [📖](../workflows/testarch/atdd/README.md)        | Failing acceptance tests + implementation checklist                                           | TDD red phase + optional recording mode              | **+ Recording**: AI generation verified with live browser (accurate selectors from real DOM)                 |
-| `*automate`    | [📖](../workflows/testarch/automate/README.md)    | Prioritized specs, fixtures, README/script updates, DoD summary                               | Optional healing/recording, avoid duplicate coverage | **+ Healing**: Pattern fixes enhanced with visual debugging + **+ Recording**: AI verified with live browser |
-| `*test-review` | [📖](../workflows/testarch/test-review/README.md) | Test quality review report with 0-100 score, violations, fixes                                | Reviews tests against knowledge base patterns        | -                                                                                                            |
-| `*nfr-assess`  | [📖](../workflows/testarch/nfr-assess/README.md)  | NFR assessment report with actions                                                            | Focus on security/performance/reliability            | -                                                                                                            |
-| `*trace`       | [📖](../workflows/testarch/trace/README.md)       | Phase 1: Coverage matrix, recommendations. Phase 2: Gate decision (PASS/CONCERNS/FAIL/WAIVED) | Two-phase workflow: traceability + gate decision     | -                                                                                                            |
-
-**📖** = Click to view detailed workflow documentation
+| Command        | Primary Outputs                                                                               | Notes                                                | With Playwright MCP Enhancements                                                                             |
+| -------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| `*framework`   | Playwright/Cypress scaffold, `.env.example`, `.nvmrc`, sample specs                           | Use when no production-ready harness exists          | -                                                                                                            |
+| `*ci`          | CI workflow, selective test scripts, secrets checklist                                        | Platform-aware (GitHub Actions default)              | -                                                                                                            |
+| `*test-design` | Combined risk assessment, mitigation plan, and coverage strategy                              | Risk scoring + optional exploratory mode             | **+ Exploratory**: Interactive UI discovery with browser automation (uncover actual functionality)           |
+| `*atdd`        | Failing acceptance tests + implementation checklist                                           | TDD red phase + optional recording mode              | **+ Recording**: AI generation verified with live browser (accurate selectors from real DOM)                 |
+| `*automate`    | Prioritized specs, fixtures, README/script updates, DoD summary                               | Optional healing/recording, avoid duplicate coverage | **+ Healing**: Pattern fixes enhanced with visual debugging + **+ Recording**: AI verified with live browser |
+| `*test-review` | Test quality review report with 0-100 score, violations, fixes                                | Reviews tests against knowledge base patterns        | -                                                                                                            |
+| `*nfr-assess`  | NFR assessment report with actions                                                            | Focus on security/performance/reliability            | -                                                                                                            |
+| `*trace`       | Phase 1: Coverage matrix, recommendations. Phase 2: Gate decision (PASS/CONCERNS/FAIL/WAIVED) | Two-phase workflow: traceability + gate decision     | -                                                                                                            |

package/src/modules/bmm/docs/workflows-solutioning.md

@@ -363,7 +363,7 @@ Planning (prd by PM - FRs/NFRs only)
   → Phase 4 (Implementation)
 ```
 
-**Note on TEA (Test Architect):** TEA is fully operational with 8 workflows across all phases. TEA validates architecture testability during Phase 3 reviews but does not have a dedicated solutioning workflow. TEA's primary setup occurs in Phase 2 (`*framework`, `*ci`, `*test-design`) and testing execution in Phase 4 (`*atdd`, `*automate`, `*test-review`, `*trace`, `*nfr-assess`).
+**Note on TEA (Test Architect):** TEA is fully operational with 8 workflows across all phases. TEA validates architecture testability during Phase 3 reviews but does not have a dedicated solutioning workflow. TEA's primary setup occurs after architecture in Phase 3 (`*framework`, `*ci`, system-level `*test-design`), with optional Phase 2 baseline `*trace`. Testing execution happens in Phase 4 (`*atdd`, `*automate`, `*test-review`, `*trace`, `*nfr-assess`).
 
 **Note:** Enterprise uses the same planning and architecture as BMad Method. The only difference is optional extended workflows added AFTER architecture but BEFORE create-epics-and-stories.
 

package/src/modules/bmm/module.yaml

@@ -43,13 +43,14 @@ project_knowledge: # Artifacts from research, document-project output, other lon
   prompt: "Where should non-ephemeral project knowledge be searched for and stored\n(docs, research, references)?"
   default: "docs"
   result: "{project-root}/{value}"
-# tea_use_mcp_enhancements:
-#   prompt: "Test Architect Playwright MCP capabilities (healing, exploratory, verification) are optionally available.\nYou will have to setup your MCPs yourself; refer to test-architecture.md for hints.\nWould you like to enable MCP enhancements in Test Architect?"
-#   default: false
-#   result: "{value}"
-
-# tea_use_playwright_utils:
-#   prompt:
-#     - "Are you using playwright-utils (@seontechnologies/playwright-utils) in your project?\nYou must install packages yourself, or use test architect's *framework command."
-#   default: false
-#   result: "{value}"
+
+tea_use_mcp_enhancements:
+  prompt: "WEB APP ONLY: Test Architect Playwright MCP capabilities (healing, exploratory, verification) are optionally available.\nYou will have to setup your MCPs yourself; refer to test-architecture.md for hints.\nWould you like to enable MCP enhancements in Test Architect?"
+  default: false
+  result: "{value}"
+
+tea_use_playwright_utils:
+  prompt:
+    - "WEB APP ONLY: Are you using playwright-utils (@seontechnologies/playwright-utils) in your project?\nYou must install packages yourself, or use test architect's *framework command."
+  default: false
+  result: "{value}"

package/src/modules/bmm/workflows/1-analysis/create-product-brief/product-brief.template.md

@@ -1,8 +1,10 @@
-# Product Brief: {{project_name}}
-
-**Date:** {{date}}
-**Author:** {{user_name}}
-
 ---
+stepsCompleted: []
+inputDocuments: []
+date: { system-date }
+author: { user }
+---
+
+# Product Brief: {{project_name}}
 
 <!-- Content will be appended sequentially through collaborative workflow steps -->

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md

@@ -3,13 +3,13 @@ name: 'step-01-init'
 description: 'Initialize the product brief workflow by detecting continuation state and setting up the document'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01-init.md'
 nextStepFile: '{workflow_path}/steps/step-02-vision.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Template References
 productBriefTemplate: '{workflow_path}/product-brief.template.md'

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md

@@ -3,14 +3,12 @@ name: 'step-01b-continue'
 description: 'Resume the product brief workflow from where it was left off, ensuring smooth continuation'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
-# Task References
-# (No task references used in this continuation step)
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 ---
 
 # Step 1B: Product Brief Continuation

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md

@@ -3,13 +3,13 @@ name: 'step-02-vision'
 description: 'Discover and define the core product vision, problem statement, and unique value proposition'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-02-vision.md'
 nextStepFile: '{workflow_path}/steps/step-03-users.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md

@@ -3,13 +3,13 @@ name: 'step-03-users'
 description: 'Define target users with rich personas and map their key interactions with the product'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-users.md'
 nextStepFile: '{workflow_path}/steps/step-04-metrics.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md

@@ -3,13 +3,13 @@ name: 'step-04-metrics'
 description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-04-metrics.md'
 nextStepFile: '{workflow_path}/steps/step-05-scope.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md

@@ -3,13 +3,13 @@ name: 'step-05-scope'
 description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-05-scope.md'
 nextStepFile: '{workflow_path}/steps/step-06-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'

package/src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md

@@ -3,14 +3,12 @@ name: 'step-06-complete'
 description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
-# Task References
-# (No task references used in this completion step)
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
 ---
 
 # Step 6: Product Brief Completion
@@ -84,9 +82,8 @@ This brief serves as the foundation for all subsequent product development activ
 **Status File Management:**
 Update the main workflow status file:
 
-- Check if `{output_folder}/bmm-workflow-status.yaml` exists
-- If not, create it with basic structure
-- Update workflow_status["product-brief"] = `{outputFile}`
+- Check if `{output_folder} or {planning_artifacts}/bmm-workflow-status.yaml` exists
+- If so, update workflow_status["product-brief"] = `{outputFile}`
 - Add completion timestamp and metadata
 - Save file, preserving all comments and structure
 
@@ -113,7 +110,7 @@ Perform final validation of the product brief:
 **Recommended Next Workflow:**
 Provide guidance on logical next workflows:
 
-1. `workflow prd` - Create detailed Product Requirements Document
+1. `create-prd` - Create detailed Product Requirements Document
    - Brief provides foundation for detailed requirements
    - User personas inform journey mapping
    - Success metrics become specific acceptance criteria
@@ -121,8 +118,8 @@ Provide guidance on logical next workflows:
 
 **Other Potential Next Steps:**
 
-2. `workflow create-ux-design` - UX research and design (can run parallel with PRD)
-3. `workflow domain-research` - Deep market or domain research (if needed)
+1. `create-ux-design` - UX research and design (can run parallel with PRD)
+2. `domain-research` - Deep market or domain research (if needed)
 
 **Strategic Considerations:**
 

package/src/modules/bmm/workflows/1-analysis/create-product-brief/workflow.md

@@ -49,10 +49,10 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
 
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`
 
 ### 2. First Step EXECUTION
 
-Load, read the full file and then execute `{project-root}/_bmad/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md` to begin the workflow.
+Load, read the full file and then execute `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.

package/src/modules/bmm/workflows/1-analysis/research/research.template.md

@@ -1,3 +1,17 @@
+---
+stepsCompleted: []
+inputDocuments: []
+workflowType: 'research'
+lastStep: 1
+research_type: '{{research_type}}'
+research_topic: '{{research_topic}}'
+research_goals: '{{research_goals}}'
+user_name: '{{user_name}}'
+date: '{{date}}'
+web_research_enabled: true
+source_verification: true
+---
+
 # Research Report: {{research_type}}
 
 **Date:** {{date}}