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

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md

@@ -15,8 +15,8 @@ targetWorkflowFile: '{target_workflow_path}'
 complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
 
 # Documentation References
-stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/step-template.md'
-workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/workflow-template.md'
+stepTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/step-template.md'
+workflowTemplate: '{project-root}/{bmad_folder}/bmb/docs/workflows/templates/workflow-template.md'
 ---
 
 # Step 8: Comprehensive Compliance Report Generation

package/src/modules/bmb/workflows/workflow-compliance-check/workflow.md

@@ -1,5 +1,5 @@
 ---
-name: Workflow Compliance Check
+name: workflow-compliance-check
 description: Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting
 web_bundle: false
 ---

package/src/modules/bmb/workflows-legacy/edit-module/checklist.md

@@ -24,7 +24,6 @@ Use this checklist to validate module edits meet BMAD Core standards.
 
 ### Optional Fields (if used)
 
-- [ ] custom_agent_location documented
 - [ ] custom_module_location documented
 - [ ] Module-specific fields documented in README
 

package/src/modules/bmgd/README.md

@@ -129,8 +129,9 @@ bmgd/
 │       (Uses BMM workflows via cross-module references)
 ├── templates/
 ├── data/
+├── module.yaml
 └── _module-installer/
-    └── install-config.yaml
+    └── installer.js (optional)
 ```
 
 ## Configuration

package/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md

@@ -140,14 +140,14 @@ I see {{epic_count}} epics with {{story_count}} total stories.
   </check>
 
 <action>Search for relevant starter templates with websearch, examples:
-<WebSearch>{{primary_technology}} starter template CLI create command latest {date}</WebSearch>
-<WebSearch>{{primary_technology}} boilerplate generator latest options</WebSearch>
+Search the web: "{{primary_technology}} starter template CLI create command latest"
+Search the web: "{{primary_technology}} boilerplate generator latest options"
 </action>
 
   <check if="starter_templates_found">
     <action>Investigate what each starter provides:
-      <WebSearch>{{starter_name}} default setup technologies included latest</WebSearch>
-      <WebSearch>{{starter_name}} project structure file organization</WebSearch>
+      Search the web: "{{starter_name}} default setup technologies included latest"
+      Search the web: "{{starter_name}} project structure file organization"
     </action>
 
     <check if="{user_skill_level} == 'expert'">
@@ -176,7 +176,7 @@ I see {{epic_count}} epics with {{story_count}} total stories.
 
     <check if="user_accepts_starter">
       <action>Get current starter command and options:
-        <WebSearch>{{starter_name}} CLI command options flags latest 2024</WebSearch>
+        Search the web: "{{starter_name}} CLI command options flags latest"
       </action>
 
       <action>Document the initialization command:
@@ -282,7 +282,7 @@ Let's work through the remaining {{remaining_count}} decisions."
 
 <step n="4" goal="Facilitate collaborative decision making" repeat="for-each-decision">
   <critical>Each decision must be made WITH the user, not FOR them</critical>
-  <critical>ALWAYS verify current versions using WebSearch - NEVER trust hardcoded versions</critical>
+  <critical>ALWAYS search the web to verify current versions - NEVER trust hardcoded versions</critical>
 
 <action>For each decision in priority order:</action>
 
@@ -327,8 +327,8 @@ Let's work through the remaining {{remaining_count}} decisions."
 
   <check if="decision_involves_specific_technology">
     <action>Verify current stable version:
-      <WebSearch>{{technology}} latest stable version 2024</WebSearch>
-      <WebSearch>{{technology}} current LTS version</WebSearch>
+      Search the web: "{{technology}} latest stable version"
+      Search the web: "{{technology}} current LTS version"
     </action>
 
     <action>Update decision record with verified version:

package/src/modules/bmm/_module-installer/installer.js

@@ -9,7 +9,7 @@ const platformCodes = require(path.join(__dirname, '../../../../tools/cli/lib/pl
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
+ * @param {Object} options.config - Module configuration from module.yaml
  * @param {Array<string>} options.installedIDEs - Array of IDE codes that were installed
  * @param {Object} options.logger - Logger instance for output
  * @returns {Promise<boolean>} - Success status

package/src/modules/bmm/_module-installer/platform-specifics/claude-code.js

@@ -5,7 +5,7 @@ const chalk = require('chalk');
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
+ * @param {Object} options.config - Module configuration from module.yaml
  * @param {Object} options.logger - Logger instance for output
  * @param {Object} options.platformInfo - Platform metadata from global config
  * @returns {Promise<boolean>} - Success status

package/src/modules/bmm/_module-installer/platform-specifics/windsurf.js

@@ -5,7 +5,7 @@ const chalk = require('chalk');
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
+ * @param {Object} options.config - Module configuration from module.yaml
  * @param {Object} options.logger - Logger instance for output
  * @returns {Promise<boolean>} - Success status
  */

package/src/modules/bmm/agents/analyst.agent.yaml

@@ -39,11 +39,14 @@ agent:
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
       description: Document your existing project (optional, but recommended for existing brownfield project efforts)
 
-    - trigger: party-mode
-      exec: "{project-root}/{bmad_folder}/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"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
-      web-only: true
+    - multi: "[SPM] Start Party Mode (optionally suggest attendees and topic), [CH] Chat"
+      triggers:
+        - party-mode:
+            - input: SPM or fuzzy match start party mode
+            - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
+            - data: what is being discussed or suggested with the command, along with custom party custom agents if specified
+            - type: exec
+        - expert-chat:
+            - input: CH or fuzzy match validate agent
+            - action: agent responds as expert based on its personal to converse
+            - type: action

package/src/modules/bmm/agents/architect.agent.yaml

@@ -26,12 +26,8 @@ agent:
       exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.md"
       description: Create an Architecture Document to Guide Development of a PRD (required for BMad Method projects)
 
-    - trigger: validate-architecture
-      validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.yaml"
-      description: Validate Architecture Document (Recommended, use another LLM and fresh context for best results)
-
     - trigger: implementation-readiness
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness/workflow.md"
       description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)
 
     - trigger: create-excalidraw-diagram

package/src/modules/bmm/agents/pm.agent.yaml

@@ -27,14 +27,14 @@ agent:
       exec: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/workflow.md"
       description: Create Product Requirements Document (PRD) (Required for BMad Method flow)
 
-    - trigger: validate-prd
-      validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/workflow.yaml"
-      description: Validate PRD (Highly Recommended, use fresh context and different LLM for best results)
-
     - trigger: create-epics-and-stories
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.yaml"
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
       description: Create Epics and User Stories from PRD (Required for BMad Method flow AFTER the Architecture is completed)
 
+    - trigger: implementation-readiness
+      exec: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness/workflow.md"
+      description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)
+
     - trigger: correct-course
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
       description: Course Correction Analysis (optional during implementation when things go off track)

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

@@ -139,6 +139,9 @@ 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
@@ -146,6 +149,14 @@ 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:
@@ -170,10 +181,21 @@ Quality assurance guidance:
 
 <!-- Test Architect documentation to be added -->
 
+<<<<<<< Updated upstream
+
+<<<<<<< Updated upstream
+
 - Test design workflows
 - Quality gates
 - Risk assessment
-- NFR validation
+- # NFR validation
+  =======
+  > > > > > > > Stashed changes
+  - Test design workflows
+  - Quality gates
+  - Risk assessment
+  - NFR validation
+    > > > > > > > Stashed changes
 
 ---
 

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

@@ -76,8 +76,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 - `create-prd` - Create PRD for Level 2-4 projects (creates FRs/NFRs only)
 - `tech-spec` - Quick spec for Level 0-1 projects
 - `create-epics-and-stories` - Break PRD into implementable pieces (runs AFTER architecture)
-- `validate-prd` - Validate PRD completeness
-- `validate-tech-spec` - Validate Technical Specification
+- `implementation-readiness` - Validate PRD + Architecture + Epics + UX (optional)
 - `correct-course` - Handle mid-project changes
 - `workflow-init` - Initialize workflow tracking
 
@@ -145,8 +144,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 - `workflow-status` - Check what to do next
 - `create-architecture` - Produce a Scale Adaptive Architecture
-- `validate-architecture` - Validate architecture document
-- `implementation-readiness` - Validate readiness for Phase 4
+- `implementation-readiness` - Validate PRD + Architecture + Epics + UX (optional)
 
 **Communication Style:** Comprehensive yet pragmatic. Uses architectural metaphors. Balances technical depth with accessibility. Connects decisions to business value.
 
@@ -182,13 +180,8 @@ 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
-- `epic-tech-context` - Optional epic-specific technical context
-- `validate-epic-tech-context` - Validate epic technical context
 - `create-story` - Draft next story from epic
 - `validate-create-story` - Independent story validation
-- `story-context` - Assemble dynamic technical context XML
-- `validate-story-context` - Validate story context
-- `story-ready-for-dev` - Mark story ready without context generation
 - `epic-retrospective` - Post-epic review
 - `correct-course` - Handle changes during implementation
 
@@ -230,7 +223,6 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
   - Repository docs reference
   - MCP server best practices
   - Web search fallback
-- `story-done` - Mark story complete and advance queue
 
 **Communication Style:** Succinct and checklist-driven. Cites file paths and acceptance criteria IDs. Only asks questions when inputs are missing.
 
@@ -458,7 +450,6 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
 
 - `workflow-status` - Check what to do next
 - `develop-story` - Execute Dev Story workflow, implementing tasks and tests
-- `story-done` - Mark story done after DoD complete
 - `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.
