bmad-method 6.0.0-alpha.15 → 6.0.0-alpha.17

package/src/modules/bmm/agents/tech-writer.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/tech-writer.md"
+    id: "_bmad/bmm/agents/tech-writer.md"
     name: Paige
     title: Technical Writer
     icon: 📚
@@ -17,12 +17,12 @@ agent:
       - Docs are living artifacts that evolve with code. Know when to simplify vs when to be detailed.
 
   critical_actions:
-    - "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/data/documentation-standards.md into permanent memory and follow ALL rules within"
+    - "CRITICAL: Load COMPLETE file {project-root}/_bmad/bmm/data/documentation-standards.md into permanent memory and follow ALL rules within"
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
     - trigger: document-project
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml"
       description: Comprehensive project documentation (brownfield analysis, architecture scanning)
 
     - trigger: generate-mermaid
@@ -30,15 +30,15 @@ agent:
       description: Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)
 
     - trigger: create-excalidraw-flowchart
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-flowchart/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml"
       description: Create Excalidraw flowchart for processes and logic flows
 
     - trigger: create-excalidraw-diagram
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml"
       description: Create Excalidraw system architecture or technical diagram
 
     - trigger: create-excalidraw-dataflow
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml"
       description: Create Excalidraw data flow diagram
 
     - trigger: validate-doc
@@ -54,14 +54,14 @@ agent:
       description: Create clear technical explanations with examples
 
     - trigger: standards-guide
-      action: "Display the complete documentation standards from {project-root}/{bmad_folder}bmm/data/documentation-standards.md in a clear, formatted way for the user."
+      action: "Display the complete documentation standards from {project-root}/_bmadbmm/data/documentation-standards.md in a clear, formatted way for the user."
       description: Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)
 
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/bmm/agents/ux-designer.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/bmm/agents/ux-designer.md"
+    id: "_bmad/bmm/agents/ux-designer.md"
     name: Sally
     title: UX Designer
     icon: 🎨
@@ -24,22 +24,22 @@ agent:
 
   menu:
     - trigger: create-ux-design
-      exec: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
       description: Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture)
 
     - trigger: validate-design
-      validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
+      validate-workflow: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
       description: Validate UX Specification and Design Artifacts
 
     - trigger: create-excalidraw-wireframe
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-wireframe/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml"
       description: Create website or app wireframe (Excalidraw)
 
     - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: Bring the whole team in to chat with other expert agents from the party
 
     - trigger: advanced-elicitation
-      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
       web-only: true

package/src/modules/bmm/docs/README.md

@@ -139,9 +139,6 @@ Comprehensive documentation for all BMM workflows organized by phase:
   - Complete story lifecycle
   - One-story-at-a-time discipline
 
-<<<<<<< Updated upstream
-<<<<<<< Updated upstream
-
 - **[Testing & QA Workflows](./test-architecture.md)** - Comprehensive quality assurance (1,420 lines)
   - Test strategy, automation, quality gates
   - TEA agent and test healing
@@ -149,14 +146,6 @@ Comprehensive documentation for all BMM workflows organized by phase:
 
 **Total: 34 workflows documented across all phases**
 
-=======
-
-> > > > > > > Stashed changes
-
-=======
-
-> > > > > > > Stashed changes
-
 ### Advanced Workflow References
 
 For detailed technical documentation on specific complex workflows:
@@ -181,23 +170,9 @@ Quality assurance guidance:
 
 <!-- Test Architect documentation to be added -->
 
-<<<<<<< Updated upstream
-
-<<<<<<< Updated upstream
-
 - Test design workflows
 - Quality gates
 - Risk assessment
-- # NFR validation
-  =======
-  > > > > > > > Stashed changes
-  - Test design workflows
-  - Quality gates
-  - Risk assessment
-  - NFR validation
-    > > > > > > > Stashed changes
-
----
 
 ## 🏗️ Module Structure
 

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

