bmad-method 6.0.0-alpha.4 → 6.0.0-alpha.5

package/bmad/bmm/docs/quick-spec-flow.md

@@ -8,60 +8,67 @@
 
 ## What is Quick Spec Flow?
 
-Quick Spec Flow is a **streamlined alternative** to the full BMad Method for Level 0-1 projects. Instead of going through Product Brief → PRD → Architecture, you go **straight to a context-aware technical specification** and start coding.
+Quick Spec Flow is a **streamlined alternative** to the full BMad Method for Quick Flow track projects. Instead of going through Product Brief → PRD → Architecture, you go **straight to a context-aware technical specification** and start coding.
 
 ### When to Use Quick Spec Flow
 
-✅ **Use Quick Spec Flow (Level 0-1) when:**
+✅ **Use Quick Flow track when:**
 
-- Single bug fix or small enhancement (Level 0)
-- Small feature with 2-3 related changes (Level 1)
+- Single bug fix or small enhancement
+- Small feature with clear scope (typically 1-15 stories)
 - Rapid prototyping or experimentation
 - Adding to existing brownfield codebase
 - You know exactly what you want to build
 
-❌ **Use Full BMM Flow (Level 2-4) when:**
+❌ **Use BMad Method or Enterprise tracks when:**
 
-- Building new products or major features (Level 2-4)
+- Building new products or major features
 - Need stakeholder alignment
 - Complex multi-team coordination
 - Requires extensive planning and architecture
 
-💡 **Not sure?** Run `workflow-init` to get a recommendation based on your project's size and complexity!
+💡 **Not sure?** Run `workflow-init` to get a recommendation based on your project's needs!
 
 ---
 
 ## Quick Spec Flow Overview
 
-```
-┌─────────────────────────────────────────────────────────────┐
-│                    QUICK SPEC FLOW                          │
-│                   (Level 0-1 Projects)                      │
-└─────────────────────────────────────────────────────────────┘
-
-Step 1: Run Tech-Spec Workflow
-    │
-    ├─► Detects your project stack (package.json, requirements.txt, etc.)
-    ├─► Analyzes brownfield codebase (if exists)
-    ├─► Detects test frameworks and conventions
-    ├─► Confirms conventions with you
-    ├─► Generates context-rich tech-spec
-    └─► Creates ready-to-implement stories
-
-Step 2: Optional - Generate Story Context (SM Agent)
-    │
-    └─► For complex scenarios only
-
-Step 3: Implement (DEV Agent)
-    │
-    └─► Code, test, commit
-
-DONE! 🚀
+```mermaid
+flowchart TD
+    START[Step 1: Run Tech-Spec Workflow]
+    DETECT[Detects project stack<br/>package.json, requirements.txt, etc.]
+    ANALYZE[Analyzes brownfield codebase<br/>if exists]
+    TEST[Detects test frameworks<br/>and conventions]
+    CONFIRM[Confirms conventions<br/>with you]
+    GENERATE[Generates context-rich<br/>tech-spec]
+    STORIES[Creates ready-to-implement<br/>stories]
+
+    OPTIONAL[Step 2: Optional<br/>Generate Story Context<br/>SM Agent<br/>For complex scenarios only]
+
+    IMPL[Step 3: Implement<br/>DEV Agent<br/>Code, test, commit]
+
+    DONE[DONE! 🚀]
+
+    START --> DETECT
+    DETECT --> ANALYZE
+    ANALYZE --> TEST
+    TEST --> CONFIRM
+    CONFIRM --> GENERATE
+    GENERATE --> STORIES
+    STORIES --> OPTIONAL
+    OPTIONAL -.->|Optional| IMPL
+    STORIES --> IMPL
+    IMPL --> DONE
+
+    style START fill:#bfb,stroke:#333,stroke-width:2px
+    style OPTIONAL fill:#ffb,stroke:#333,stroke-width:2px,stroke-dasharray: 5 5
+    style IMPL fill:#bbf,stroke:#333,stroke-width:2px
+    style DONE fill:#f9f,stroke:#333,stroke-width:3px
 ```
 
 ---
 
-## Level 0: Single Atomic Change
+## Single Atomic Change
 
 **Best for:** Bug fixes, single file changes, isolated improvements
 
@@ -97,7 +104,7 @@ DONE! 🚀
 - ✅ Auto-validates quality
 - ✅ Story context optional (tech-spec is comprehensive!)
 
-### Example Level 0 Scenarios
+### Example Single Change Scenarios
 
 - "Fix the login validation bug"
 - "Add email field to user registration form"
@@ -106,13 +113,13 @@ DONE! 🚀
 
 ---
 
-## Level 1: Coherent Small Feature
+## Coherent Small Feature
 
 **Best for:** Small features with 2-3 related user stories
 
 ### What You Get
 
-1. **tech-spec.md** - Same comprehensive spec as Level 0
+1. **tech-spec.md** - Same comprehensive spec as single change projects
 2. **epics.md** - Epic organization with story breakdown
 3. **story-[epic-slug]-1.md** - First story
 4. **story-[epic-slug]-2.md** - Second story
@@ -140,7 +147,7 @@ Stories are **automatically validated** to ensure proper sequence:
 - ✅ Infrastructure → Features → Polish order
 - ✅ Backend → Frontend flow
 
-### Example Level 1 Scenarios
+### Example Small Feature Scenarios
 
 - "Add OAuth social login (Google, GitHub, Twitter)"
 - "Build user profile page with avatar upload"
@@ -295,7 +302,7 @@ Generates scores:
 - Implementation Readiness: ✅ Ready
 ```
 