@@ -649,15 +640,11 @@ Some workflows are available to multiple agents:
 
 Many workflows have optional validation workflows that perform independent review:
 
-| Validation                   | Agent       | Validates                        |
-| ---------------------------- | ----------- | -------------------------------- |
-| `validate-prd`               | PM          | PRD completeness (FRs/NFRs only) |
-| `validate-tech-spec`         | PM          | Technical specification quality  |
-| `validate-architecture`      | Architect   | Architecture document            |
-| `validate-design`            | UX Designer | UX specification and artifacts   |
-| `validate-epic-tech-context` | SM          | Epic technical context           |
-| `validate-create-story`      | SM          | Story draft                      |
-| `validate-story-context`     | SM          | Story context XML                |
+| Validation                 | Agent       | Validates                                  |
+| -------------------------- | ----------- | ------------------------------------------ |
+| `implementation-readiness` | Architect   | PRD + Architecture + Epics + UX (optional) |
+| `validate-design`          | UX Designer | UX specification and artifacts             |
+| `validate-create-story`    | SM          | Story draft                                |
 
 **When to use validation:**
 
@@ -912,13 +899,10 @@ Load the customized agent and verify the changes are reflected in its behavior a
 **Story Development Cycle:**
 
 ```
-1. SM: *epic-tech-context (optional, once per epic)
-2. SM: *create-story
-3. SM: *story-context
-4. DEV: *develop-story
-5. DEV: *code-review
-6. DEV: *story-done
-7. Repeat steps 2-6 for next story
+1. SM: *create-story
+2. DEV: *develop-story
+3. DEV: *code-review
+4. Repeat steps 1-3 for next story
 ```
 
 **Testing Strategy:**