@@ -180,11 +180,13 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 - `workflow-status` - Check what to do next
 - `sprint-planning` - Initialize `sprint-status.yaml` tracking
-- `create-story` - Draft next story from epic
-- `validate-create-story` - Independent story validation
+- `create-story` - Create next story from epic (sets status to `ready-for-dev`)
+- `validate-create-story` - Optional quality check (does not change status; run before dev-story for extra validation)
 - `epic-retrospective` - Post-epic review
 - `correct-course` - Handle changes during implementation
 
+**Story handoff sequence:** `create-story` → (optional) `validate-create-story` → `dev-story`
+
 **Communication Style:** Task-oriented and efficient. Direct and eliminates ambiguity. Focuses on clear handoffs and developer-ready specifications.
 
 **Expertise:**
@@ -212,7 +214,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 **Workflows:**
 
 - `workflow-status` - Check what to do next
-- `develop-story` - Implement story with:
+- `dev-story` - Implement story with:
   - Task-by-task iteration
   - Test-driven development
   - Multi-run capability (initial + fixes)
@@ -449,7 +451,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 **Workflows:**
 
 - `workflow-status` - Check what to do next
-- `develop-story` - Execute Dev Story workflow, implementing tasks and tests
+- `dev-story` - Execute Dev Story workflow, implementing tasks and tests
 - `code-review` - Perform thorough clean context QA code review on a story
 
 **Communication Style:** Direct and energetic. Execution-focused. Breaks down complex game challenges into actionable steps. Celebrates performance wins.
@@ -644,7 +646,7 @@ Many workflows have optional validation workflows that perform independent revie
 | -------------------------- | ----------- | ------------------------------------------ |
 | `implementation-readiness` | Architect   | PRD + Architecture + Epics + UX (optional) |
 | `validate-design`          | UX Designer | UX specification and artifacts             |
-| `validate-create-story`    | SM          | Story draft                                |
+| `validate-create-story`    | SM          | Story file                                 |
 
 **When to use validation:**
 
@@ -661,14 +663,14 @@ You can customize any agent's personality without modifying core agent files.
 
 ### Location
 
-**Customization Directory:** `{project-root}/{bmad_folder}/_cfg/agents/`
+**Customization Directory:** `{project-root}/_bmad/_config/agents/`
 
 **Naming Convention:** `{module}-{agent-name}.customize.yaml`
 
 **Examples:**
 
 ```
-{bmad_folder}/_cfg/agents/
+_bmad/_config/agents/
 ├── bmm-pm.customize.yaml
 ├── bmm-dev.customize.yaml
 ├── cis-storyteller.customize.yaml
@@ -768,9 +770,9 @@ Other agents collaborate with PM's specialized perspective.
 
 ```bash
 # Create customization file at:
-# {project-root}/{bmad_folder}/_cfg/agents/{module}-{agent-name}.customize.yaml
+# {project-root}/_bmad/_config/agents/{module}-{agent-name}.customize.yaml
 
-# Example: {bmad_folder}/_cfg/agents/bmm-pm.customize.yaml
+# Example: _bmad/_config/agents/bmm-pm.customize.yaml
 ```
 
 **Step 2: Regenerate Agent Manifest**
@@ -900,7 +902,7 @@ Load the customized agent and verify the changes are reflected in its behavior a
 
 ```
 1. SM: *create-story
-2. DEV: *develop-story
+2. DEV: *dev-story
 3. DEV: *code-review
 4. Repeat steps 1-3 for next story
 ```
@@ -910,7 +912,7 @@ Load the customized agent and verify the changes are reflected in its behavior a
 ```
 1. TEA: *framework (once per project, early)
 2. TEA: *atdd (before implementing features)
-3. DEV: *develop-story (includes tests)
+3. DEV: *dev-story (includes tests)
 4. TEA: *automate (comprehensive test suite)
 5. TEA: *trace (quality gate)
 6. TEA: *ci (pipeline setup)
