diff --git a/src/modules/bmm/workflows/4-implementation/autonomous-epic/README.md b/src/modules/bmm/workflows/4-implementation/autonomous-epic/README.md
index 90467813..714a14c9 100644
--- a/src/modules/bmm/workflows/4-implementation/autonomous-epic/README.md
+++ b/src/modules/bmm/workflows/4-implementation/autonomous-epic/README.md
@@ -431,10 +431,10 @@ Ready to merge
```bash
# In another terminal, watch progress:
-watch -n 10 'cat docs/sprint-artifacts/.autonomous-epic-progress.yaml'
+watch -n 10 'cat _bmad-output/implementation-artifacts/.autonomous-epic-progress.yaml'
# Or tail completion report:
-tail -f docs/sprint-artifacts/epic-2-completion-report.md
+tail -f _bmad-output/implementation-artifacts/epic-2-completion-report.md
```
### 4. Interruption Handling
@@ -630,7 +630,7 @@ Story 3/8: 2-3-password-reset
```bash
# Check progress programmatically:
-cat docs/sprint-artifacts/.autonomous-epic-progress.yaml
+cat _bmad-output/implementation-artifacts/.autonomous-epic-progress.yaml
# Example:
epic_num: 2
@@ -643,7 +643,7 @@ current_story: 2-3-password-reset
```bash
# Generated when epic completes:
-cat docs/sprint-artifacts/epic-2-completion-report.md
+cat _bmad-output/implementation-artifacts/epic-2-completion-report.md
```
## Advanced: Batch Epic Processing
diff --git a/src/modules/bmm/workflows/4-implementation/autonomous-epic/instructions.xml b/src/modules/bmm/workflows/4-implementation/autonomous-epic/instructions.xml
index cbb9461b..fdf572cf 100644
--- a/src/modules/bmm/workflows/4-implementation/autonomous-epic/instructions.xml
+++ b/src/modules/bmm/workflows/4-implementation/autonomous-epic/instructions.xml
@@ -20,6 +20,43 @@
4. Return to this workflow and continue
+
+
+
+ 🚨 WHAT YOLO MODE MEANS:
+ - YOLO mode ONLY means: automatically answer "y", "Y", "C", or "continue" to prompts
+ - YOLO mode does NOT mean: skip steps, skip workflows, skip verification, or produce minimal output
+ - YOLO mode does NOT mean: pretend work was done when it wasn't
+ - ALL steps must still be fully executed - just without waiting for user confirmation
+ - ALL invoke-workflow calls must still be fully executed
+ - ALL verification checks must still pass
+
+
+
+
+
+ 🚨 STORY CREATION IS SACRED - YOU MUST ACTUALLY RUN CREATE-STORY:
+ - DO NOT just output "Creating story..." and move on
+ - DO NOT skip the invoke-workflow tag
+ - DO NOT pretend the story was created
+ - You MUST fully execute the create-story workflow with ALL its steps
+ - The story file MUST exist and be verified BEFORE proceeding
+
+ 🚨 CREATE-STORY QUALITY REQUIREMENTS:
+ - create-story must analyze epics, PRD, architecture, and UX documents
+ - create-story must produce comprehensive story files (4kb+ minimum)
+ - Tiny story files (under 4kb) indicate the workflow was not properly executed
+ - Story files MUST contain: Tasks/Subtasks, Acceptance Criteria, Dev Notes, Architecture Constraints
+
+ 🚨 HARD VERIFICATION REQUIRED AFTER STORY CREATION:
+ - After invoke-workflow for create-story completes, you MUST verify:
+ 1. The story file EXISTS on disk (use file read/check)
+ 2. The story file is AT LEAST 4000 bytes (use wc -c or file size check)
+ 3. The story file contains required sections (Tasks, Acceptance Criteria, Dev Notes)
+ - If ANY verification fails: HALT and report error - do NOT proceed to super-dev-pipeline
+ - Do NOT trust "Story created" output without verification
+
+
@@ -172,27 +219,77 @@
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
+
+
+
-
+
+
+
- Create story just-in-time
+
+ Create story just-in-time - MUST FULLY EXECUTE ALL STEPS
+ This workflow must load epics, PRD, architecture, UX docs
+ This workflow must produce a comprehensive 4kb+ story file
-
+
+ Set {{expected_story_file}} = {{story_dir}}/story-{{epic_num}}.{{story_num}}.md
+ Check if file exists: {{expected_story_file}}
+
+
+
+
+
+ Add to failed_stories with reason: "Story file not created"
+
+
+
+
+ Get file size of {{expected_story_file}} in bytes
+
+
+
+
+
+
+
+
+
+
+ Add to failed_stories with reason: "Story file too small - workflow not properly executed"
+
+
+
+
+ Read {{expected_story_file}} and check for required sections
+
+
+
+
+ Add to failed_stories with reason: "Story file missing required sections"
+
+
+
+
+
+
+
+ Update sprint-status: set {{current_story.key}} to "ready-for-dev" (if not already)
- Add to failed_stories, continue to next
+ Add to failed_stories with error details
+ Update sprint-status: set {{current_story.key}} to "in-progress"
@@ -213,6 +310,7 @@
Log incomplete tasks for reviewMark as partial success
+ Update sprint-status: set {{current_story.key}} to "review"
diff --git a/src/modules/bmm/workflows/4-implementation/autonomous-epic/workflow.yaml b/src/modules/bmm/workflows/4-implementation/autonomous-epic/workflow.yaml
index 30f3ebac..fac0862a 100644
--- a/src/modules/bmm/workflows/4-implementation/autonomous-epic/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/autonomous-epic/workflow.yaml
@@ -46,6 +46,31 @@ super_dev_pipeline_features:
quality_gates: "All super-dev-story gates with disciplined execution"
brownfield_support: "Validates existing code before implementation"
+# YOLO MODE CLARIFICATION
+# YOLO mode ONLY means auto-approve prompts (answer "y", "Y", "C", "continue")
+# YOLO mode does NOT mean: skip steps, skip workflows, or produce minimal output
+# ALL steps, workflows, and verifications must still be fully executed
+yolo_clarification:
+ auto_approve_prompts: true
+ skip_steps: false # NEVER - all steps must execute
+ skip_workflows: false # NEVER - invoke-workflow calls must execute
+ skip_verification: false # NEVER - all checks must pass
+ minimal_output: false # NEVER - full quality output required
+
+# STORY QUALITY REQUIREMENTS
+# These settings ensure create-story produces comprehensive story files
+story_quality_requirements:
+ minimum_size_bytes: 4000 # Story files must be at least 4KB
+ enforce_minimum_size: true
+ required_sections:
+ - "## Tasks"
+ - "## Acceptance Criteria"
+ - "## Dev Notes"
+ - "Architecture Constraints"
+ - "Gap Analysis"
+ halt_on_quality_failure: true # Stop processing if story fails quality check
+ verify_file_exists: true # Verify story file was actually created on disk
+
# TASK-BASED COMPLETION SETTINGS (NEW)
# These settings ensure stories are truly complete, not just marked as such
completion_verification:
@@ -68,5 +93,3 @@ completion_verification:
strict_epic_completion: true
standalone: true
-
-web_bundle: false
diff --git a/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/README.md b/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/README.md
index 1cc40f3c..08f41fa6 100644
--- a/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/README.md
+++ b/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/README.md
@@ -38,7 +38,7 @@ Args: "1.9" (epic.story number)
2. **SCAN codebase systematically** (Glob for files, Read to verify implementation)
3. Generate gap analysis with verified ✅/❌/⚠️ status
4. Update story file with truthful checkboxes
-5. Save to docs/sprint-artifacts/
+5. Save to _bmad-output/implementation-artifacts/
---
diff --git a/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/step-01-initialize.md b/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/step-01-initialize.md
index 2b1c9499..6212924b 100644
--- a/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/step-01-initialize.md
+++ b/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/step-01-initialize.md
@@ -13,7 +13,7 @@ Which story should I regenerate with gap analysis?
Options:
1. Provide story number (e.g., "1.9" or "1-9")
-2. Provide story filename (e.g., "1-9-admin-user-service-bridgeid-rbac.md")
+2. Provide story filename (e.g., "story-1.9.md" or legacy "1-9-admin-user-service-bridgeid-rbac.md")
Your choice:
```
@@ -21,12 +21,14 @@ Your choice:
**Parse input:**
- Extract epic_num (e.g., "1")
- Extract story_num (e.g., "9")
-- Locate story file: `docs/sprint-artifacts/{epic_num}-{story_num}-*.md`
+- Locate story file: `{story_dir}/story-{epic_num}.{story_num}.md` (fallback: `{story_dir}/{epic_num}-{story_num}-*.md`)
### 2. Load Existing Story Content
```bash
-Read: docs/sprint-artifacts/{epic_num}-{story_num}-*.md
+Read: {story_dir}/story-{epic_num}.{story_num}.md
+# If not found, fallback:
+Read: {story_dir}/{epic_num}-{story_num}-*.md
```
**Extract from existing story:**
@@ -40,8 +42,7 @@ Read: docs/sprint-artifacts/{epic_num}-{story_num}-*.md
### 3. Load Epic Context
```bash
-Glob: docs/archive/planning-round-1-greenfield/epics/epic-{epic_num}-*.md
-Read: [found epic file]
+Read: {planning_artifacts}/epics.md
```
**Extract from epic:**
diff --git a/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/step-03-generate-story.md b/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/step-03-generate-story.md
index c0a3a5e9..34281465 100644
--- a/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/step-03-generate-story.md
+++ b/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/step-03-generate-story.md
@@ -8,7 +8,7 @@ Generate complete 7-section story file using verified gap analysis from Step 2.
### 1. Load Template
```bash
-Read: _bmad/custom/workflows/create-story-with-gap-analysis/template.md
+Read: {installed_path}/template.md
```
### 2. Fill Template Variables
@@ -88,7 +88,7 @@ Read: _bmad/custom/workflows/create-story-with-gap-analysis/template.md
**Write filled template:**
```bash
-Write: docs/sprint-artifacts/{{epic_num}}-{{story_num}}-{{slug}}.md
+Write: {story_dir}/story-{{epic_num}}.{{story_num}}.md
[Complete 7-section story with verified gap analysis]
```
@@ -96,28 +96,28 @@ Write: docs/sprint-artifacts/{{epic_num}}-{{story_num}}-{{slug}}.md
```bash
# Check section count
-grep "^## " docs/sprint-artifacts/{{story_file}} | wc -l
+grep "^## " {story_dir}/story-{{epic_num}}.{{story_num}}.md | wc -l
# Should output: 7
# Check for gap analysis
-grep -q "Gap Analysis.*Current State" docs/sprint-artifacts/{{story_file}}
+grep -q "Gap Analysis.*Current State" {story_dir}/story-{{epic_num}}.{{story_num}}.md
# Should find it
# Run custom validation
-./scripts/validate-bmad-format.sh docs/sprint-artifacts/{{story_file}}
+./scripts/validate-bmad-format.sh {story_dir}/story-{{epic_num}}.{{story_num}}.md
# Update script to expect 7 sections + gap analysis subsection
```
### 5. Update Sprint Status
```bash
-Read: docs/sprint-artifacts/sprint-status.yaml
+Read: {sprint_status}
# Find story entry
# Update status to "ready-for-dev" if was "backlog"
# Preserve all comments and structure
-Write: docs/sprint-artifacts/sprint-status.yaml
+Write: {sprint_status}
```
### 6. Report Completion
@@ -126,7 +126,7 @@ Write: docs/sprint-artifacts/sprint-status.yaml
```
✅ Story {{epic_num}}.{{story_num}} Regenerated with Gap Analysis
-File: docs/sprint-artifacts/{{story_file}}
+File: {story_dir}/story-{{epic_num}}.{{story_num}}.md
Sections: 7/7 ✅
Gap Analysis: VERIFIED with codebase scan
diff --git a/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/workflow.yaml b/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/workflow.yaml
index b408bbed..19217943 100644
--- a/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/create-story-with-gap-analysis/workflow.yaml
@@ -7,6 +7,7 @@ config_source: "{project-root}/_bmad/bmm/config.yaml"
user_name: "{config_source}:user_name"
communication_language: "{config_source}:communication_language"
date: system-generated
+planning_artifacts: "{config_source}:planning_artifacts"
implementation_artifacts: "{config_source}:implementation_artifacts"
output_folder: "{implementation_artifacts}"
story_dir: "{implementation_artifacts}"
@@ -19,8 +20,8 @@ instructions: "{installed_path}/step-01-initialize.md"
# Variables and inputs
variables:
sprint_status: "{implementation_artifacts}/sprint-status.yaml"
- epics_file: "{output_folder}/epics.md"
- prd_file: "{output_folder}/PRD.md"
+ epics_file: "{planning_artifacts}/epics.md"
+ prd_file: "{planning_artifacts}/prd.md"
# Project context
project_context: "**/project-context.md"
diff --git a/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml b/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml
index 75d967be..d2554d16 100644
--- a/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml
+++ b/src/modules/bmm/workflows/4-implementation/create-story/instructions.xml
@@ -3,6 +3,11 @@
You MUST have already loaded and processed: {installed_path}/workflow.yamlCommunicate all responses in {communication_language} and generate all documents in {document_output_language}
+ 🚨 YOLO MODE CLARIFICATION: YOLO mode ONLY means auto-approve prompts (answer "y", "Y", "C", "continue").
+ YOLO mode does NOT mean: skip steps, skip sections, skip analysis, or produce minimal output.
+ ALL steps must be fully executed. ALL sections must be populated. The output file must be COMPREHENSIVE (4KB+ minimum).
+ Skipping steps or producing minimal output in YOLO mode is a CRITICAL FAILURE.
+
🔥 CRITICAL MISSION: You are creating the ULTIMATE story context engine that prevents LLM developer mistakes, omissions or
disasters! 🔥Your purpose is NOT to copy from epics - it's to create a comprehensive, optimized story file that gives the DEV agent
@@ -302,6 +307,32 @@
Save file, preserving ALL comments and structure including STATUS DEFINITIONS
+ QUALITY VERIFICATION - Story file must meet minimum requirements before completion
+ Verify story file was created on disk
+
+
+
+ HALT - Story creation failed
+
+
+ Get file size of {{story_file}}
+
+
+
+
+ HALT - Story creation incomplete. Re-run with full analysis.
+
+
+ Verify required sections exist in story file
+
+
+ HALT - Story creation incomplete
+
+
+
+ HALT - Story creation incomplete
+
+
Report completion