-### Story Validation (Level 1 Only)
+### Story Validation (Multi-Story Features)
 
 Checks:
 
@@ -310,7 +317,7 @@ Checks:
 
 ## Complete User Journey
 
-### Scenario 1: Bug Fix (Level 0)
+### Scenario 1: Bug Fix (Single Change)
 
 **Goal:** Fix login validation bug
 
@@ -335,7 +342,7 @@ Checks:
 
 ---
 
-### Scenario 2: Small Feature (Level 1)
+### Scenario 2: Small Feature (Multi-Story)
 
 **Goal:** Add OAuth social login (Google, GitHub)
 
@@ -385,7 +392,7 @@ Quick Spec Flow works seamlessly with all Phase 4 implementation workflows:
 ### sprint-planning (SM Agent)
 
 - ✅ Works with epics.md from tech-spec
-- ✅ Organizes Level 1 stories for coordinated implementation
+- ✅ Organizes multi-story features for coordinated implementation
 - ✅ Tracks progress through sprint-status.yaml
 
 ### dev-story (DEV Agent)
@@ -398,7 +405,7 @@ Quick Spec Flow works seamlessly with all Phase 4 implementation workflows:
 
 ## Comparison: Quick Spec vs Full BMM
 
-| Aspect                | Quick Spec Flow (Level 0-1)  | Full BMM Flow (Level 2-4)          |
+| Aspect                | Quick Flow Track             | BMad Method/Enterprise Tracks      |
 | --------------------- | ---------------------------- | ---------------------------------- |
 | **Setup**             | None (standalone)            | workflow-init recommended          |
 | **Planning Docs**     | tech-spec.md only            | Product Brief → PRD → Architecture |
@@ -412,18 +419,18 @@ Quick Spec Flow works seamlessly with all Phase 4 implementation workflows:
 
 ---
 
-## When to Graduate from Quick Spec to Full BMM
+## When to Graduate from Quick Flow to BMad Method
 
-Start with Quick Spec, but switch to Full BMM when:
+Start with Quick Flow, but switch to BMad Method when:
 
-- ❌ Project grows beyond 3-5 stories
+- ❌ Project grows beyond initial scope
 - ❌ Multiple teams need coordination
 - ❌ Stakeholders need formal documentation
 - ❌ Product vision is unclear
 - ❌ Architectural decisions need deep analysis
 - ❌ Compliance/regulatory requirements exist
 
-💡 **Tip:** You can always run `workflow-init` later to transition from Quick Spec to Full BMM!
+💡 **Tip:** You can always run `workflow-init` later to transition from Quick Flow to BMad Method!
 
 ---
 
@@ -459,8 +466,8 @@ Start with Quick Spec, but switch to Full BMM when:
 
 ### 🎯 **Focus**
 
-- Level 0: Single atomic change
-- Level 1: Coherent small feature
+- Single atomic changes
+- Coherent small features
 - No scope creep
 - Fast iteration
 