@@ -975,12 +977,12 @@ Quick reference for agent selection:
 | **UX Designer**         | 🎨   | 2 (Planning)            | create-ux-design, validate-design             | UX-heavy projects, design               |
 | **Architect**           | 🏗️   | 3 (Solutioning)         | architecture, implementation-readiness        | Technical design, architecture          |
 | **SM**                  | 🏃   | 4 (Implementation)      | sprint-planning, create-story                 | Story management, sprint coordination   |
-| **DEV**                 | 💻   | 4 (Implementation)      | develop-story, code-review                    | Implementation, coding                  |
+| **DEV**                 | 💻   | 4 (Implementation)      | dev-story, code-review                        | Implementation, coding                  |
 | **TEA**                 | 🧪   | All Phases              | framework, atdd, automate, trace, ci          | Testing, quality assurance              |
 | **Paige (Tech Writer)** | 📚   | All Phases              | document-project, diagrams, validation        | Documentation, diagrams                 |
 | **Principal Engineer**  | ⚡   | Quick Flow (All phases) | create-tech-spec, quick-dev, code-review      | Rapid development, technical leadership |
 | **Game Designer**       | 🎲   | 1-2 (Games)             | brainstorm-game, gdd, narrative               | Game design, creative vision            |
-| **Game Developer**      | 🕹️   | 4 (Games)               | develop-story, code-review                    | Game implementation                     |
+| **Game Developer**      | 🕹️   | 4 (Games)               | dev-story, code-review                        | Game implementation                     |
 | **Game Architect**      | 🏛️   | 3 (Games)               | architecture, implementation-readiness        | Game systems architecture               |
 | **BMad Master**         | 🧙   | Meta                    | party-mode, list tasks/workflows              | Orchestration, multi-agent              |
 
@@ -1070,7 +1072,7 @@ Quick reference for agent selection:
 
 - [ ] SM: `*sprint-planning` (once)
 - [ ] SM: `*create-story`
-- [ ] DEV: `*develop-story`
+- [ ] DEV: `*dev-story`
 - [ ] DEV: `*code-review`
 
 **Testing Strategy:**

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

@@ -137,7 +137,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections):
 
    ```bash
    # Load BMad Master or any agent
-   {bmad_folder}/core/tools/shard-doc.xml --input docs/massive-doc.md
+   _bmad/core/tools/shard-doc.xml --input docs/massive-doc.md
    ```
 
    - Splits on level 2 sections by default
@@ -147,7 +147,7 @@ If you have documentation but files are huge (>500 lines, 10+ level 2 sections):
 2. **Then:** Run `index-docs` task to create navigation:
 
    ```bash
-   {bmad_folder}/core/tasks/index-docs.xml --directory ./docs
+   _bmad/core/tasks/index-docs.xml --directory ./docs
    ```
 
 3. **Finally:** Validate quality - if sharded docs still seem incomplete/outdated → Run `document-project`
@@ -210,7 +210,7 @@ If you have **good, current documentation** but it's in massive files:
 
 ```bash
 # For each massive doc (>500 lines or 10+ level 2 sections)
-{bmad_folder}/core/tools/shard-doc.xml \
+_bmad/core/tools/shard-doc.xml \
   --input docs/api-documentation.md \
   --output docs/api/ \
   --level 2  # Split on ## headers (default)
@@ -219,7 +219,7 @@ If you have **good, current documentation** but it's in massive files:
 **Step 2: Generate index**
 
 ```bash
