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

package/src/modules/bmm/workflows/4-implementation/retrospective/workflow.yaml

@@ -3,43 +3,55 @@ name: "retrospective"
 description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic"
 author: "BMad"
 
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 user_skill_level: "{config_source}:user_skill_level"
 document_output_language: "{config_source}:document_output_language"
 date: system-generated
+sprint_artifacts: "{config_source}:sprint_artifacts"
 
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/retrospective"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective"
 template: false
 instructions: "{installed_path}/instructions.md"
 
-mode: interactive
-trigger: "Run AFTER completing an epic"
-
 required_inputs:
-  - agent_manifest: "{project-root}/bmad/_cfg/agent-manifest.csv"
-
-output_artifacts:
-  - retrospective_summary: "Comprehensive review of what went well and what could improve"
-  - lessons_learned: "Key insights for future epics"
-  - action_items: "Specific improvements with ownership"
-  - next_epic_preparation: "Dependencies, gaps, and preparation tasks for next epic"
-  - critical_path: "Blockers or prerequisites that must be addressed"
-
-facilitation:
-  facilitator: "Bob (Scrum Master)"
-  tone: "Psychological safety - no blame, focus on systems and processes"
-  format: "Two-part: (1) Review completed epic + (2) Preview next epic preparation"
-
-validation_required:
-  - testing_complete: "Has full regression testing been completed?"
-  - deployment_status: "Has epic been deployed to production?"
-  - business_validation: "Have stakeholders reviewed and accepted deliverables?"
-  - technical_health: "Is codebase in stable, maintainable state?"
-  - blocker_resolution: "Any unresolved blockers that will impact next epic?"
+  - agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: SELECTIVE LOAD - only load the completed epic and relevant retrospectives
+input_file_patterns:
+  epics:
+    description: "The completed epic for retrospective"
+    whole: "{output_folder}/*epic*.md"
+    sharded_index: "{output_folder}/*epic*/index.md"
+    sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
+    load_strategy: "SELECTIVE_LOAD"
+  previous_retrospective:
+    description: "Previous epic's retrospective (optional)"
+    pattern: "{sprint_artifacts}/**/epic-{{prev_epic_num}}-retro-*.md"
+    load_strategy: "SELECTIVE_LOAD"
+  architecture:
+    description: "System architecture for context"
+    whole: "{output_folder}/*architecture*.md"
+    sharded: "{output_folder}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
+  prd:
+    description: "Product requirements for context"
+    whole: "{output_folder}/*prd*.md"
+    sharded: "{output_folder}/*prd*/*.md"
+    load_strategy: "FULL_LOAD"
+  document_project:
+    description: "Brownfield project documentation (optional)"
+    sharded: "{output_folder}/*.md"
+    load_strategy: "INDEX_GUIDED"
+
+# Required files
+sprint_status_file: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+story_directory: "{sprint_artifacts}"
+retrospectives_folder: "{sprint_artifacts}"
 
 standalone: true
-
 web_bundle: false

package/src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md

@@ -1,7 +1,24 @@
 # Sprint Planning - Sprint Status Generator
 
-<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/bmm/workflows/4-implementation/sprint-planning/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}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml</critical>
+
+## 📚 Document Discovery - Full Epic Loading
+
+**Strategy**: Sprint planning needs ALL epics and stories to build complete status tracking.
+
+**Epic Discovery Process:**
+
+1. **Search for whole document first** - Look for `epics.md`, `bmm-epics.md`, or any `*epic*.md` file
+2. **Check for sharded version** - If whole document not found, look for `epics/index.md`
+3. **If sharded version found**:
+   - Read `index.md` to understand the document structure
+   - Read ALL epic section files listed in the index (e.g., `epic-1.md`, `epic-2.md`, etc.)
+   - Process all epics and their stories from the combined content
+   - This ensures complete sprint status coverage
+4. **Priority**: If both whole and sharded versions exist, use the whole document
+
+**Fuzzy matching**: Be flexible with document names - users may use variations like `epics.md`, `bmm-epics.md`, `user-stories.md`, etc.
 
 <workflow>
 
@@ -26,6 +43,11 @@
 <action>Build complete inventory of all epics and stories from all epic files</action>
 </step>
 
