bmad-method 6.0.0-alpha.1 → 6.0.0-alpha.10

package/src/modules/bmb/workflows/create-workflow/README.md

@@ -159,7 +159,7 @@ The brainstorming phase invokes the CIS brainstorming workflow to:
 ### Generated Workflow Folder
 
 Creates a complete workflow folder at:
-`{project-root}/bmad/{{target_module}}/workflows/{{workflow_name}}/`
+`{project-root}/{bmad_folder}/{{target_module}}/workflows/{{workflow_name}}/`
 
 ### Files Created
 
@@ -267,9 +267,9 @@ To modify this workflow:
 
 For issues or questions:
 
-- Review `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
-- Check existing workflows in `/bmad/bmm/workflows/` for examples
-- Validate against `/bmad/bmb/workflows/create-workflow/checklist.md`
+- Review `/{bmad_folder}/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Check existing workflows in `/{bmad_folder}/bmm/workflows/` for examples
+- Validate against `/{bmad_folder}/bmb/workflows/create-workflow/checklist.md`
 - Consult BMAD Method v6 documentation
 
 ---

package/src/modules/bmb/workflows/create-workflow/checklist.md

@@ -61,7 +61,7 @@
 
 - [ ] web_bundle section present if needed
 - [ ] Name, description, author copied from main config
-- [ ] All file paths converted to bmad/-relative format
+- [ ] All file paths converted to {bmad_folder}/-relative format
 - [ ] NO {config_source} variables in web bundle
 - [ ] NO {project-root} prefixes in paths
 - [ ] Instructions path listed correctly

package/src/modules/bmb/workflows/create-workflow/instructions.md

@@ -1,10 +1,11 @@
 # Build Workflow - Workflow Builder Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.yaml</critical>
 <critical>You MUST fully understand the workflow creation guide at: {workflow_creation_guide}</critical>
 <critical>Study the guide thoroughly to follow ALL conventions for optimal human-AI collaboration</critical>
 <critical>Communicate in {communication_language} throughout the workflow creation process</critical>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 
 <workflow>
 
@@ -13,7 +14,7 @@
 
 <action if="user_response == 'y' or user_response == 'yes'">
 Invoke brainstorming workflow to explore ideas and design concepts:
-- Workflow: {project-root}/bmad/core/workflows/brainstorming/workflow.yaml
+- Workflow: {project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml
 - Context data: {installed_path}/brainstorm-context.md
 - Purpose: Generate creative workflow ideas, explore different approaches, and clarify requirements
 
@@ -108,7 +109,8 @@ Most workflows should be `standalone: true` to give users direct access.
 1. **Yes (Recommended)** - Users can run it directly (standalone: true)
 2. **No** - Only called by other workflows/agents (standalone: false)
 
-Most workflows choose option 1:</ask>
+Most workflows choose option 1:
+</ask>
 
 <action>Store {{standalone_setting}} as true or false based on response</action>
 
@@ -150,7 +152,8 @@ The architecture workflow is an excellent example of intent-based with prescript
 2. **Prescriptive** - Structured, consistent, controlled interactions
 3. **Mixed/Balanced** - I'll help you decide step-by-step
 
-What feels right for your workflow's purpose?</ask>
+What feels right for your workflow's purpose?
+</ask>
 
 <action>Store {{instruction_style}} preference</action>
 
@@ -185,11 +188,12 @@ Beyond style, consider **how interactive** this workflow should be:
 
 <ask>What interactivity level suits this workflow?
 
-1. **High** - Highly collaborative, user actively involved throughout
-2. **Medium** - Guided with key decision points (most common)
-3. **Low** - Autonomous with final review
+1. **High** - Highly collaborative, user actively involved throughout (Recommended)
+2. **Medium** - Guided with key decision points
+3. **Low** - Mostly autonomous with final review
 
-Select the level that matches your workflow's purpose:</ask>
+Select the level that matches your workflow's purpose:
+</ask>
 
 <action>Store {{interactivity_level}} preference</action>
 
@@ -252,7 +256,7 @@ Include:
 
 ```yaml
 # Critical variables from config
-config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
+config_source: '{project-root}/{bmad_folder}/{{target_module}}/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
@@ -274,13 +278,13 @@ name: 'workflow-name'
 description: 'Clear purpose statement'
 
 # Paths
-installed_path: '{project-root}/bmad/module/workflows/name'
+installed_path: '{project-root}/{bmad_folder}/module/workflows/name'
 template: '{installed_path}/template.md'
 instructions: '{installed_path}/instructions.md'
 validation: '{installed_path}/checklist.md'
 
 # Critical variables from config
-config_source: '{project-root}/bmad/module/config.yaml'
+config_source: '{project-root}/{bmad_folder}/module/config.yaml'
 output_folder: '{config_source}:output_folder'
 user_name: '{config_source}:user_name'
 communication_language: '{config_source}:communication_language'
@@ -311,7 +315,7 @@ Load and use the template at: {template_instructions}
 Generate the instructions.md file following the workflow creation guide:
 
 1. ALWAYS include critical headers:
-   - Workflow engine reference: {project-root}/bmad/core/tasks/workflow.xml
+   - Workflow engine reference: {project-root}/{bmad_folder}/core/tasks/workflow.xml
    - workflow.yaml reference: must be loaded and processed
 
 2. Structure with <workflow> tags containing all steps
@@ -325,7 +329,7 @@ Generate the instructions.md file following the workflow creation guide:
 
 4. Use proper XML tags from guide:
    - Execution: <action>, <check>, <ask>, <goto>, <invoke-workflow>
-   - Output: <template-output>, <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>, <critical>, <example>
+   - Output: <template-output>, <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>, <critical>, <example>
    - Flow: <loop>, <break>, <continue>
 
 5. Best practices from guide:
@@ -487,6 +491,7 @@ Generate the template.md file following guide conventions:
    # Document Title
 
    **Date:** {{date}}
+
    **Author:** {{user_name}}
    ```
 
@@ -575,7 +580,9 @@ Review the created workflow:
 4. Validate YAML syntax
 5. Confirm all placeholders are replaced
 
-**Standard Config Validation:** 6. Verify workflow.yaml contains standard config block:
+**Standard Config Validation:**
+
+6. Verify workflow.yaml contains standard config block:
 
 - config_source defined
 - output_folder, user_name, communication_language pulled from config
@@ -584,7 +591,9 @@ Review the created workflow:
 7. Check instructions use config variables where appropriate
 8. Verify template includes config variables in metadata (if document workflow)
 
-**YAML/Instruction/Template Alignment:** 9. Cross-check all workflow.yaml variables against instruction usage:
+**YAML/Instruction/Template Alignment:**
+
+9. Cross-check all workflow.yaml variables against instruction usage:
 
 - Are all yaml variables referenced in instructions.md OR template.md?
 - Are there hardcoded values that should be variables?
@@ -608,15 +617,15 @@ If yes:
 
 - Web bundles are self-contained and cannot use config_source variables
 - All files must be explicitly listed in web_bundle_files
-- File paths use bmad/ root (not {project-root})
+- File paths use {bmad_folder}/ root (not {project-root})
 
 <action>Configure web_bundle section in workflow.yaml:</action>
 
 1. Copy core workflow metadata (name, description, author)
-2. Convert all file paths to bmad/-relative paths:
+2. Convert all file paths to {bmad_folder}/-relative paths:
    - Remove {project-root}/ prefix
    - Remove {config_source} references (use hardcoded values)
-   - Example: "{project-root}/bmad/bmm/workflows/x" → "bmad/bmm/workflows/x"
+   - Example: "{project-root}/{bmad_folder}/bmm/workflows/x" → "{bmad_folder}/bmm/workflows/x"
 
 3. List ALL referenced files by scanning:
 
@@ -634,8 +643,8 @@ If yes:
 
    **Critical: Workflow Dependencies**
    - If instructions call another workflow, that workflow's yaml MUST be in web_bundle_files
-   - Example: `<invoke-workflow>{project-root}/bmad/core/workflows/x/workflow.yaml</invoke-workflow>`
-     → Add "bmad/core/workflows/x/workflow.yaml" to web_bundle_files
+   - Example: `<invoke-workflow>{project-root}/{bmad_folder}/core/workflows/x/workflow.yaml</invoke-workflow>`
+     → Add "{bmad_folder}/core/workflows/x/workflow.yaml" to web_bundle_files
 
 4. Create web_bundle_files array with complete list
 
@@ -646,24 +655,24 @@ web_bundle:
   name: '{workflow_name}'
   description: '{workflow_description}'
   author: '{author}'
-  instructions: 'bmad/{module}/workflows/{workflow}/instructions.md'
-  validation: 'bmad/{module}/workflows/{workflow}/checklist.md'
-  template: 'bmad/{module}/workflows/{workflow}/template.md'
+  instructions: '{bmad_folder}/{module}/workflows/{workflow}/instructions.md'
+  validation: '{bmad_folder}/{module}/workflows/{workflow}/checklist.md'
+  template: '{bmad_folder}/{module}/workflows/{workflow}/template.md'
 
   # Any data files (no config_source)
-  data_file: 'bmad/{module}/workflows/{workflow}/data.csv'
+  data_file: '{bmad_folder}/{module}/workflows/{workflow}/data.csv'
 
   web_bundle_files:
-    - 'bmad/{module}/workflows/{workflow}/instructions.md'
-    - 'bmad/{module}/workflows/{workflow}/checklist.md'
-    - 'bmad/{module}/workflows/{workflow}/template.md'
-    - 'bmad/{module}/workflows/{workflow}/data.csv'
+    - '{bmad_folder}/{module}/workflows/{workflow}/instructions.md'
+    - '{bmad_folder}/{module}/workflows/{workflow}/checklist.md'
+    - '{bmad_folder}/{module}/workflows/{workflow}/template.md'
+    - '{bmad_folder}/{module}/workflows/{workflow}/data.csv'
     # Add every single file referenced anywhere
 
   # CRITICAL: If this workflow invokes other workflows, use existing_workflows
   # This signals the bundler to recursively include those workflows' web_bundles
   existing_workflows:
-    - workflow_variable_name: 'bmad/path/to/workflow.yaml'
+    - workflow_variable_name: '{bmad_folder}/path/to/workflow.yaml'
 ```
 
 **Example with existing_workflows:**
@@ -673,14 +682,14 @@ web_bundle:
   name: 'brainstorm-game'
   description: 'Game brainstorming with CIS workflow'
   author: 'BMad'
-  instructions: 'bmad/bmm/workflows/brainstorm-game/instructions.md'
+  instructions: '{bmad_folder}/bmm/workflows/brainstorm-game/instructions.md'
   template: false
   web_bundle_files:
-    - 'bmad/bmm/workflows/brainstorm-game/instructions.md'
-    - 'bmad/mmm/workflows/brainstorm-game/game-context.md'
-    - 'bmad/core/workflows/brainstorming/workflow.yaml'
+    - '{bmad_folder}/bmm/workflows/brainstorm-game/instructions.md'
+    - '{bmad_folder}/mmm/workflows/brainstorm-game/game-context.md'
+    - '{bmad_folder}/core/workflows/brainstorming/workflow.yaml'
   existing_workflows:
-    - core_brainstorming: 'bmad/core/workflows/brainstorming/workflow.yaml'
+    - core_brainstorming: '{bmad_folder}/core/workflows/brainstorming/workflow.yaml'
 ```
 
 **What existing_workflows does:**
@@ -688,13 +697,13 @@ web_bundle:
 - Tells the bundler this workflow invokes another workflow
 - Bundler recursively includes the invoked workflow's entire web_bundle
 - Essential for meta-workflows that orchestrate other workflows
-- Maps workflow variable names to their bmad/-relative paths
+- Maps workflow variable names to their {bmad_folder}/-relative paths
 
 <action>Validate web bundle completeness:</action>
 
 - Ensure no {config_source} variables remain
 - Verify all file paths are listed
-- Check that paths are bmad/-relative
+- Check that paths are {bmad_folder}/-relative
 - If workflow uses <invoke-workflow>, add to existing_workflows
 
 <template-output>web_bundle_config</template-output>

package/src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md

@@ -25,7 +25,7 @@ Create a folder with these files:
 # workflow.yaml (REQUIRED)
 name: 'my-workflow'
 description: 'What this workflow does'
-installed_path: '{project-root}/bmad/module/workflows/my-workflow'
+installed_path: '{project-root}/{bmad_folder}/module/workflows/my-workflow'
 template: '{installed_path}/template.md'
 instructions: '{installed_path}/instructions.md'
 default_output_file: '{output_folder}/output.md'
@@ -44,7 +44,7 @@ standalone: true
 ```markdown
 # instructions.md
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: workflow.yaml</critical>
 
 <workflow>
@@ -61,13 +61,13 @@ That's it! To execute, tell the BMAD agent: `workflow path/to/my-workflow/`
 
 ### Tasks vs Workflows
 
-| Aspect         | Task               | Workflow                |
-| -------------- | ------------------ | ----------------------- |
-| **Purpose**    | Single operation   | Multi-step process      |
-| **Format**     | XML                | Folder with YAML config |
-| **Location**   | `/src/core/tasks/` | `/bmad/*/workflows/`    |
-| **User Input** | Minimal            | Extensive               |
-| **Output**     | Variable           | Usually documents       |
+| Aspect         | Task               | Workflow                      |
+| -------------- | ------------------ | ----------------------------- |
+| **Purpose**    | Single operation   | Multi-step process            |
+| **Format**     | XML                | Folder with YAML config       |
+| **Location**   | `/src/core/tasks/` | `/{bmad_folder}/*/workflows/` |
+| **User Input** | Minimal            | Extensive                     |
+| **Output**     | Variable           | Usually documents             |
 
 ### Workflow Types
 
@@ -104,7 +104,7 @@ name: 'workflow-name'
 description: 'Clear purpose statement'
 
 # Paths
-installed_path: '{project-root}/bmad/module/workflows/name'
+installed_path: '{project-root}/{bmad_folder}/module/workflows/name'
 template: '{installed_path}/template.md' # or false
 instructions: '{installed_path}/instructions.md' # or false
 validation: '{installed_path}/checklist.md' # optional
@@ -641,7 +641,7 @@ the technology stack recommendations. Please choose: web, mobile, or desktop.</a
 ```markdown
 # instructions.md
 
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: workflow.yaml</critical>
 
 <workflow>
@@ -855,7 +855,6 @@ _Generated on {{date}}_
 **Output:**
 
 - `<template-output>` - Save checkpoint
-- `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` - Trigger AI enhancement
 - `<critical>` - Important info
 - `<example>` - Show example
 
@@ -904,7 +903,6 @@ _Generated on {{date}}_
   <step n="2" goal="Define requirements">
     Create functional and non-functional requirements.
     <template-output>requirements</template-output>
-    <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
   </step>
 
   <step n="3" goal="Validate">
@@ -976,6 +974,27 @@ _Generated on {{date}}_
 3. **Set limits** - "3-5 items maximum"
 4. **Explain why** - Context helps AI make better decisions
 
+### Time Estimate Prohibition
+
+**CRITICAL:** For all planning, analysis, and estimation workflows, include this prohibition:
+
+```xml
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
+```
+
+**When to include this:**
+
+- Planning workflows (PRDs, tech specs, architecture)
+- Analysis workflows (research, brainstorming, product briefs)
+- Retrospective workflows (reviews, post-mortems)
+- Any workflow discussing project scope or complexity
+
+**When NOT needed:**
+
+- Pure implementation workflows (code generation, refactoring)
+- Simple action workflows (file operations, status updates)
+- Workflows that only process existing data
+
 ### Conditional Execution Best Practices
 
 **✅ DO:**
@@ -1020,6 +1039,164 @@ _Generated on {{date}}_
 - **Unclosed check tags** - Always close `<check if="">...</check>` blocks
 - **Wrong conditional pattern** - Use `<action if="">` for single items, `<check if="">` for blocks
 
+## Document Sharding Support
+
+If your workflow loads large planning documents (PRDs, epics, architecture, etc.), implement sharding support for efficiency.
+
+### What is Document Sharding?
+
+Document sharding splits large markdown files into smaller section-based files:
+
+- `PRD.md` (50k tokens) → `prd/epic-1.md`, `prd/epic-2.md`, etc.
+- Enables selective loading (90%+ token savings)
+- All BMM workflows support both whole and sharded documents
+
+### When to Add Sharding Support
+
+**Add sharding support if your workflow:**
+
+- Loads planning documents (PRD, epics, architecture, UX specs)
+- May be used in large multi-epic projects
+- Processes documents that could exceed 20k tokens
+- Would benefit from selective section loading
+
+**Skip sharding support if your workflow:**
+
+- Only generates small documents
+- Doesn't load external documents
+- Works with code files (not planning docs)
+
+### Implementation Pattern
+
+#### 1. Add input_file_patterns to workflow.yaml
+
+```yaml
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+input_file_patterns:
+  prd:
+    whole: '{output_folder}/*prd*.md'
+    sharded: '{output_folder}/*prd*/index.md'
+
+  epics:
+    whole: '{output_folder}/*epic*.md'
+    sharded_index: '{output_folder}/*epic*/index.md'
+    sharded_single: '{output_folder}/*epic*/epic-{{epic_num}}.md' # For selective load
+
+  architecture:
+    whole: '{output_folder}/*architecture*.md'
+    sharded: '{output_folder}/*architecture*/index.md'
+
+  document_project:
+    sharded: '{output_folder}/index.md' # Brownfield always uses index
+```
+
+#### 2. Add Discovery Instructions to instructions.md
+
+Place early in instructions (after critical declarations, before workflow steps):
+
+```markdown
+## 📚 Document Discovery
+
+This workflow requires: [list required documents]
+
+**Discovery Process** (execute for each document):
+
+1. **Search for whole document first** - Use fuzzy file matching
+2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
+3. **If sharded version found**:
+   - Read `index.md` to understand the document structure
+   - Read ALL section files listed in the index (or specific sections for selective load)
+   - Treat the combined content as if it were a single document
+4. **Brownfield projects**: The `document-project` workflow creates `{output_folder}/index.md`
+
+**Priority**: If both whole and sharded versions exist, use the whole document.
+
+**Fuzzy matching**: Be flexible with document names - users may use variations.
+```
+
+#### 3. Choose Loading Strategy
+
+**Full Load Strategy** (most workflows):
+
+```xml
+<action>Search for document using fuzzy pattern: {output_folder}/*prd*.md</action>
+<action>If not found, check for sharded version: {output_folder}/*prd*/index.md</action>
+<action if="sharded found">Read index.md to understand structure</action>
+<action if="sharded found">Read ALL section files listed in index</action>
+<action if="sharded found">Combine content as single document</action>
+```
+
+**Selective Load Strategy** (advanced - for phase 4 type workflows):
+
+```xml
+<action>Determine section needed (e.g., epic_num from story key)</action>
+<action>Check for sharded version: {output_folder}/*epics*/index.md</action>
+<action if="sharded found">Read ONLY the specific section file: epics/epic-{{epic_num}}.md</action>
+<action if="sharded found">Skip all other section files (efficiency optimization)</action>
+<action if="whole document found">Load complete document and extract relevant section</action>
+```
+
+### Pattern Examples
+
+**Example 1: Simple Full Load**
+
+```yaml
+# workflow.yaml
+input_file_patterns:
+  requirements:
+    whole: '{output_folder}/*requirements*.md'
+    sharded: '{output_folder}/*requirements*/index.md'
+```
+
+```markdown
+<!-- instructions.md -->
+
+## Document Discovery
+
+Load requirements document (whole or sharded).
+
+1. Try whole: _requirements_.md
+2. If not found, try sharded: _requirements_/index.md
+3. If sharded: Read index + ALL section files
+```
+
+**Example 2: Selective Load with Epic Number**
+
+```yaml
+# workflow.yaml
+input_file_patterns:
+  epics:
+    whole: '{output_folder}/*epic*.md'
+    sharded_single: '{output_folder}/*epic*/epic-{{epic_num}}.md'
+```
+
+```xml
+<!-- instructions.md step -->
+<step n="2" goal="Load Epic Content">
+  <action>Extract epic number from story key (e.g., "3-2-feature" → epic_num = 3)</action>
+  <action>Check for sharded epics: {output_folder}/*epic*/index.md</action>
+  <action if="sharded found">Load ONLY epics/epic-{{epic_num}}.md (selective optimization)</action>
+  <action if="whole document found">Load full epics.md and extract Epic {{epic_num}}</action>
+</step>
+```
+
+### Testing Your Sharding Support
+
+1. **Test with whole document**: Verify workflow works with single `document.md`
+2. **Test with sharded document**: Create sharded version and verify discovery
+3. **Test with both present**: Ensure whole document takes priority
+4. **Test selective loading**: Verify only needed sections are loaded (if applicable)
+
+### Complete Reference
+
+**[→ Document Sharding Guide](../../../../docs/document-sharding-guide.md)** - Comprehensive guide with examples
+
+**BMM Examples**:
+
+- Full Load: `src/modules/bmm/workflows/2-plan-workflows/prd/`
+- Selective Load: `src/modules/bmm/workflows/4-implementation/epic-tech-context/`
+
 ## Web Bundles
 
 Web bundles allow workflows to be deployed as self-contained packages for web environments.
@@ -1036,7 +1213,7 @@ Web bundles allow workflows to be deployed as self-contained packages for web en
 1. **Self-Contained**: No external dependencies
 2. **No Config Variables**: Cannot use `{config_source}` references
 3. **Complete File List**: Every referenced file must be listed
-4. **Relative Paths**: Use `bmad/` root paths (no `{project-root}`)
+4. **Relative Paths**: Use `{bmad_folder}/` root paths (no `{project-root}`)
 
 ### Creating a Web Bundle
 
@@ -1048,20 +1225,20 @@ web_bundle:
   description: 'Workflow description'
   author: 'Your Name'
 
-  # Core files (bmad/-relative paths)
-  instructions: 'bmad/module/workflows/workflow/instructions.md'
-  validation: 'bmad/module/workflows/workflow/checklist.md'
-  template: 'bmad/module/workflows/workflow/template.md'
+  # Core files ({bmad_folder}/-relative paths)
+  instructions: '{bmad_folder}/module/workflows/workflow/instructions.md'
+  validation: '{bmad_folder}/module/workflows/workflow/checklist.md'
+  template: '{bmad_folder}/module/workflows/workflow/template.md'
 
   # Data files (no config_source allowed)
-  data_file: 'bmad/module/workflows/workflow/data.csv'
+  data_file: '{bmad_folder}/module/workflows/workflow/data.csv'
 
   # Complete file list - CRITICAL!
   web_bundle_files:
-    - 'bmad/module/workflows/workflow/instructions.md'
-    - 'bmad/module/workflows/workflow/checklist.md'
-    - 'bmad/module/workflows/workflow/template.md'
-    - 'bmad/module/workflows/workflow/data.csv'
+    - '{bmad_folder}/module/workflows/workflow/instructions.md'
+    - '{bmad_folder}/module/workflows/workflow/checklist.md'
+    - '{bmad_folder}/module/workflows/workflow/template.md'
+    - '{bmad_folder}/module/workflows/workflow/data.csv'
     # Include ALL referenced files
 ```
 
@@ -1069,7 +1246,7 @@ web_bundle:
 
 1. **Remove Config Dependencies**:
    - Replace `{config_source}:variable` with hardcoded values
-   - Convert `{project-root}/bmad/` to `bmad/`
+   - Convert `{project-root}/{bmad_folder}/` to `{bmad_folder}/`
 
 2. **Inventory All Files**:
    - Scan instructions.md for file references
@@ -1078,7 +1255,7 @@ web_bundle:
 
 3. **Test Completeness**:
    - Ensure no missing file references
-   - Verify all paths are relative to bmad/
+   - Verify all paths are relative to {bmad_folder}/
 
 ### Example: Complete Web Bundle
 
@@ -1088,37 +1265,37 @@ web_bundle:
   description: 'Requirements analysis workflow'
   author: 'BMad Team'
 
-  instructions: 'bmad/bmm/workflows/analyze-requirements/instructions.md'
-  validation: 'bmad/bmm/workflows/analyze-requirements/checklist.md'
-  template: 'bmad/bmm/workflows/analyze-requirements/template.md'
+  instructions: '{bmad_folder}/bmm/workflows/analyze-requirements/instructions.md'
+  validation: '{bmad_folder}/bmm/workflows/analyze-requirements/checklist.md'
+  template: '{bmad_folder}/bmm/workflows/analyze-requirements/template.md'
 
   # Data files
-  techniques_data: 'bmad/bmm/workflows/analyze-requirements/techniques.csv'
-  patterns_data: 'bmad/bmm/workflows/analyze-requirements/patterns.json'
+  techniques_data: '{bmad_folder}/bmm/workflows/analyze-requirements/techniques.csv'
+  patterns_data: '{bmad_folder}/bmm/workflows/analyze-requirements/patterns.json'
 
   # Sub-workflow reference
-  validation_workflow: 'bmad/bmm/workflows/validate-requirements/workflow.yaml'
+  validation_workflow: '{bmad_folder}/bmm/workflows/validate-requirements/workflow.yaml'
 
   standalone: true
 
   web_bundle_files:
     # Core workflow files
-    - 'bmad/bmm/workflows/analyze-requirements/instructions.md'
-    - 'bmad/bmm/workflows/analyze-requirements/checklist.md'
-    - 'bmad/bmm/workflows/analyze-requirements/template.md'
+    - '{bmad_folder}/bmm/workflows/analyze-requirements/instructions.md'
+    - '{bmad_folder}/bmm/workflows/analyze-requirements/checklist.md'
+    - '{bmad_folder}/bmm/workflows/analyze-requirements/template.md'
 
     # Data files
-    - 'bmad/bmm/workflows/analyze-requirements/techniques.csv'
-    - 'bmad/bmm/workflows/analyze-requirements/patterns.json'
+    - '{bmad_folder}/bmm/workflows/analyze-requirements/techniques.csv'
+    - '{bmad_folder}/bmm/workflows/analyze-requirements/patterns.json'
 
     # Sub-workflow and its files
-    - 'bmad/bmm/workflows/validate-requirements/workflow.yaml'
-    - 'bmad/bmm/workflows/validate-requirements/instructions.md'
-    - 'bmad/bmm/workflows/validate-requirements/checklist.md'
+    - '{bmad_folder}/bmm/workflows/validate-requirements/workflow.yaml'
+    - '{bmad_folder}/bmm/workflows/validate-requirements/instructions.md'
+    - '{bmad_folder}/bmm/workflows/validate-requirements/checklist.md'
 
     # Shared templates referenced in instructions
-    - 'bmad/bmm/templates/requirement-item.md'
-    - 'bmad/bmm/templates/validation-criteria.md'
+    - '{bmad_folder}/bmm/templates/requirement-item.md'
+    - '{bmad_folder}/bmm/templates/validation-criteria.md'
 ```
 
 ## Troubleshooting
@@ -1147,4 +1324,4 @@ web_bundle:
 _For implementation details, see:_
 
 - `/src/core/tasks/workflow.xml` - Execution engine
-- `/bmad/bmm/workflows/` - Production examples
+- `/{bmad_folder}/bmm/workflows/` - Production examples

package/src/modules/bmb/workflows/create-workflow/workflow-template/instructions.md

@@ -1,9 +1,11 @@
 # PRD Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-related}/bmad/{module-code}/workflows/{workflow}/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-related}/{bmad_folder}/{module-code}/workflows/{workflow}/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the workflow process</critical>
 
+<!-- For planning/analysis workflows, add: <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical> -->
+
 <workflow>
 
 <step n="1" goal="">