-{bmad_folder}/core/tasks/index-docs.xml --directory ./docs
+_bmad/core/tasks/index-docs.xml --directory ./docs
 ```
 
 **Step 3: Validate**
@@ -340,7 +340,7 @@ flowchart TD
 **Status Progression:**
 
 - Epic: `backlog → in-progress → done`
-- Story: `backlog → drafted → ready-for-dev → in-progress → review → done`
+- Story: `backlog → ready-for-dev → in-progress → review → done`
 
 **Brownfield-Specific Implementation Tips:**
 
@@ -397,7 +397,7 @@ Document in tech-spec/architecture:
 ### 8. Use Sprint Planning Effectively
 
 - Run `sprint-planning` at Phase 4 start
-- Context epics before drafting stories
+- Context epics before creating stories
 - Update `sprint-status.yaml` as work progresses
 
 ### 9. Learn Continuously

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

@@ -425,7 +425,7 @@ Team C (2 devs): Analytics feature (3 epics)
 
 **Problem:** Teams customize BMad (agents, workflows, configs) but don't want personal tooling in main repo.
 
-**Anti-pattern:** Adding `{bmad_folder}/` to `.gitignore` breaks IDE tools, submodule management.
+**Anti-pattern:** Adding `_bmad/` to `.gitignore` breaks IDE tools, submodule management.
 
 ### The Solution: Git Submodules
 
@@ -463,7 +463,7 @@ git commit -m "Add BMM as submodule"
 git clone https://github.com/your-org/your-project.git
 cd your-project
 git submodule update --init --recursive
-# Make personal customizations in {bmad_folder}/
+# Make personal customizations in _bmad/
 ```
 
 ### Daily Workflow
@@ -472,7 +472,7 @@ git submodule update --init --recursive
 
 ```bash
 cd /path/to/your-project
-# BMad available at ./{bmad_folder}/, load agents normally
+# BMad available at ./_bmad/, load agents normally
 ```
 
 **Update personal config:**

package/src/modules/bmm/docs/faq.md

@@ -199,24 +199,11 @@ PRDs are for Level 2-4 projects with multiple features requiring product-level c
 
 ### Q: How do I mark a story as done?
 
-**A:** You have two options:
+**A:** After dev-story completes and code-review passes:
 
-**Option 1: Use story-done workflow (Recommended)**
-
-1. Load SM agent
-2. Run `story-done` workflow
-3. Workflow automatically updates `sprint-status.yaml` (created by sprint-planning at Phase 4 start)
-4. Moves story from current status → `DONE`
-5. Advances the story queue
-
-**Option 2: Manual update**
-
-1. After dev-story completes and code-review passes
-2. Open `sprint-status.yaml` (created by sprint-planning)
-3. Change the story status from `review` to `done`
-4. Save the file
-
-The story-done workflow is faster and ensures proper status file updates.
+1. Open `sprint-status.yaml` (created by sprint-planning)
+2. Change the story status from `review` to `done`
+3. Save the file
 
 ### Q: Can I work on multiple stories at once?
 