+  <step n="0.5" goal="Discover and load project documents">
+    <invoke-protocol name="discover_inputs" />
+    <note>After discovery, these content variables are available: {epics_content} (all epics loaded - uses FULL_LOAD strategy)</note>
+  </step>
+
 <step n="2" goal="Build sprint status structure">
 <action>For each epic found, create entries in this order:</action>
 
@@ -124,8 +146,6 @@ development_status:
 ```
 
 <action>Write the complete sprint status YAML to {status_file}</action>
-<action>CRITICAL: For story_location field, write the variable value EXACTLY as defined in workflow.yaml: "{project-root}/docs/stories"</action>
-<action>CRITICAL: Do NOT resolve {project-root} to an absolute path - keep it as the literal string "{project-root}/docs/stories"</action>
 <action>CRITICAL: Metadata appears TWICE - once as comments (#) for documentation, once as YAML key:value fields for parsing</action>
 <action>Ensure all items are ordered: epic, its stories, its retrospective, next epic...</action>
 </step>
@@ -133,10 +153,10 @@ development_status:
 <step n="5" goal="Validate and report">
 <action>Perform validation checks:</action>
 
-- [ ] Every epic in epic files appears in sprint-status.yaml
-- [ ] Every story in epic files appears in sprint-status.yaml
+- [ ] Every epic in epic files appears in {status_file}
+- [ ] Every story in epic files appears in {status_file}
 - [ ] Every epic has a corresponding retrospective entry
-- [ ] No items in sprint-status.yaml that don't exist in epic files
+- [ ] No items in {status_file} that don't exist in epic files
 - [ ] All status values are legal (match state machine definitions)
 - [ ] File is valid YAML syntax
 
@@ -161,7 +181,7 @@ development_status:
 
 **Next Steps:**
 
-1. Review the generated sprint-status.yaml
+1. Review the generated {status_file}
 2. Use this file to track development progress
 3. Agents will update statuses as they work
 4. Re-run this workflow to refresh auto-detected statuses
@@ -212,10 +232,3 @@ optional ↔ completed
 3. **Parallel Work Supported**: Multiple stories can be `in-progress` if team capacity allows
 4. **Review Before Done**: Stories should pass through `review` before `done`
 5. **Learning Transfer**: SM typically drafts next story after previous one is `done` to incorporate learnings
-
-### Error Handling
-
-- If epic file can't be parsed, report specific file and continue with others
-- If existing status file is malformed, backup and regenerate
-- Log warnings for duplicate story IDs across epics
-- Validate status transitions are legal (can't go from `backlog` to `done`)

package/src/modules/bmm/workflows/4-implementation/sprint-planning/sprint-status-template.yaml

@@ -38,7 +38,7 @@ generated: 05-06-2-2025 21:30
 project: My Awesome Project
 project_key: jira-1234
 tracking_system: file-system
-story_location: "{project-root}/docs/stories"
+story_location: "{story_location}"
 
 development_status:
   epic-1: contexted

package/src/modules/bmm/workflows/4-implementation/sprint-planning/workflow.yaml

@@ -3,14 +3,15 @@ description: "Generate and manage the sprint status tracking file for Phase 4 im
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
+sprint_artifacts: "{config_source}:sprint_artifacts"
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/sprint-planning"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning"
 instructions: "{installed_path}/instructions.md"
 template: "{installed_path}/sprint-status-template.yaml"
 validation: "{installed_path}/checklist.md"
@@ -19,19 +20,28 @@ validation: "{installed_path}/checklist.md"
 variables:
   # Project identification
   project_name: "{config_source}:project_name"
-  project_key: "{config_source}:project_name" # Future: Jira project key, Linear workspace ID, etc.
 
   # Tracking system configuration
   tracking_system: "file-system" # Options: file-system, Future will support other options from config of mcp such as jira, linear, trello
-  story_location: "{project-root}/docs/stories" # Relative path for file-system, Future will support URL for Jira/Linear/Trello
-  story_location_absolute: "{config_source}:dev_story_location" # Absolute path for file operations
+  story_location: "{config_source}:sprint_artifacts" # Relative path for file-system, Future will support URL for Jira/Linear/Trello
+  story_location_absolute: "{config_source}:sprint_artifacts" # Absolute path for file operations
 
   # Source files (file-system only)
   epics_location: "{output_folder}" # Directory containing epic*.md files
   epics_pattern: "epic*.md" # Pattern to find epic files
 
   # Output configuration
-  status_file: "{output_folder}/sprint-status.yaml"
+  status_file: "{sprint_artifacts}/sprint-status.yaml"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: FULL LOAD - sprint planning needs ALL epics to build complete status
+input_file_patterns:
+  epics:
+    description: "All epics with user stories"
+    whole: "{output_folder}/*epic*.md"
+    sharded: "{output_folder}/*epic*/*.md"
+    load_strategy: "FULL_LOAD"
 
 # Output configuration
 default_output_file: "{status_file}"

package/src/modules/bmm/workflows/4-implementation/story-context/checklist.md

@@ -1,7 +1,7 @@
 # Story Context Assembly Checklist
 
 ```xml