@@ -493,7 +500,7 @@ Start with Quick Spec, but switch to Full BMM when:
 
 Quick Spec Flow is **fully standalone**:
 
-- Detects if you're Level 0 or Level 1
+- Detects if it's a single change or multi-story feature
 - Asks for greenfield vs brownfield
 - Works without status file tracking
 - Perfect for rapid prototyping
@@ -518,13 +525,13 @@ Quick Spec Flow is **fully standalone**:
 
 **A:** Absolutely! Quick Spec Flow captures UX/UI considerations, component changes, and accessibility requirements.
 
-### Q: What if my Level 0 project grows?
+### Q: What if my Quick Flow project grows?
 
-**A:** No problem! You can always transition to Full BMM by running workflow-init and create-prd. Your tech-spec becomes input for the PRD.
+**A:** No problem! You can always transition to BMad Method by running workflow-init and create-prd. Your tech-spec becomes input for the PRD.
 
 ### Q: Do I need story-context for every story?
 
-**A:** Usually no! Tech-spec is comprehensive enough for most Level 0-1 projects. Only use story-context for complex edge cases.
+**A:** Usually no! Tech-spec is comprehensive enough for most Quick Flow projects. Only use story-context for complex edge cases.
 
 ### Q: Can I skip validation?
 
@@ -559,13 +566,13 @@ When validation runs, read the scores. They tell you if your spec is production-
 
 ### 5. **Story Context is Optional**
 
-For Level 0, try going directly to dev-story first. Only add story-context if you hit complexity.
+For single changes, try going directly to dev-story first. Only add story-context if you hit complexity.
 
-### 6. **Keep Level 0 Truly Atomic**
+### 6. **Keep Single Changes Truly Atomic**
 
-If your "single change" needs 3+ files, it might be Level 1. Let the workflow guide you.
+If your "single change" needs 3+ files, it might be a multi-story feature. Let the workflow guide you.
 
-### 7. **Validate Story Sequence for Level 1**
+### 7. **Validate Story Sequence for Multi-Story Features**
 
 When you get multiple stories, check the dependency validation output. Proper sequence matters!
 
@@ -573,7 +580,7 @@ When you get multiple stories, check the dependency validation output. Proper se
 
 ## Real-World Examples
 
-### Example 1: Adding Logging (Level 0)
+### Example 1: Adding Logging (Single Change)
 
 **Input:** "Add structured logging to payment processing"
 
@@ -589,7 +596,7 @@ When you get multiple stories, check the dependency validation output. Proper se
 
 ---
 
-### Example 2: Search Feature (Level 1)
+### Example 2: Search Feature (Multi-Story)
 
 **Input:** "Add search to product catalog with filters"
 

package/bmad/bmm/docs/quick-start.md

@@ -19,7 +19,7 @@ BMad Method (BMM) helps you build software through guided workflows with special
 
 1. **Phase 1: Analysis** (Optional) - Brainstorming, Research, Product Brief
 2. **Phase 2: Planning** (Required) - Create your requirements (tech-spec or PRD)
-3. **Phase 3: Architecture** (Conditional) - Design the architecture for complex projects (10+ stories)
+3. **Phase 3: Solutioning** (Track-dependent) - Design the architecture for BMad Method and Enterprise tracks
 4. **Phase 4: Implementation** (Required) - Build your software Epic by Epic, Story by Story
 
 ## Installation
@@ -54,28 +54,28 @@ During workflow-init, you'll describe:
 - Whether there's an existing codebase or this is a new project
 - The general size and complexity (you can adjust this later)
 
-#### Project Scale Levels
+#### Planning Tracks
 
-Based on your description, the workflow will suggest a level and let you choose from:
+Based on your description, the workflow will suggest a track and let you choose from:
 
-**Greenfield Project Levels:**
+**Three Planning Tracks:**
 
-- **Level 0** - Single atomic change (1 story) - bug fixes, typos, minor updates, single file changes
-- **Level 1** - Small feature (1-10 stories) - simple additions, isolated features, one module
-- **Level 2** - Medium feature set (5-15 stories) - dashboards, multiple related features, several modules
-- **Level 3** - Complex integration (12-40 stories) - platform features, major integrations, architectural changes
-- **Level 4** - Enterprise expansion (40+ stories) - multi-tenant, ecosystem changes, system-wide initiatives
+- **Quick Flow** - Fast implementation (tech-spec only) - bug fixes, simple features, clear scope (typically 1-15 stories)
+- **BMad Method** - Full planning (PRD + Architecture + UX) - products, platforms, complex features (typically 10-50+ stories)
+- **Enterprise Method** - Extended planning (BMad Method + Security/DevOps/Test) - enterprise requirements, compliance, multi-tenant (typically 30+ stories)
+
+**Note**: Story counts are guidance, not definitions. Tracks are chosen based on planning needs, not story math.
 
 #### What gets created?
 