@@ -371,7 +358,7 @@ See [IDE Setup Guides](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/do
 
 ### Q: Can I customize agents?
 
-**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `{bmad_folder}/_cfg/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
+**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `_bmad/_config/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
 
 **Note:** While source agents in this repo are YAML, they install as `.md` files with XML-style tags - a format any LLM can read and follow.
 

package/src/modules/bmm/docs/glossary.md

@@ -186,12 +186,11 @@ Multi-agent collaboration feature where all installed agents (19+ from BMM, CIS,
 ### Story Status Progression
 
 ```
-backlog → drafted → ready-for-dev → in-progress → review → done
+backlog → ready-for-dev → in-progress → review → done
 ```
 
-- **backlog** - Story exists in epic but not yet drafted
-- **drafted** - Story file created by SM via create-story
-- **ready-for-dev** - Story drafted and reviewed, ready for DEV
+- **backlog** - Story exists in epic but not yet created
+- **ready-for-dev** - Story file created via create-story; validation is optional (run `validate-create-story` for quality check before dev picks it up)
 - **in-progress** - DEV is implementing via dev-story
 - **review** - Implementation complete, awaiting code-review
 - **done** - Completed with DoD met

package/src/modules/bmm/docs/images/README.md

@@ -23,7 +23,7 @@ When you edit `workflow-method-greenfield.excalidraw`, regenerate the SVG:
 After regenerating the SVG, validate that it renders correctly:
 
 ```bash
-./tools/validate-svg-changes.sh src/modules/bmm/docs/images/workflow-method-greenfield.svg
+./tools/validate-svg-changes.sh path/to/workflow-method-greenfield.svg
 ```
 
 This script:

package/src/modules/bmm/docs/images/workflow-method-greenfield.excalidraw

@@ -2934,7 +2934,7 @@
         "gap": 1
       },
       "endBinding": {
-        "elementId": "proc-story-done",
+        "elementId": "proc-code-review",
         "focus": 0.04241833499478815,
         "gap": 1.3466869862454587
       },
@@ -3189,7 +3189,7 @@
       "lineHeight": 1.25
     },
     {
-      "id": "proc-story-done",
+      "id": "proc-code-review",
       "type": "rectangle",
       "x": 1169.3991588878014,
       "y": 947.2529662369525,
@@ -3207,12 +3207,12 @@
         "value": 8
       },
       "groupIds": [
-        "proc-story-done-group"
+        "proc-code-review-group"
       ],
       "boundElements": [
         {
           "type": "text",
-          "id": "proc-story-done-text"
+          "id": "proc-code-review-text"
         },
         {
           "type": "arrow",
@@ -3235,7 +3235,7 @@
       "link": null
     },
     {
-      "id": "proc-story-done-text",
+      "id": "proc-code-review-text",
       "type": "text",
       "x": 1187.9272045420983,
       "y": 972.2529662369525,
@@ -3249,14 +3249,14 @@
       "roughness": 0,
       "opacity": 100,
       "groupIds": [
-        "proc-story-done-group"
+        "proc-code-review-group"
       ],
       "fontSize": 16,
       "fontFamily": 1,
       "text": "Code Review\n<<use different\nLLM>>",
       "textAlign": "center",
       "verticalAlign": "middle",
-      "containerId": "proc-story-done",
+      "containerId": "proc-code-review",
       "locked": false,
       "version": 502,
       "versionNonce": 1242095014,
@@ -3289,7 +3289,7 @@
       "opacity": 100,
       "groupIds": [],
       "startBinding": {
-        "elementId": "proc-story-done",
+        "elementId": "proc-code-review",
         "focus": 0.014488632877232727,
         "gap": 8.284295421831303
       },

package/src/modules/bmm/docs/party-mode.md

@@ -27,7 +27,7 @@ Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent), and su
 
 **The basics:**
 
-1. Party mode reads `{bmad_folder}/_cfg/agent-manifest.csv`
+1. Party mode reads `_bmad/_config/agent-manifest.csv`
 2. Loads ALL installed agents (already includes your customizations from install)
 3. BMad Master orchestrates - picks 2-3 relevant agents per message based on topic
 4. Agents respond in character, can agree/disagree/build on each other's ideas
@@ -126,11 +126,11 @@ _(Multiple perspectives reveal the right answer)_
 
 ## Agent Customization
 
-Party mode uses agents from `{bmad_folder}/[module]/agents/*.md` - these already include any customizations you applied during install.
+Party mode uses agents from `_bmad/[module]/agents/*.md` - these already include any customizations you applied during install.
 
 **To customize agents for party mode:**
 
-1. Create customization file: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
+1. Create customization file: `_bmad/_config/agents/bmm-pm.customize.yaml`
 2. Run `npx bmad-method install` to rebuild agents
 3. Customizations now active in party mode
 

package/src/modules/bmm/docs/quick-flow-solo-dev.md

@@ -1,6 +1,6 @@
 # Quick Flow Solo Dev Agent (Barry)
 
-**Agent ID:** `.bmad/bmm/agents/quick-flow-solo-dev.md`
+**Agent ID:** `_bmad/bmm/agents/quick-flow-solo-dev.md`
 **Icon:** 🚀
 **Module:** BMM
 
@@ -36,25 +36,25 @@ Barry owns the entire BMAD Quick Flow path, providing a streamlined 3-step devel
 
 ### 1. **create-tech-spec**
 
-- **Workflow:** `.bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml`
+- **Workflow:** `_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml`
 - **Description:** Architect a technical spec with implementation-ready stories
 - **Use when:** You need to transform requirements into a buildable spec
 
 ### 2. **quick-dev**
 
-- **Workflow:** `.bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml`
+- **Workflow:** `_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml`
 - **Description:** Ship features from spec or direct instructions - no handoffs
 - **Use when:** You're ready to ship code based on a spec or clear instructions
 
 ### 3. **code-review**
 
-- **Workflow:** `.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml`
+- **Workflow:** `_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml`
 - **Description:** Review code for quality, patterns, and acceptance criteria
 - **Use when:** You need to validate implementation quality
 
 ### 4. **party-mode**
 
-- **Workflow:** `.bmad/core/workflows/party-mode/workflow.yaml`
+- **Workflow:** `_bmad/core/workflows/party-mode/workflow.yaml`
 - **Description:** Bring in other experts when I need specialized backup
 - **Use when:** You need collaborative problem-solving or specialized expertise
 

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

@@ -377,12 +377,6 @@ Checks:
 
 Quick Spec Flow works seamlessly with all Phase 4 implementation workflows:
 
-### story-context (SM Agent)
-
-- ✅ Recognizes tech-spec.md as authoritative source
-- ✅ Extracts context from tech-spec (replaces PRD)
-- ✅ Generates XML context for complex scenarios
-
 ### create-story (SM Agent)
 
 - ✅ Can work with tech-spec.md instead of PRD
@@ -529,10 +523,6 @@ Quick Spec Flow is **fully standalone**:
 
 **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 Quick Flow projects. Only use story-context for complex edge cases.
-
 ### Q: Can I skip validation?
 
 **A:** No, validation always runs automatically. But it's fast and catches issues early!
@@ -564,15 +554,11 @@ Starter templates save hours of setup time. Let Quick Spec Flow find the best on
 
 When validation runs, read the scores. They tell you if your spec is production-ready.
 
-### 5. **Story Context is Optional**
-
-For single changes, try going directly to dev-story first. Only add story-context if you hit complexity.
-
-### 6. **Keep Single Changes Truly Atomic**
+### 5. **Keep Single Changes Truly Atomic**
 
 If your "single change" needs 3+ files, it might be a multi-story feature. Let the workflow guide you.
 
-### 7. **Validate Story Sequence for Multi-Story Features**
+### 6. **Validate Story Sequence for Multi-Story Features**
 
 When you get multiple stories, check the dependency validation output. Proper sequence matters!
 

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

@@ -35,7 +35,7 @@ _Complete visual flowchart showing all phases, workflows, agents (color-coded),
 npx bmad-method@alpha install
 ```
 
-The interactive installer will guide you through setup and create a `{bmad_folder}/` folder with all agents and workflows.
+The interactive installer will guide you through setup and create a `_bmad/` folder with all agents and workflows.
 
 ---
 
@@ -200,12 +200,12 @@ Once planning and architecture are complete, you'll move to Phase 4. **Important
 3. Tell the agent: "Run sprint-planning"
 4. This creates your `sprint-status.yaml` file that tracks all epics and stories
 
-#### 3.2 Draft Your First Story
+#### 3.2 Create Your First Story
 
 1. **Start a new chat** with the **SM agent**
 2. Wait for the menu
 3. Tell the agent: "Run create-story"
-4. This drafts the story file from the epic
+4. This creates the story file from the epic
 
 #### 3.3 Implement the Story