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

package/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.yaml

@@ -0,0 +1,63 @@
+# Epic and Story Decomposition Workflow
+name: create-epics-and-stories
+description: "Transform PRD requirements into bite-sized stories organized into deliverable functional epics. This workflow takes a Product Requirements Document (PRD) and breaks it down into epics and user stories that can be easily assigned to development teams. It ensures that all functional requirements are captured in a structured format, making it easier for teams to understand and implement the necessary features."
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+project_name: "{config_source}:project_name"
+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"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+input_file_patterns:
+  prd:
+    description: "Product Requirements Document with FRs and NFRs"
+    whole: "{output_folder}/*prd*.md"
+    sharded: "{output_folder}/*prd*/index.md"
+    load_strategy: "INDEX_GUIDED"
+  product_brief:
+    description: "Product vision and goals (optional)"
+    whole: "{output_folder}/*product*brief*.md"
+    sharded: "{output_folder}/*product*brief*/index.md"
+    load_strategy: "INDEX_GUIDED"
+  domain_brief:
+    description: "Domain-specific requirements and context (optional)"
+    whole: "{output_folder}/*domain*brief*.md"
+    sharded: "{output_folder}/*domain*brief*/index.md"
+    load_strategy: "INDEX_GUIDED"
+  ux_design:
+    description: "UX design specification for interaction patterns (optional)"
+    whole: "{output_folder}/*ux*.md"
+    sharded: "{output_folder}/*ux*/index.md"
+    load_strategy: "FULL_LOAD"
+  architecture:
+    description: "Architecture decisions and technical design (optional)"
+    whole: "{output_folder}/*architecture*.md"
+    sharded: "{output_folder}/*architecture*/index.md"
+    load_strategy: "FULL_LOAD"
+
+# Module path and component files
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories"
+instructions: "{installed_path}/instructions.md"
+template: "{installed_path}/epics-template.md"
+
+# Output configuration
+default_output_file: "{output_folder}/epics.md"
+
+standalone: true
+
+web_bundle:
+  name: "create-epics-and-stories"
+  description: "Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents"
+  author: "BMad"
+  instructions: "{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/instructions.md"
+  template: "{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/epics-template.md"
+  web_bundle_files:
+    - "{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/instructions.md"
+    - "{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/epics-template.md"

package/src/modules/bmm/workflows/3-solutioning/{solutioning-gate-check → implementation-readiness}/checklist.md

@@ -4,10 +4,10 @@
 
 ### Core Planning Documents
 
-- [ ] PRD exists and is complete (Level 2-4 projects)
+- [ ] PRD exists and is complete
 - [ ] PRD contains measurable success criteria
 - [ ] PRD defines clear scope boundaries and exclusions
-- [ ] Architecture document exists (architecture\*.md) (Level 3-4 projects)
+- [ ] Architecture document exists (architecture\*.md)
 - [ ] Technical Specification exists with implementation details
 - [ ] Epic and story breakdown document exists
 - [ ] All documents are dated and versioned
@@ -22,7 +22,7 @@
 
 ## Alignment Verification
 
-### PRD to Architecture Alignment (Level 3-4)
+### PRD to Architecture Alignment
 
 - [ ] Every functional requirement in PRD has architectural support documented
 - [ ] All non-functional requirements from PRD are addressed in architecture
@@ -33,7 +33,7 @@
 - [ ] If architecture.md: All technology choices have verified versions
 - [ ] If UX spec exists: Architecture supports UX requirements
 
-### PRD to Stories Coverage (Level 2-4)
+### PRD to Stories Coverage
 
 - [ ] Every PRD requirement maps to at least one story
 - [ ] All user journeys in PRD have complete story coverage
@@ -154,21 +154,15 @@
 
 ### Critical Issues Found
 
-- [ ] ***
-- [ ] ***
-- [ ] ***
+<!-- checklist of critical issues or N/A -->
 
 ### High Priority Issues Found
 