-Once you confirm your level, the `bmm-workflow-status.md` file will be created in your project's docs folder (assuming default install location). This file tracks your progress through all phases.
+Once you confirm your track, the `bmm-workflow-status.yaml` file will be created in your project's docs folder (assuming default install location). This file tracks your progress through all phases.
 
 **Important notes:**
 
-- Every level has different paths through the phases
+- Every track has different paths through the phases
 - Story counts can still change based on overall complexity as you work
-- For this guide, we'll assume a Level 2 project
-- This workflow will guide you through Phase 1 (optional), Phase 2 (required), and Phase 3 (required for Level 2+ complexity)
+- For this guide, we'll assume a BMad Method track project
+- This workflow will guide you through Phase 1 (optional), Phase 2 (required), and Phase 3 (required for BMad Method and Enterprise tracks)
 
 ### Step 2: Work Through Phases 1-3
 
@@ -100,12 +100,12 @@ Phase 1 (Analysis) is entirely optional. All workflows are optional or recommend
 The next TRULY REQUIRED step is:
   - PRD (Product Requirements Document) in Phase 2 - Planning
   - Agent: pm
-  - Command: /bmad:bmm:workflows:prd
+  - Command: prd
 ```
 
 #### How to Run Workflows in Phases 1-3
 
-When an agent tells you to run a workflow (like `/bmad:bmm:workflows:prd`):
+When an agent tells you to run a workflow (like `prd`):
 
 1. **Start a new chat** with the specified agent (e.g., PM) - See [docs/ide-info](../docs/ide-info/) for your IDE's specific instructions
 2. **Wait for the menu** to appear
@@ -121,21 +121,21 @@ The agents in V6 are very good with fuzzy menu matching!
 For v4 users or those who prefer to skip workflow-status guidance:
 
 - **Analyst** → Brainstorming, Product Brief
-- **PM** → PRD (10+ stories) OR tech-spec (1-10 stories)
+- **PM** → PRD (BMad Method/Enterprise tracks) OR tech-spec (Quick Flow track)
 - **UX-Designer** → UX Design Document (if UI-heavy)
-- **Architect** → Architecture (10+ stories)
+- **Architect** → Architecture (BMad Method/Enterprise tracks)
 
 #### Phase 2: Planning - Creating the PRD
 
-**For Level 2+ projects (10+ stories):**
+**For BMad Method and Enterprise tracks:**
 
 1. Load the **PM agent** in a new chat
 2. Tell it to run the PRD workflow
-3. Once complete, you'll have two files:
+3. Once complete, you'll have:
    - **PRD.md** - Your Product Requirements Document
-   - **Epics.md** - High-level epics with stories
+   - Epic breakdown
 
-**For smaller projects (Levels 0-1):**
+**For Quick Flow track:**
 
 - Use **tech-spec** instead of PRD (no architecture needed)
 
@@ -149,7 +149,7 @@ If your project has a user interface:
 
 #### Phase 3: Architecture
 
-**For Level 2+ projects only:**
+**For BMad Method and Enterprise tracks:**
 
 1. Load the **Architect agent** in a new chat
 2. Tell it to run the create-architecture workflow
@@ -261,7 +261,7 @@ The agent creates documents, asks questions, and helps you make decisions throug
 
 BMad creates two files to track your progress:
 
-**1. bmm-workflow-status.md**
+**1. bmm-workflow-status.yaml**
 
 - Shows which phase you're in and what's next
 - Created by workflow-init
@@ -280,28 +280,59 @@ BMad creates two files to track your progress:
 
 ## The Complete Flow Visualized
 
-```
-Phase 1 (Optional)          Phase 2 (Required)         Phase 3 (Conditional)        Phase 4 (Required)
-┌─────────────────┐        ┌─────────────────┐        ┌─────────────────┐         ┌──────────────────┐
-│ Analysis        │        │ Planning        │        │ Architecture    │         │ Implementation   │
-│                 │        │                 │        │                 │         │                  │
-│ • Brainstorm    │        │ Level 0-1:      │        │ Level 2+:       │         │ Per Epic:        │
-│ • Research      │───────▶│  • tech-spec    │───────▶│  • architecture │────────▶│  • epic context  │
-│ • Brief         │        │                 │        │  • gate-check   │         │                  │
-│                 │        │ Level 2+:       │        │                 │         │ Per Story:       │
-│ (Analyst)       │        │  • PRD          │        │ (Architect)     │         │  • create-story  │
-│                 │        │  • UX (opt)     │        │                 │         │  • story-context │
-│                 │        │                 │        │                 │         │  • dev-story     │
-│                 │        │ (PM, UX)        │        │                 │         │  • code-review   │
-│                 │        │                 │        │                 │         │                  │
-│                 │        │                 │        │                 │         │ (SM, DEV)        │
-└─────────────────┘        └─────────────────┘        └─────────────────┘         └──────────────────┘
+```mermaid
+flowchart LR
+    subgraph P1["Phase 1 (Optional)<br/>Analysis"]
+        direction TB
+        A1[Brainstorm]
+        A2[Research]
+        A3[Brief]
+        A4[Analyst]
+        A1 ~~~ A2 ~~~ A3 ~~~ A4
+    end
+
+    subgraph P2["Phase 2 (Required)<br/>Planning"]
+        direction TB
+        B1[Quick Flow:<br/>tech-spec]
+        B2[Method/Enterprise:<br/>PRD]
+        B3[UX opt]
+        B4[PM, UX]
+        B1 ~~~ B2 ~~~ B3 ~~~ B4
+    end
+
+    subgraph P3["Phase 3 (Track-dependent)<br/>Solutioning"]
+        direction TB
+        C1[Method/Enterprise:<br/>architecture]
+        C2[gate-check]
+        C3[Architect]
+        C1 ~~~ C2 ~~~ C3
+    end
+
+    subgraph P4["Phase 4 (Required)<br/>Implementation"]
+        direction TB
+        D1[Per Epic:<br/>epic context]
+        D2[Per Story:<br/>create-story]
+        D3[story-context]
+        D4[dev-story]
+        D5[code-review]
+        D6[SM, DEV]
+        D1 ~~~ D2 ~~~ D3 ~~~ D4 ~~~ D5 ~~~ D6
+    end
+
+    P1 --> P2
+    P2 --> P3
+    P3 --> P4
+
+    style P1 fill:#bbf,stroke:#333,stroke-width:2px
+    style P2 fill:#bfb,stroke:#333,stroke-width:2px
+    style P3 fill:#ffb,stroke:#333,stroke-width:2px
+    style P4 fill:#fbf,stroke:#333,stroke-width:2px
 ```
 
 ## Common Questions
 
 **Q: Do I always need architecture?**