@@ -957,9 +941,8 @@ Agent analyzes project state → recommends next workflow
 
 ```
 Each phase has validation gates:
-- Phase 2 to 3: validate-prd, validate-tech-spec
-- Phase 3 to 4: implementation-readiness
-Run validation before advancing
+- Phase 3 to 4: implementation-readiness (validates PRD + Architecture + Epics + UX (optional))
+Run validation before advancing to implementation
 ```
 
 **Course correction:**
@@ -991,13 +974,13 @@ Quick reference for agent selection:
 | **PM**                  | 📋   | 2 (Planning)            | prd, tech-spec, epics-stories                 | Planning, requirements docs             |
 | **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-context  | Story management, sprint coordination   |
-| **DEV**                 | 💻   | 4 (Implementation)      | develop-story, code-review, story-done        | Implementation, coding                  |
+| **SM**                  | 🏃   | 4 (Implementation)      | sprint-planning, create-story                 | Story management, sprint coordination   |
+| **DEV**                 | 💻   | 4 (Implementation)      | develop-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, story-done, code-review        | Game implementation                     |
+| **Game Developer**      | 🕹️   | 4 (Games)               | develop-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              |
 
@@ -1087,10 +1070,8 @@ Quick reference for agent selection:
 
 - [ ] SM: `*sprint-planning` (once)
 - [ ] SM: `*create-story`