-- [ ] ***
-- [ ] ***
-- [ ] ***
+<!-- checklist of high priority issues or N/A -->
 
 ### Medium Priority Issues Found
 
-- [ ] ***
-- [ ] ***
-- [ ] ***
+<!-- checklist of medium priority issues or N/A -->
 
 ---
 

package/src/modules/bmm/workflows/3-solutioning/implementation-readiness/instructions.md

@@ -0,0 +1,332 @@
+# Implementation Readiness - Workflow Instructions
+
+<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/3-solutioning/implementation-readiness/workflow.yaml</critical>
+<critical>Communicate all findings and analysis in {communication_language} throughout the assessment</critical>
+<critical>Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically</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>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
+
+<workflow>
+
+<step n="0" goal="Validate workflow readiness" tag="workflow-status">
+<action>Check if {workflow_status_file} exists</action>
+
+<check if="status file not found">
+  <output>No workflow status file found. Implementation Readiness check can run standalone or as part of BMM workflow path.</output>
+  <output>**Recommended:** Run `workflow-init` first for project context tracking and workflow sequencing.</output>
+  <ask>Continue in standalone mode or exit to run workflow-init? (continue/exit)</ask>
+  <check if="continue">
+    <action>Set standalone_mode = true</action>
+  </check>
+  <check if="exit">
+    <action>Exit workflow</action>
+  </check>
+</check>
+
+<check if="status file found">
+  <action>Load the FULL file:  {workflow_status_file}</action>
+  <action>Parse workflow_status section</action>
+  <action>Check status of "implementation-readiness" workflow</action>
+  <action>Get {selected_track} (quick-flow, bmad-method, or enterprise-bmad-method)</action>
+  <action>Find first non-completed workflow (next expected workflow)</action>
+
+<action>Based on the selected_track, understand what artifacts should exist: - quick-flow: Tech spec and simple stories in an epic only (no PRD, minimal solutioning) - bmad-method and enterprise-bmad-method: PRD, UX design, epics/stories, architecture</action>
+
+  <check if="implementation-readiness status is file path (already completed)">
+    <output>⚠️ Implementation readiness check already completed: {{implementation-readiness status}}</output>
+    <ask>Re-running will create a new validation report. Continue? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Use workflow-status to see your next step.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <check if="implementation-readiness is not the next expected workflow">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. Implementation readiness check is out of sequence.</output>
+    <ask>Continue with readiness check anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+<action>Set standalone_mode = false</action>
+</check>
+
+<template-output>project_context</template-output>
+</step>
+
+<step n="0.5" goal="Discover and load input documents">
+<invoke-protocol name="discover_inputs" />
+<note>After discovery, these content variables are available: {prd_content}, {epics_content}, {architecture_content}, {ux_design_content}, {tech_spec_content}, {document_project_content}</note>
+</step>
+
+<step n="1" goal="Inventory loaded project artifacts">
+<action>Review the content loaded by Step 0.5 and create an inventory</action>
+
+<action>Inventory of available documents:
+
+- PRD: {prd_content} (loaded if available)
+- Architecture: {architecture_content} (loaded if available)
+- Epics: {epics_content} (loaded if available)
+- UX Design: {ux_design_content} (loaded if available)
+- Tech Spec: {tech_spec_content} (loaded if available, Quick Flow track)
+- Brownfield docs: {document_project_content} (loaded via INDEX_GUIDED if available)
+  </action>
+
+<action>For each loaded document, extract:
+
+- Document type and purpose
+- Brief description of what it contains
+- Flag any expected documents that are missing as potential issues
+  </action>
+
+<template-output>document_inventory</template-output>
+</step>
+
+<step n="2" goal="Deep analysis of core planning documents">
+<action>Thoroughly analyze each loaded document to extract:
+  - Core requirements and success criteria
+  - Architectural decisions and constraints
+  - Technical implementation approaches
+  - User stories and acceptance criteria
+  - Dependencies and sequencing requirements
+  - Any assumptions or risks documented
+</action>
+
+<action>For PRD analysis, focus on:
+
+- User requirements and use cases
+- Functional and non-functional requirements
+- Success metrics and acceptance criteria
+- Scope boundaries and explicitly excluded items
+- Priority levels for different features
+  </action>
+
+<action>For Architecture/Tech Spec analysis, focus on:
+
+- System design decisions and rationale
+- Technology stack and framework choices
+- Integration points and APIs
+- Data models and storage decisions
+- Security and performance considerations
+- Any architectural constraints that might affect story implementation
+  </action>
+
+<action>For Epic/Story analysis, focus on:
+
+- Coverage of PRD requirements
+- Story sequencing and dependencies
+- Acceptance criteria completeness
+- Technical tasks within stories
+- Estimated complexity and effort indicators
+  </action>
+
+<template-output>document_analysis</template-output>
+</step>
+
+<step n="3" goal="Cross-reference validation and alignment check">
+
+<action>PRD ↔ Architecture Alignment:
+
+- Verify every PRD requirement has corresponding architectural support
+- Check that architectural decisions don't contradict PRD constraints
+- Identify any architectural additions beyond PRD scope (potential gold-plating)
+- Ensure non-functional requirements from PRD are addressed in architecture document
+- If using new architecture workflow: verify implementation patterns are defined
+  </action>
+
+<action>PRD ↔ Stories Coverage:
+
+- Map each PRD requirement to implementing stories
+- Identify any PRD requirements without story coverage
+- Find stories that don't trace back to PRD requirements
+- Validate that story acceptance criteria align with PRD success criteria
+  </action>
+
+<action>Architecture ↔ Stories Implementation Check:
+
+- Verify architectural decisions are reflected in relevant stories
+- Check that story technical tasks align with architectural approach
+- Identify any stories that might violate architectural constraints
+- Ensure infrastructure and setup stories exist for architectural components
+  </action>
+
+<template-output>alignment_validation</template-output>
+</step>
+
+<step n="4" goal="Gap and risk analysis">
+<action>Identify and categorize all gaps, risks, and potential issues discovered during validation</action>
+
+<action>Check for Critical Gaps:
+
+- Missing stories for core requirements
+- Unaddressed architectural concerns
+- Absent infrastructure or setup stories for greenfield projects
+- Missing error handling or edge case coverage
+- Security or compliance requirements not addressed
+  </action>
+
+<action>Identify Sequencing Issues:
+
+- Dependencies not properly ordered
+- Stories that assume components not yet built
+- Parallel work that should be sequential
+- Missing prerequisite technical tasks
+  </action>
+
+<action>Detect Potential Contradictions:
+
+- Conflicts between PRD and architecture approaches
+- Stories with conflicting technical approaches
+- Acceptance criteria that contradict requirements
+- Resource or technology conflicts
+  </action>
+
+<action>Find Gold-Plating and Scope Creep:
+
+- Features in architecture not required by PRD
+- Stories implementing beyond requirements
+- Technical complexity beyond project needs
+- Over-engineering indicators
+  </action>
+
+<action>Check Testability Review (if test-design exists in Phase 3):
+
+**Note:** test-design is recommended for BMad Method, required for Enterprise Method
+
+- Check if {output_folder}/test-design-system.md exists
+- If exists: Review testability assessment (Controllability, Observability, Reliability)
+- If testability concerns documented: Flag for gate decision
+- If missing AND track is Enterprise: Flag as CRITICAL gap
+- If missing AND track is Method: Note as recommendation (not blocker)
+  </action>
+
+<template-output>gap_risk_analysis</template-output>
+</step>
+
+<step n="5" goal="UX and special concerns validation" optional="true">
+  <check if="UX artifacts exist or UX workflow in active path">
+    <action>Review UX artifacts and validate integration:
+      - Check that UX requirements are reflected in PRD
+      - Verify stories include UX implementation tasks
+      - Ensure architecture supports UX requirements (performance, responsiveness)
+      - Identify any UX concerns not addressed in stories
+    </action>
+
+    <action>Validate accessibility and usability coverage:
+      - Check for accessibility requirement coverage in stories
+      - Verify responsive design considerations if applicable
+      - Ensure user flow completeness across stories
+    </action>
+
+  </check>
+
+<template-output>ux_validation</template-output>
+</step>
+
+<step n="6" goal="Generate comprehensive readiness assessment">
+<action>Compile all findings into a structured readiness report with:
+- Executive summary of readiness status
+- Project context and validation scope
+- Document inventory and coverage assessment
+- Detailed findings organized by severity (Critical, High, Medium, Low)
+- Specific recommendations for each issue
+- Overall readiness recommendation (Ready, Ready with Conditions, Not Ready)
+</action>
+
+<action>Provide actionable next steps:
+
+- List any critical issues that must be resolved
+- Suggest specific document updates needed
+- Recommend additional stories or tasks required
+- Propose sequencing adjustments if needed
+  </action>
+
+<action>Include positive findings:
+
+- Highlight well-aligned areas
+- Note particularly thorough documentation
+- Recognize good architectural decisions
+- Commend comprehensive story coverage where found
+  </action>
+
+<template-output>readiness_assessment</template-output>
+</step>
+
+<step n="7" goal="Update status and complete" tag="workflow-status">
+<check if="standalone_mode != true">
+  <action>Load the FULL file: {workflow_status_file}</action>
+  <action>Find workflow_status key "implementation-readiness"</action>
+  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+  <action>Update workflow_status["implementation-readiness"] = "{output_folder}/implementation-readiness-report-{{date}}.md"</action>
+  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+<action>Determine next agent from path file based on next workflow</action>
+</check>
+
+<action>Determine overall readiness status from the readiness_assessment (Ready, Ready with Conditions, or Not Ready)</action>
+
+<output>**✅ Implementation Readiness Check Complete!**
+
+**Assessment Report:**
+
+- Readiness assessment saved to: {output_folder}/implementation-readiness-report-{{date}}.md
+
+{{#if standalone_mode != true}}
+**Status Updated:**
+
+- Progress tracking updated: implementation-readiness marked complete
+- Next workflow: {{next_workflow}}
+  {{else}}
+  **Note:** Running in standalone mode (no progress tracking)
+  {{/if}}
+
+**Next Steps:**
+
+{{#if standalone_mode != true}}
+
+- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
+- Review the assessment report and address any critical issues before proceeding
+
+Check status anytime with: `workflow-status`
+{{else}}
+Since no workflow is in progress:
+
+- Refer to the BMM workflow guide if unsure what to do next
+- Or run `workflow-init` to create a workflow path and get guided next steps
+  {{/if}}
+  </output>
+
+<check if="overall readiness status is Ready OR Ready with Conditions">
+  <output>**🚀 Ready for Implementation!**
+
+Your project artifacts are aligned and complete. You can now proceed to Phase 4: Implementation.
+</output>
+
+<ask>Would you like to run the **sprint-planning** workflow to initialize your sprint tracking and prepare for development? (yes/no)</ask>
+
+  <check if="yes">
+    <action>Inform user that sprint-planning workflow will be invoked</action>
+    <invoke-workflow path="{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml" />
+  </check>
+  <check if="no">
+    <output>You can run sprint-planning later when ready: `sprint-planning`</output>
+  </check>
+</check>
+
+<check if="overall readiness status is Not Ready">
+  <output>**⚠️ Not Ready for Implementation**
+
+Critical issues must be resolved before proceeding. Review the assessment report and address the identified gaps.
+
+Once issues are resolved, re-run implementation-readiness to validate again.
+</output>
+</check>
+
+<template-output>status_update_result</template-output>
+</step>
+
+</workflow>

package/src/modules/bmm/workflows/3-solutioning/{solutioning-gate-check → implementation-readiness}/template.md

@@ -143,4 +143,4 @@ _Minor items for consideration_
 
 ---
 
-_This readiness assessment was generated using the BMad Method Implementation Ready Check workflow (v6-alpha)_
+_This readiness assessment was generated using the BMad Method Implementation Readiness workflow (v6-alpha)_

package/src/modules/bmm/workflows/3-solutioning/implementation-readiness/workflow.yaml

@@ -0,0 +1,64 @@
+# Implementation Readiness - Workflow Configuration
+name: implementation-readiness
+description: "Validate that PRD, UX Design, Architecture, Epics and Stories are complete and aligned before Phase 4 implementation. Ensures all artifacts cover the MVP requirements with no gaps or contradictions."
+author: "BMad"
+
+# Critical variables from config
+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"
+date: system-generated
+
+# Workflow status integration
+workflow_status_workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
+workflow_paths_dir: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/paths"
+workflow_status_file: "{output_folder}/bmm-workflow-status.yaml"
+
+# Module path and component files
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness"
+template: "{installed_path}/template.md"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Output configuration
+default_output_file: "{output_folder}/implementation-readiness-report-{{date}}.md"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: How to load sharded documents (FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED)
+input_file_patterns:
+  prd:
+    description: "Product Requirements with FRs and NFRs"
+    whole: "{output_folder}/*prd*.md"
+    sharded: "{output_folder}/*prd*/index.md"
+    load_strategy: "FULL_LOAD"
+  epics:
+    description: "Epic breakdown with user stories"
+    whole: "{output_folder}/*epic*.md"
+    sharded: "{output_folder}/*epic*/index.md"
+    load_strategy: "FULL_LOAD"
+  architecture:
+    description: "System architecture with decisions and patterns"
+    whole: "{output_folder}/*architecture*.md"
+    sharded: "{output_folder}/*architecture*/index.md"
+    load_strategy: "FULL_LOAD"
+  ux_design:
+    description: "UX design specification (if UI components)"
+    whole: "{output_folder}/*ux*.md"
+    sharded: "{output_folder}/*ux*/index.md"
+    load_strategy: "FULL_LOAD"
+  tech_spec:
+    description: "Technical specification (for Quick Flow track)"
+    whole: "{output_folder}/*tech-spec*.md"
+    sharded: "{output_folder}/*tech-spec*/index.md"
+    load_strategy: "FULL_LOAD"
+  document_project:
+    description: "Brownfield project documentation (optional)"
+    sharded: "{output_folder}/index.md"
+    load_strategy: "INDEX_GUIDED"
+
+standalone: true
+
+web_bundle: false

package/src/modules/bmm/workflows/4-implementation/code-review/instructions.md

@@ -1,7 +1,7 @@
 # Senior Developer Review - Workflow Instructions
 
 ````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} and language MUST be tailored to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</critical>
@@ -23,7 +23,7 @@
       <action>Use {{story_path}} directly</action>
       <action>Read COMPLETE story file and parse sections</action>
       <action>Extract story_key from filename or story metadata</action>
-      <action>Verify Status is "review" - if not, HALT with message: "Story status must be 'review' to proceed"</action>
+      <action>Verify Status is "review" or "ready-for-review" - if not, HALT with message: "Story status must be 'review' or 'ready-for-review' to proceed"</action>
     </check>
 
     <check if="{{story_path}} is NOT provided">
@@ -35,11 +35,11 @@
       <action>Find FIRST story (reading in order from top to bottom) where:
         - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
         - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
-        - Status value equals "review"
+        - Status value equals "review" OR "ready-for-review"
       </action>
 
-      <check if="no story with status 'review' found">
-        <output>📋 No stories with status "review" found
+      <check if="no story with status 'review' or 'ready-for-review' found">
+        <output>📋 No stories with status "review" or "ready-for-review" found
 
 **What would you like to do?**
 1. Run `dev-story` to implement and mark a story ready for review
@@ -51,17 +51,18 @@
         <check if="option 3 selected">
           <ask>What code would you like me to review?
 
-Provide:
-- File path(s) or directory to review
-- What to review for:
-  • General quality and standards
-  • Requirements compliance
-  • Security concerns
-  • Performance issues
-  • Architecture alignment
-  • Something else (specify)
+          Provide:
+          - File path(s) or directory to review
+          - What to review for:
+            • General quality and standards
+            • Requirements compliance
+            • Security concerns
+            • Performance issues
+            • Architecture alignment
+            • Something else (specify)
 
-Your input:</ask>
+            Your input:?
+          </ask>
 
           <action>Parse user input to extract:
             - {{review_files}}: file paths or directories to review
@@ -88,6 +89,11 @@ Your input:</ask>
     <action if="story cannot be read">HALT with message: "Unable to read story file"</action>
   </step>
 
+  <step n="1.5" goal="Discover and load project documents">
+    <invoke-protocol name="discover_inputs" />
+    <note>After discovery, these content variables are available: {architecture_content}, {ux_design_content}, {epics_content} (loads only epic for this story if sharded), {document_project_content}</note>
+  </step>
+
   <step n="2" goal="Resolve story context file and specification inputs">
     <action>Locate story context file: Under Dev Agent Record → Context Reference, read referenced path(s). If missing, search {{output_folder}} for files matching pattern "story-{{epic_num}}.{{story_num}}*.context.xml" and use the most recent.</action>
     <action if="no story context file found">Continue but record a WARNING in review notes: "No story context file found"</action>
@@ -96,6 +102,7 @@ Your input:</ask>
     <action if="no tech spec found">Continue but record a WARNING in review notes: "No Tech Spec found for epic {{epic_num}}"</action>
 
     <action>Load architecture/standards docs: For each file name in {{arch_docs_file_names}} within {{arch_docs_search_dirs}}, read if exists. Collect testing, coding standards, security, and architectural patterns.</action>
+    <note>Architecture and brownfield docs were pre-loaded in Step 1.5 as {architecture_content} and {document_project_content}</note>
   </step>
 
   <step n="3" goal="Detect tech stack and establish best-practice reference set">
@@ -334,11 +341,11 @@ Review was saved to story file, but sprint-status.yaml may be out of sync.
       <action if="user confirms or no ask needed">
         Append under the story's "Tasks / Subtasks" a new subsection titled "Review Follow-ups (AI)", adding each item as an unchecked checkbox in imperative form, prefixed with "[AI-Review]" and severity. Example: "- [ ] [AI-Review][High] Add input validation on server route /api/x (AC #2)".
       </action>
-      <action if="{{persist_action_items}} == true and 'backlog_file' in {{persist_targets}}">
+      <action>
         If {{backlog_file}} does not exist, copy {installed_path}/backlog_template.md to {{backlog_file}} location.
         Append a row per action item with Date={{date}}, Story={{epic_num}}.{{story_num}}, Epic={{epic_num}}, Type, Severity, Owner (or "TBD"), Status="Open", Notes with short context and file refs.
       </action>
-      <action if="{{persist_action_items}} == true and ('epic_followups' in {{persist_targets}} or {{update_epic_followups}} == true)">
+      <action>
         If an epic Tech Spec was found: open it and create (if missing) a section titled "{{epic_followups_section_title}}". Append a bullet list of action items scoped to this epic with references back to Story {{epic_num}}.{{story_num}}.
       </action>
       <action>Save modified files.</action>
@@ -347,7 +354,7 @@ Review was saved to story file, but sprint-status.yaml may be out of sync.
   </step>
 
   <step n="10" goal="Validation and completion">
-    <invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/bmad/core/tasks/validate-workflow.xml</invoke-task>
+    <invoke-task>Run validation checklist at {installed_path}/checklist.md using {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
     <action>Report workflow completion.</action>
 
     <check if="ad_hoc_review_mode == true">