-A: Only for larger projects (10+ stories). Small projects can skip straight from tech-spec to implementation.
+A: Only for BMad Method and Enterprise tracks. Quick Flow projects skip straight from tech-spec to implementation.
 
 **Q: Can I change my plan later?**
 A: Yes! The SM agent has a "correct-course" workflow for handling scope changes.
@@ -328,14 +359,8 @@ A: Yes, once you learn the flow. Use the Quick Reference in Step 2 to go directl
 
 ✅ **Always use fresh chats** - Load agents in new chats for each workflow to avoid context issues
 ✅ **Let workflow-status guide you** - Load any agent and ask for status when unsure what's next
-✅ **Level matters** - Small projects (0-1) use tech-spec, larger projects (2+) need PRD and architecture
+✅ **Track matters** - Quick Flow uses tech-spec, BMad Method/Enterprise need PRD and architecture
 ✅ **Tracking is automatic** - The status files update themselves, no manual editing needed
 ✅ **Agents are flexible** - Use menu numbers, shortcuts (\*prd), or natural language
 
 **Ready to start building?** Install BMad, load the Analyst, run workflow-init, and let the agents guide you!
-
----
-
-**Version**: v6-alpha
-**Last Updated**: 2025-01
-**For detailed documentation**: [Complete BMM Workflows Guide](../src/modules/bmm/workflows/README.md)