5 levels of scale adaption compressed to 3 clear distinctions driven by user preference and project needs

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

@@ -8,26 +8,26 @@
 
 ## 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!
 
 ---
 
@@ -68,7 +68,7 @@ flowchart TD
 
 ---
 
-## Level 0: Single Atomic Change
+## Single Atomic Change
 
 **Best for:** Bug fixes, single file changes, isolated improvements
 
@@ -104,7 +104,7 @@ flowchart TD
 - ✅ 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"
@@ -113,13 +113,13 @@ flowchart TD
 
 ---
 
-## 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
@@ -147,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"
@@ -302,7 +302,7 @@ Generates scores:
 - Implementation Readiness: ✅ Ready
 ```
 
-### Story Validation (Level 1 Only)
+### Story Validation (Multi-Story Features)
 
 Checks:
 
@@ -317,7 +317,7 @@ Checks:
 
 ## Complete User Journey
 
-### Scenario 1: Bug Fix (Level 0)
+### Scenario 1: Bug Fix (Single Change)
 
 **Goal:** Fix login validation bug
 
@@ -342,7 +342,7 @@ Checks:
 
 ---
 
-### Scenario 2: Small Feature (Level 1)
+### Scenario 2: Small Feature (Multi-Story)
 
 **Goal:** Add OAuth social login (Google, GitHub)
 
@@ -392,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)
@@ -405,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 |
@@ -419,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!
 
 ---
 
@@ -466,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
 
@@ -500,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
@@ -525,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?
 
@@ -566,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!
 
@@ -580,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"
 
@@ -596,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"