-<checklist id="bmad/bmm/workflows/4-implementation/story-context/checklist">
+<checklist id="{bmad_folder}/bmm/workflows/4-implementation/story-context/checklist">
   <item>Story fields (asA/iWant/soThat) captured</item>
   <item>Acceptance criteria list matches story draft exactly (no invention)</item>
   <item>Tasks/subtasks captured as task list</item>

package/src/modules/bmm/workflows/4-implementation/story-context/context-template.xml

@@ -1,4 +1,4 @@
-<story-context id="bmad/bmm/workflows/4-implementation/story-context/template" v="1.0">
+<story-context id="{bmad_folder}/bmm/workflows/4-implementation/story-context/template" v="1.0">
   <metadata>
     <epicId>{{epic_id}}</epicId>
     <storyId>{{story_id}}</storyId>

package/src/modules/bmm/workflows/4-implementation/story-context/instructions.md

@@ -1,12 +1,12 @@
 <!-- BMAD BMM Story Context Assembly Instructions (v6) -->
 
 ```xml
-<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: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <critical>Generate all documents in {document_output_language}</critical>
 <critical>This workflow assembles a Story Context file for a single drafted story by extracting acceptance criteria, tasks, relevant docs/code, interfaces, constraints, and testing guidance.</critical>
-<critical>If story_path is provided, use it. Otherwise, find the first story with status "drafted" in sprint-status.yaml. If none found, HALT.</critical>
+<critical>If {story_path} is provided, use it. Otherwise, find the first story with status "drafted" in sprint-status.yaml. If none found, HALT.</critical>
 <critical>Check if context file already exists. If it does, ask user if they want to replace it, verify it, or cancel.</critical>
 
 <critical>DOCUMENT OUTPUT: Technical context file (.context.xml). Concise, structured, project-relative paths only.</critical>
@@ -34,18 +34,17 @@
 
       <check if="no story with status 'drafted' found">
         <output>📋 No drafted stories found in sprint-status.yaml
+          All stories are either still in backlog or already marked ready/in-progress/done.
 
-All stories are either still in backlog or already marked ready/in-progress/done.
-
-**Next Steps:**
-1. Run `create-story` to draft more stories
-2. Run `sprint-planning` to refresh story tracking
+          **Next Steps:**
+          1. Run `create-story` to draft more stories
+          2. Run `sprint-planning` to refresh story tracking
         </output>
         <action>HALT</action>
       </check>
 
       <action>Use the first drafted story found</action>
-      <action>Find matching story file in {{story_dir}} using story_key pattern</action>
+      <action>Find matching story file in {{story_path}} using story_key pattern</action>
       <action>Read the COMPLETE story file</action>
     </check>
 
@@ -61,10 +60,10 @@ All stories are either still in backlog or already marked ready/in-progress/done
     <check if="context file already exists">
       <output>⚠️ Context file already exists: {default_output_file}
 
-**What would you like to do?**
-1. **Replace** - Generate new context file (overwrites existing)
-2. **Verify** - Validate existing context file
-3. **Cancel** - Exit without changes
+        **What would you like to do?**
+        1. **Replace** - Generate new context file (overwrites existing)
+        2. **Verify** - Validate existing context file
+        3. **Cancel** - Exit without changes
       </output>
       <ask>Choose action (replace/verify/cancel):</ask>
 
@@ -89,9 +88,15 @@ All stories are either still in backlog or already marked ready/in-progress/done
     <template-output file="{default_output_file}">so_that</template-output>
   </step>
 
+  <step n="1.5" goal="Discover and load project documents">
+    <invoke-protocol name="discover_inputs" />
+    <note>After discovery, these content variables are available: {prd_content}, {tech_spec_content}, {architecture_content}, {ux_design_content}, {epics_content} (loads only epic for this story if sharded), {document_project_content}</note>
+  </step>
+
   <step n="2" goal="Collect relevant documentation">
-    <action>Scan docs and src module docs for items relevant to this story's domain: search keywords from story title, ACs, and tasks.</action>
-    <action>Prefer authoritative sources: PRD, Architecture, Front-end Spec, Testing standards, module-specific docs.</action>
+    <action>Review loaded content from Step 1.5 for items relevant to this story's domain (use keywords from story title, ACs, and tasks).</action>
+    <action>Extract relevant sections from: {prd_content}, {tech_spec_content}, {architecture_content}, {ux_design_content}, {document_project_content}</action>
+    <action>Note: Tech-Spec ({tech_spec_content}) is used for Level 0-1 projects (instead of PRD). It contains comprehensive technical context, brownfield analysis, framework details, existing patterns, and implementation guidance.</action>
     <action>For each discovered document: convert absolute paths to project-relative format by removing {project-root} prefix. Store only relative paths (e.g., "docs/prd.md" not "/Users/.../docs/prd.md").</action>
     <template-output file="{default_output_file}">
       Add artifacts.docs entries with {path, title, section, snippet}:
@@ -151,7 +156,7 @@ All stories are either still in backlog or already marked ready/in-progress/done
   <step n="6" goal="Validate and save">
     <anchor id="validation_step" />
     <action>Validate output context file structure and content</action>
-    <invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
+    <invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
   </step>
 
   <step n="7" goal="Update story file and mark ready for dev" tag="sprint-status">
@@ -178,12 +183,14 @@ You may need to run sprint-planning to refresh tracking.
     <output>✅ Story context generated successfully, {user_name}!
 
 **Story Details:**
+
 - Story: {{epic_id}}.{{story_id}} - {{story_title}}
 - Story Key: {{story_key}}
 - Context File: {default_output_file}
 - Status: drafted → ready-for-dev
 
 **Context Includes:**
+
 - Documentation artifacts and references
 - Existing code and interfaces
 - Dependencies and frameworks
@@ -191,6 +198,7 @@ You may need to run sprint-planning to refresh tracking.
 - Development constraints
 
 **Next Steps:**
+
 1. Review the context file: {default_output_file}
 2. Run `dev-story` to implement the story
 3. Generate context for more drafted stories if needed

package/src/modules/bmm/workflows/4-implementation/story-context/workflow.yaml

@@ -4,28 +4,59 @@ description: "Assemble a dynamic Story Context XML by pulling latest documentati
 author: "BMad"
 
 # Critical variables
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 document_output_language: "{config_source}:document_output_language"
-story_path: "{config_source}:dev_story_location"
+story_path: "{config_source}:sprint_artifacts/stories"
 date: system-generated
+sprint_artifacts: "{config_source}:sprint_artifacts"
+sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-context"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context"
 template: "{installed_path}/context-template.xml"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 
-# Variables and inputs
-variables:
-  story_path: "" # Optional: Explicit story path. If not provided, finds first story with status "drafted"
-  story_dir: "{config_source}:dev_story_location"
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: SELECTIVE LOAD - only load the specific epic needed for this story
+input_file_patterns:
+  prd:
+    description: "Product requirements (optional)"
+    whole: "{output_folder}/*prd*.md"
+    sharded: "{output_folder}/*prd*/*.md"
+    load_strategy: "FULL_LOAD"
+  tech_spec:
+    description: "Technical specification (Quick Flow track)"
+    whole: "{output_folder}/tech-spec.md"
+    load_strategy: "FULL_LOAD"
+  architecture:
+    description: "System architecture and decisions"
+    whole: "{output_folder}/*architecture*.md"
+    sharded: "{output_folder}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
+  ux_design:
+    description: "UX design specification (if UI)"
+    whole: "{output_folder}/*ux*.md"
+    sharded: "{output_folder}/*ux*/*.md"
+    load_strategy: "FULL_LOAD"
+  epics:
+    description: "Epic containing this story"
+    whole: "{output_folder}/*epic*.md"
+    sharded_index: "{output_folder}/*epic*/index.md"
+    sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
+    load_strategy: "SELECTIVE_LOAD"
+  document_project:
+    description: "Brownfield project documentation (optional)"
+    sharded: "{output_folder}/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 # Output configuration
 # Uses story_key from sprint-status.yaml (e.g., "1-2-user-authentication")
-default_output_file: "{story_dir}/{{story_key}}.context.xml"
+default_output_file: "{story_path}/{{story_key}}.context.xml"
 
 standalone: true
 

package/src/modules/bmm/workflows/4-implementation/story-done/instructions.md

@@ -1,6 +1,6 @@
 # Story Approved Workflow Instructions (DEV Agent)
 
-<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: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 

package/src/modules/bmm/workflows/4-implementation/story-done/workflow.yaml

@@ -4,20 +4,21 @@ description: "Marks a story as done (DoD complete) and moves it from its current
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
+sprint_artifacts: "{config_source}:sprint_artifacts"
+sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-done"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done"
 instructions: "{installed_path}/instructions.md"
 
 # Variables and inputs
 variables:
-  story_path: "" # Explicit path to story file
-  story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
+  story_dir: "{config_source}:sprint_artifacts" # Directory where stories are stored
 
 # Output configuration - no output file, just status updates
 default_output_file: ""

package/src/modules/bmm/workflows/4-implementation/story-ready/instructions.md

@@ -1,6 +1,6 @@
 # Story Ready Workflow Instructions (SM Agent)
 
-<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: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</critical>
@@ -14,12 +14,12 @@
 
 <action>If {{story_path}} is provided → use it directly; extract story_key from filename or metadata; GOTO mark_ready</action>
 
-<critical>MUST read COMPLETE sprint-status.yaml file from start to end to preserve order</critical>
-<action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
+<critical>MUST read COMPLETE {sprint_status} file from start to end to preserve order</critical>
+<action>Load the FULL file: {sprint_status}</action>
 <action>Read ALL lines from beginning to end - do not skip any content</action>
 <action>Parse the development_status section completely</action>
 
-<action>Find ALL stories (reading in order from top to bottom) where:
+<action>Find ALL stories (reading in order from start to end) where:
 
 - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
 - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
@@ -30,7 +30,7 @@
 <action>Count total drafted stories found</action>
 
 <check if="no drafted stories found">
-  <output>📋 No drafted stories found in sprint-status.yaml
+  <output>📋 No drafted stories found in {sprint_status}
 
 All stories are either still in backlog or already marked ready/in-progress/done.
 
@@ -67,7 +67,7 @@ All stories are either still in backlog or already marked ready/in-progress/done
 </step>
 
 <step n="2" goal="Update sprint status to ready-for-dev" tag="sprint-status">
-<action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
+<action>Load the FULL file: {sprint_status}</action>
 <action>Find development_status key matching {{story_key}}</action>
 <action>Verify current status is "drafted" (expected previous state)</action>
 <action>Update development_status[{{story_key}}] = "ready-for-dev"</action>

package/src/modules/bmm/workflows/4-implementation/story-ready/workflow.yaml

@@ -4,23 +4,21 @@ description: "Marks a drafted story as ready for development and moves it from T
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
+sprint_artifacts: "{config_source}:sprint_artifacts"
+sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
 
 # Workflow components
-installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/story-ready"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready"
 instructions: "{installed_path}/instructions.md"
 
 # Variables and inputs
 variables:
-  story_path: "" # Explicit path to story file
-  story_dir: "{config_source}:dev_story_location" # Directory where stories are stored
-
-# Output configuration - no output file, just status updates
-default_output_file: ""
+  story_dir: "{config_source}:sprint_artifacts"
 
 standalone: true
 

package/src/modules/bmm/workflows/document-project/checklist.md

@@ -181,7 +181,7 @@
 
 ### Missing Information (to note for user)
 
-- ***
+-
 
 ## Deep-Dive Mode Validation (if deep-dive was performed)
 

package/src/modules/bmm/workflows/document-project/instructions.md

@@ -1,7 +1,7 @@
 # Document Project Workflow Router
 
-<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/bmm/workflows/document-project/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}/bmm/workflows/document-project/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 
 <workflow>
@@ -10,7 +10,7 @@
 
 <step n="1" goal="Validate workflow and get project info">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+<invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
   <param>mode: data</param>
   <param>data_request: project_config</param>
 </invoke-workflow>
@@ -36,7 +36,7 @@
   </check>
 
   <!-- Now validate sequencing -->
-  <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+  <invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
     <param>mode: validate</param>
     <param>calling_workflow: document-project</param>
   </invoke-workflow>
@@ -179,7 +179,7 @@ Your choice [1/2/3]:
 <step n="4" goal="Update status and complete">
 
 <check if="status_file_found == true">
-  <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
+  <invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/workflow-status">
     <param>mode: update</param>
     <param>action: complete_workflow</param>
     <param>workflow_name: document-project</param>

package/src/modules/bmm/workflows/document-project/workflow.yaml

@@ -5,7 +5,7 @@ description: "Analyzes and documents brownfield projects by scanning codebase, a
 author: "BMad"
 
 # Critical variables
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -14,7 +14,7 @@ user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/document-project"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/document-project"
 template: false # This is an action workflow with multiple output files
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
@@ -22,11 +22,6 @@ validation: "{installed_path}/checklist.md"
 # Required data files - CRITICAL for project type detection and documentation requirements
 documentation_requirements_csv: "{installed_path}/documentation-requirements.csv"
 
-# Optional input - project root to scan (defaults to current working directory)
-recommended_inputs:
-  - project_root: "User will specify or use current directory"
-  - existing_readme: "README.md at project root (if exists)"
-  - project_config: "package.json, go.mod, requirements.txt, etc. (auto-detected)"
 # Output configuration - Multiple files generated in output folder
 # Primary output: {output_folder}/index.md
 # Additional files generated by sub-workflows based on project structure

package/src/modules/bmm/workflows/document-project/workflows/deep-dive-instructions.md

@@ -137,10 +137,10 @@ This will read EVERY file in this area. Proceed? [y/n]
 <action>For each file in file\*inventory, document: - **File Path:** Full path - **Purpose:** What this file does (1-2 sentences) - **Lines of Code:** Total LOC - **Exports:** Complete list with signatures
 
 - Functions: `functionName(param: Type): ReturnType` - Description
-  _ Classes: `ClassName` - Description with key methods
-  _ Types/Interfaces: `TypeName` - Description
-  \_ Constants: `CONSTANT_NAME: Type` - Description - **Imports/Dependencies:** What it uses and why - **Used By:** Files that import this (dependents) - **Key Implementation Details:** Important logic, algorithms, patterns - **State Management:** If applicable (Redux, Context, local state) - **Side Effects:** API calls, database queries, file I/O, external services - **Error Handling:** Try/catch blocks, error boundaries, validation - **Testing:** Associated test files and coverage - **Comments/TODOs:** Any inline documentation or planned work
-  </action>
+  - Classes: `ClassName` - Description with key methods
+  - Types/Interfaces: `TypeName` - Description
+  - Constants: `CONSTANT_NAME: Type` - Description - **Imports/Dependencies:** What it uses and why - **Used By:** Files that import this (dependents) - **Key Implementation Details:** Important logic, algorithms, patterns - **State Management:** If applicable (Redux, Context, local state) - **Side Effects:** API calls, database queries, file I/O, external services - **Error Handling:** Try/catch blocks, error boundaries, validation - **Testing:** Associated test files and coverage - **Comments/TODOs:** Any inline documentation or planned work
+    </action>
 
 <template-output>comprehensive_file_inventory</template-output>
 </step>