-- [ ] SM: `*story-context`
 - [ ] DEV: `*develop-story`
 - [ ] DEV: `*code-review`
-- [ ] DEV: `*story-done`
 
 **Testing Strategy:**
 

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

@@ -250,8 +250,8 @@ Without AI-optimized documentation, workflows fail:
 
 - **tech-spec** (Quick Flow) can't auto-detect stack/patterns → Makes wrong assumptions
 - **PRD** (BMad Method) can't reference existing code → Designs incompatible features
-- **architecture** can't build on existing structure → Suggests conflicting patterns
-- **story-context** can't inject existing patterns → Dev agent rewrites working code
+- **create-architecture** can't build on existing structure → Suggests conflicting patterns
+- **create-story** can't provide existing pattern context → Stories lack integration guidance
 - **dev-story** invents implementations → Breaks existing integrations
 
 ### Key Principle
@@ -320,18 +320,14 @@ See the [Workflows section in BMM README](../README.md) for details.
 ```mermaid
 flowchart TD
     SPRINT[sprint-planning<br/>Initialize tracking]
-    EPIC[epic-tech-context<br/>Per epic]
     CREATE[create-story]
-    CONTEXT[story-context]
     DEV[dev-story]
     REVIEW[code-review]
     CHECK{More stories?}
     RETRO[retrospective<br/>Per epic]
 
-    SPRINT --> EPIC
-    EPIC --> CREATE
-    CREATE --> CONTEXT
-    CONTEXT --> DEV
+    SPRINT --> CREATE
+    CREATE --> DEV
     DEV --> REVIEW
     REVIEW --> CHECK
     CHECK -->|Yes| CREATE
@@ -343,7 +339,7 @@ flowchart TD
 
 **Status Progression:**
 
-- Epic: `backlog → contexted`
+- Epic: `backlog → in-progress → done`
 - Story: `backlog → drafted → ready-for-dev → in-progress → review → done`
 
 **Brownfield-Specific Implementation Tips:**
@@ -351,7 +347,6 @@ flowchart TD
 1. **Respect existing patterns** - Follow established conventions
 2. **Test integration thoroughly** - Validate interactions with existing code
 3. **Use feature flags** - Enable gradual rollout
-4. **Context injection matters** - epic-tech-context and story-context reference existing patterns
 
 ---
 
@@ -375,7 +370,7 @@ When workflow-init asks about your work:
 
 ### 4. Respect Existing Patterns
 
-Tech-spec and story-context will detect conventions. Follow them unless explicitly modernizing.
+Tech-spec and create-story workflows will detect conventions from existing documentation. Follow them unless explicitly modernizing.
 
 ### 5. Plan Integration Points Explicitly
 
@@ -405,13 +400,7 @@ Document in tech-spec/architecture:
 - Context epics before drafting stories
 - Update `sprint-status.yaml` as work progresses
 
-### 9. Leverage Context Injection
-
-- Run `epic-tech-context` before story drafting
-- Always create `story-context` before implementation
-- These reference existing patterns for consistency
-
-### 10. Learn Continuously
+### 9. Learn Continuously
 
 - Run `retrospective` after each epic
 - Incorporate learnings into next stories
@@ -457,7 +446,7 @@ Document in tech-spec/architecture:
    - Analyzes existing auth patterns
    - Confirms conventions
    - Creates tech-spec.md + epic + 3-5 stories
-3. **Implement:** Load SM → `sprint-planning` → `create-story` → `story-context`
+3. **Implement:** Load SM → `sprint-planning` → `create-story`
    Load DEV → `dev-story` for each story
 4. **Review:** Load DEV → `code-review`
 
@@ -479,7 +468,7 @@ Document in tech-spec/architecture:
 4. **Solution:** Load Architect → `create-architecture` → `create-epics-and-stories` → `implementation-readiness`
 5. **Implement:** Sprint-based (10-15 stories)
    - Load SM → `sprint-planning`
-   - Per epic: `epic-tech-context` → stories
+   - Load SM → `create-story` per story
    - Load DEV → `dev-story` per story
 6. **Review:** Per story completion
 
@@ -523,12 +512,9 @@ Document in tech-spec/architecture:
    - `product-brief` - Strategic document
 3. **Plan:** Load PM → `prd` (comprehensive FRs/NFRs)
 4. **Solution:**
-   - `create-architecture` - Full system architecture
-   - `integration-planning` - Phased migration strategy
-   - `create-architecture` - Multi-tenancy architecture
-   - `validate-architecture` - External review
+   - `create-architecture` - Full system architecture including multi-tenancy design
    - `create-epics-and-stories` - Create epics and stories
-   - `implementation-readiness` - Executive approval
+   - `implementation-readiness` - Final validation before implementation
 5. **Implement:** Phased sprint-based (50+ stories)
 
 **Time:** 3-6 months
@@ -575,7 +561,7 @@ Document in tech-spec/architecture:
 **Solution:**
 
 1. Ensure `document-project` captured existing architecture
-2. Check `story-context` - should document integration points
+2. Check story files created by `create-story` - should include integration context
 3. In tech-spec/architecture - explicitly document:
    - Which existing modules to modify
    - What APIs/services to integrate with
@@ -608,7 +594,7 @@ Document in tech-spec/architecture:
 
 1. Check convention detection (Quick Spec Flow should detect patterns)
 2. Review documentation - ensure `document-project` captured patterns
-3. Use `story-context` - injects pattern guidance
+3. Use `create-story` workflow - it loads context from existing documentation
 4. Add to code-review checklist: pattern adherence, convention consistency
 5. Run retrospective to identify deviations early
 
@@ -637,9 +623,9 @@ prd                     # BMad Method/Enterprise tracks
 
 # Phase 3: Solutioning (BMad Method/Enterprise)
 # Architect agent:
-architecture                 # Create/extend architecture
+create-architecture          # Create/extend architecture
 create-epics-and-stories     # Create epics and stories (after architecture)
-implementation-readiness       # Final validation
+implementation-readiness     # Final validation
 
 # Phase 4: Implementation (All Tracks)
 # SM agent:
@@ -739,6 +725,7 @@ flowchart TD
 - **[Quick Start Guide](./quick-start.md)** - Getting started with BMM
 - **[Glossary](./glossary.md)** - Key terminology
 - **[FAQ](./faq.md)** - Common questions
+- **[Troubleshooting](./troubleshooting.md)** - Problem resolution
 - **[Workflow Documentation](./README.md#-workflow-guides)** - Complete workflow reference
 
 ---
@@ -753,7 +740,7 @@ flowchart TD
 
 **Documentation:**
 
-- [Test Architect Guide](./test-architecture.md) - Comprehensive testing strategy
+- **[Test Architect Guide](./test-architecture.md)** - Comprehensive testing strategy
 - [BMM Module README](../README.md) - Complete module and workflow reference
 
 ---

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

@@ -288,8 +288,8 @@ bmad ux *create-ux-design
 
 **BMad ensures:**
 
-- AI agents follow architectural patterns consistently (via story-context)
-- Code standards applied uniformly (via epic-tech-context)
+- AI agents follow architectural patterns consistently
+- Code standards applied uniformly
 - PRD traceability throughout implementation (via acceptance criteria)
 - No "telephone game" between PM, design, and dev
 

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

@@ -90,7 +90,7 @@ When in doubt, start smaller. You can always run create-prd later if needed.
 
 ### Q: Do I always need architecture for Level 2?
 
-**A:** No, architecture is **optional** for Level 2. Only create architecture if you need system-level design. Many Level 2 projects work fine with just PRD + epic-tech-context created during implementation.
+**A:** No, architecture is **optional** for Level 2. Only create architecture if you need system-level design. Many Level 2 projects work fine with just PRD created during planning.
 
 ### Q: What's the difference between Level 1 and Level 2?
 
@@ -147,7 +147,7 @@ If status file exists, use workflow-status. If not, use workflow-init.
 
 ### Q: How do I know when Phase 3 is complete and I can start Phase 4?
 
-**A:** For Level 3-4, run the implementation-readiness workflow. It validates that PRD (FRs/NFRs), architecture, epics+stories, and UX (if applicable) are cohesive before implementation. Pass the gate check = ready for Phase 4.
+**A:** For Level 3-4, run the implementation-readiness workflow. It validates PRD + Architecture + Epics + UX (optional) are aligned before implementation. Pass the gate check = ready for Phase 4.
 
 ### Q: Can I run workflows in parallel or do they have to be sequential?
 
@@ -162,15 +162,6 @@ If status file exists, use workflow-status. If not, use workflow-init.
 
 ## Planning Documents
 
-### Q: What's the difference between tech-spec and epic-tech-context?
-
-**A:**
-
-- **Tech-spec (Level 0-1):** Created upfront in Planning Phase, serves as primary/only planning document, a combination of enough technical and planning information to drive a single or multiple files
-- **Epic-tech-context (Level 2-4):** Created during Implementation Phase per epic, supplements PRD + Architecture
-
-Think of it as: tech-spec is for small projects (replaces PRD and architecture), epic-tech-context is for large projects (supplements PRD).
-
 ### Q: Why no tech-spec at Level 2+?
 
 **A:** Level 2+ projects need product-level planning (PRD) and system-level design (Architecture), which tech-spec doesn't provide. Tech-spec is too narrow for coordinating multiple features. Instead, Level 2-4 uses:
@@ -178,13 +169,6 @@ Think of it as: tech-spec is for small projects (replaces PRD and architecture),
 - PRD (product vision, functional requirements, non-functional requirements)
 - Architecture (system design)
 - Epics+Stories (created AFTER architecture is complete)
-- Epic-tech-context (detailed implementation per epic, created just-in-time)
-
-### Q: When do I create epic-tech-context?
-
-**A:** In Phase 4, right before implementing each epic. Don't create all epic-tech-context upfront - that's over-planning. Create them just-in-time using the epic-tech-context workflow as you're about to start working on that epic.
-
-**Why just-in-time?** You'll learn from earlier epics, and those learnings improve later epic-tech-context.
 
 ### Q: Do I need a PRD for a bug fix?
 
@@ -209,26 +193,9 @@ PRDs are for Level 2-4 projects with multiple features requiring product-level c
 
 ## Implementation
 
-### Q: Do I need story-context for every story?
-
-**A:** Technically no, but it's recommended. story-context provides implementation-specific guidance, references existing patterns, and injects expertise. Skip it only if:
-
-- Very simple story (self-explanatory)
-- You're already expert in the area
-- Time is extremely limited
-
-For Level 0-1 using tech-spec, story-context is less critical because tech-spec is already comprehensive.
-
-### Q: What if I don't create epic-tech-context before drafting stories?
-
-**A:** You can proceed without it, but you'll miss:
-
-- Epic-level technical direction
-- Architecture guidance for this epic
-- Integration strategy with other epics
-- Common patterns to follow across stories
+### Q: Does create-story include implementation context?
 
-epic-tech-context helps ensure stories within an epic are cohesive.
+**A:** Yes! The create-story workflow generates story files that include implementation-specific guidance, references existing patterns from your documentation, and provides technical context. The workflow loads your architecture, PRD, and existing project documentation to create comprehensive stories. For Quick Flow projects using tech-spec, the tech-spec itself is already comprehensive, so stories can be simpler.
 
 ### Q: How do I mark a story as done?
 
@@ -271,7 +238,7 @@ The story-done workflow is faster and ensures proper status file updates.
 - What went well
 - What could improve
 - Technical insights
-- Input for next epic-tech-context
+- Learnings for future epics
 
 Don't wait until project end - run after each epic for continuous improvement.
 
@@ -565,7 +532,7 @@ Trust your expertise - BMM supports your decisions.
 
 ### Q: How do I report a bug or request a feature?
 
-**A:** Open a GitHub issue at: https://github.com/bmad-code-org/BMAD-METHOD/issues
+**A:** Open a GitHub issue at: <https://github.com/bmad-code-org/BMAD-METHOD/issues>
 
 Please include: