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

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

@@ -2,113 +2,137 @@
 
 <workflow name="architecture">
 
-<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>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
 <critical>The goal is ARCHITECTURAL DECISIONS that prevent AI agent conflicts, not detailed implementation specs</critical>
 <critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</critical>
 <critical>This workflow replaces architecture with a conversation-driven approach</critical>
-
-<step n="0" goal="Validate workflow and extract project configuration">
-
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-  <param>mode: data</param>
-  <param>data_request: project_config</param>
-</invoke-workflow>
-
-<check if="status_exists == false">
-  <output>**Note: No Workflow Status File Found**
-
-The Decision Architecture workflow can run standalone or as part of the BMM workflow path.
-
-**Recommended:** Run `workflow-init` first for:
-
-- Project context tracking
-- Workflow sequencing guidance
-- Progress monitoring across workflows
-
-**Or continue standalone** without progress tracking.
-</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>
+<critical>Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically</critical>
+<critical>ELICITATION POINTS: After completing each major architectural decision area (identified by template-output tags for decision_record, project_structure, novel_pattern_designs, implementation_patterns, and architecture_document), invoke advanced elicitation to refine decisions before proceeding</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>
+
+<step n="0" goal="Validate workflow readiness" tag="workflow-status">
+<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
+
+<check if="status file not found">
+  <output>No workflow status file found. Create Architecture 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_exists == true">
-  <action>Store {{status_file_path}} for later updates</action>
-
-  <check if="project_level < 3">
-    <output>**Note: Level {{project_level}} Project**
-
-Decision Architecture is typically for Level 3-4 projects, but can be used for any project that needs architectural planning.
-
-For Level {{project_level}}, we'll keep the architecture appropriately scoped.
-</output>
-</check>
+<check if="status file found">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Parse workflow_status section</action>
+  <action>Check status of "create-architecture" workflow</action>
+  <action>Get project_level from YAML metadata</action>
+  <action>Find first non-completed workflow (next expected workflow)</action>
 </check>
-</step>
-
-<step n="0.5" goal="Validate workflow sequencing">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-  <param>mode: validate</param>
-  <param>calling_workflow: architecture</param>
-</invoke-workflow>
+  <check if="create-architecture status is indicates already completed">
+    <output>⚠️ Architecture already completed: {{create-architecture status}}</output>
+    <ask>Re-running will overwrite the existing architecture. 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="warning != ''">
-  <output>{{warning}}</output>
-  <ask>Continue with Decision Architecture anyway? (y/n)</ask>
-  <check if="n">
-    <output>{{suggestion}}</output>
-    <action>Exit workflow</action>
+  <check if="create-architecture is not the next expected workflow">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. Architecture is out of sequence.</output>
+    <ask>Continue with Architecture anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
   </check>
-</check>
 
-<action>Check for existing PRD and epics files using fuzzy matching</action>
+<action>Set standalone_mode = false</action>
+
+<action>Check for existing PRD file using fuzzy matching</action>
 
 <action>Fuzzy match PRD file: {prd_file}</action>
 <check if="PRD_not_found">
 <output>**PRD Not Found**
 
-Decision Architecture works from your Product Requirements Document (PRD).
+Creation of an Architecture works from your Product Requirements Document (PRD), along with an optional UX Design and other assets.
 
-Looking for: bmm-PRD.md, PRD.md, or product-requirements.md in {output_folder}
+Looking for: _prd_.md, or prd/\* + files in {output_folder}
 
-Please run the PRD workflow first to define your requirements.
-
-Run: `workflow prd`
+Please talk to the PM Agent to run the Create PRD workflow first to define your requirements, or if I am mistaken and it does exist, provide the file now.
 </output>
-<action>Exit workflow - PRD required</action>
+<ask>Would you like to exit, or can you provide a PRD?
+<action if='yes to exit'>Exit workflow - PRD required</action>
+<action if='prd provided'>Proceed to Step 1</action>
+</ask>
 </check>
 
 </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}, {ux_design_content}, {document_project_content}</note>
+</step>
+
 <step n="1" goal="Load and understand project context">
-  <action>Load the PRD using fuzzy matching: {prd_file}</action>
-  <action>Load epics file using fuzzy matching: {epics_file}</action>
+  <action>Review loaded PRD: {prd_content} (auto-loaded in Step 0.5 - handles both whole and sharded documents)</action>
 
-<action>Check for UX specification using fuzzy matching:
-<action>Attempt to locate: {ux_spec_file}</action>
-<check if="ux_spec_found">
-<action>Load UX spec and extract architectural implications: - Component complexity (simple forms vs rich interactions) - Animation/transition requirements - Real-time update needs (live data, collaborative features) - Platform-specific UI requirements - Accessibility standards (WCAG compliance level) - Responsive design breakpoints - Offline capability requirements - Performance expectations (load times, interaction responsiveness)
+  <check if="{epics_content} is not empty">
+    <action>Review loaded epics: {epics_content}</action>
+  </check>
+
+<action>Check for UX specification:
+<check if="{ux_design_content} is not empty">
+<action>Extract architectural implications from {ux_design_content}: - Component complexity (simple forms vs rich interactions) - Animation/transition requirements - Real-time update needs (live data, collaborative features) - Platform-specific UI requirements - Accessibility standards (WCAG compliance level) - Responsive design breakpoints - Offline capability requirements - Performance expectations (load times, interaction responsiveness)
 </action>
 </check>
 </action>
 
-<action>Extract and understand from PRD: - Functional Requirements (what it must do) - Non-Functional Requirements (performance, security, compliance, etc.) - Epic structure and user stories - Acceptance criteria - Any technical constraints mentioned
-</action>
+<action>Extract and understand from {prd_content}:
 
-<action>Count and assess project scale: - Number of epics: {{epic_count}} - Number of stories: {{story_count}} - Complexity indicators (real-time, multi-tenant, regulated, etc.) - UX complexity level (if UX spec exists)
-</action>
+- Functional Requirements (FRs) - the complete list of capabilities
+- Non-Functional Requirements (performance, security, compliance, etc.)
+- Any technical constraints mentioned
+  </action>
+
+<check if="{epics_content} is not empty">
+  <action>Extract from {epics_content}:
+  - Epic structure and user stories
+  - Acceptance criteria
+  </action>
+</check>
+
+<action>Count and assess project scale:
+<check if="{epics_content} is not empty">
+
+- Number of epics: {{epic_count}}
+- Number of stories: {{story_count}}
+  </check>
+  <check if="{epics_content} is empty">
+- Number of functional requirements: {{fr_count}} (from PRD)
+- FR categories: {{fr_category_list}} (capability groups from PRD)
+  </check>
+- Complexity indicators (real-time, multi-tenant, regulated, etc.)
+- UX complexity level (if UX spec exists)
+- Novel features
+  </action>
 
 <action>Reflect understanding back to {user_name}:
 "I'm reviewing your project documentation for {{project_name}}.
+<check if="{epics_content} is not empty">
 I see {{epic_count}} epics with {{story_count}} total stories.
+</check>
+<check if="{epics_content} is empty">
+I found {{fr_count}} functional requirements organized into {{fr_category_list}}.
+</check>
 {{if_ux_spec}}I also found your UX specification which defines the user experience requirements.{{/if_ux_spec}}
 
      Key aspects I notice:
@@ -142,8 +166,8 @@ I see {{epic_count}} epics with {{story_count}} total stories.
     </action>
   </check>
 
-<action>Search for relevant starter templates:
-<WebSearch>{{primary_technology}} starter template CLI create command latest 2024</WebSearch>
+<action>Search for relevant starter templates with websearch, examples:
+<WebSearch>{{primary_technology}} starter template CLI create command latest {date}</WebSearch>
 <WebSearch>{{primary_technology}} boilerplate generator latest options</WebSearch>
 </action>
 
@@ -213,7 +237,7 @@ I see {{epic_count}} epics with {{story_count}} total stories.
 
   <check if="no_starter_found_or_applicable">
     <action>Note: No standard starter template found for this project type.
-            Will need to make all architectural decisions explicitly.</action>
+            We will make all architectural decisions explicitly.</action>
   </check>
 
 <template-output>starter_template_decision</template-output>
@@ -292,34 +316,39 @@ Let's work through the remaining {{remaining_count}} decisions."
 <action>Present the decision based on mode:
 <check if="mode == 'EXPERT'">
 "{{Decision_Category}}: {{Specific_Decision}}
-Options: {{concise_option_list_with_tradeoffs}}
-Recommendation: {{recommendation}} for {{reason}}"
-</check>
 
-    <check if="mode == 'INTERMEDIATE'">
-      "Next decision: {{Human_Friendly_Category}}
+    Options: {{concise_option_list_with_tradeoffs}}
+
+    Recommendation: {{recommendation}} for {{reason}}"
 
-       We need to choose {{Specific_Decision}}.
+  </check>
 
-       Common options:
-       {{option_list_with_brief_explanations}}
+  <check if="mode == 'INTERMEDIATE'">
+    "Next decision: {{Human_Friendly_Category}}
 
-       For your project, {{recommendation}} would work well because {{reason}}."
-    </check>
+      We need to choose {{Specific_Decision}}.
 
-    <check if="mode == 'BEGINNER'">
-      "Let's talk about {{Human_Friendly_Category}}.
+      Common options:
+      {{option_list_with_brief_explanations}}
 
-       {{Educational_Context_About_Why_This_Matters}}
+      For your project, {{recommendation}} would work well because {{reason}}."
 
-       Think of it like {{real_world_analogy}}.
+  </check>
 
-       Your main options:
-       {{friendly_options_with_pros_cons}}
+  <check if="mode == 'BEGINNER'">
+    "Let's talk about {{Human_Friendly_Category}}.
 
-       My suggestion: {{recommendation}}
-       This is good for you because {{beginner_friendly_reason}}."
-    </check>
+      {{Educational_Context_About_Why_This_Matters}}
+
+      Think of it like {{real_world_analogy}}.
+
+      Your main options:
+      {{friendly_options_with_pros_cons}}
+
+      My suggestion: {{recommendation}}
+      This is good for you because {{beginner_friendly_reason}}."
+
+  </check>
 
   </action>
 
@@ -353,7 +382,12 @@ Recommendation: {{recommendation}} for {{reason}}"
 Category: {{category}}
 Decision: {{user_choice}}
 Version: {{verified_version_if_applicable}}
+<check if="{epics_content} is not empty">
 Affects Epics: {{list_of_affected_epics}}
+</check>
+<check if="{epics_content} is empty">
+Affects FR Categories: {{list_of_affected_fr_categories}}
+</check>
 Rationale: {{user_reasoning_or_default}}
 Provided by Starter: {{yes_if_from_starter}}
 </action>
@@ -372,11 +406,7 @@ Provided by Starter: {{yes_if_from_starter}}
 </action>
 
   <check if="{user_skill_level} == 'beginner'">
-    <action>Explain why these matter:
-      "These are rules that EVERY part of your app must follow.
-       If we don't decide now, each AI agent will do it differently,
-       and your app won't work properly when the pieces come together."
-    </action>
+    <action>Explain why these matter why its critical to go through and decide these things now.</action>
   </check>
 
 <template-output>cross_cutting_decisions</template-output>
@@ -388,9 +418,16 @@ Provided by Starter: {{yes_if_from_starter}}
 <action>Create comprehensive source tree: - Root configuration files - Source code organization - Test file locations - Build/dist directories - Documentation structure
 </action>
 
-<action>Map epics to architectural boundaries:
-"Epic: {{epic_name}} → Lives in {{module/directory/service}}"
-</action>
+<check if="{epics_content} is not empty">
+  <action>Map epics to architectural boundaries:
+  "Epic: {{epic_name}} → Lives in {{module/directory/service}}"
+  </action>
+</check>
+<check if="{epics_content} is empty">
+  <action>Map FR categories to architectural boundaries:
+  "FR Category: {{fr_category_name}} → Lives in {{module/directory/service}}"
+  </action>
+</check>
 
 <action>Define integration points: - Where do components communicate? - What are the API boundaries? - How do services interact?
 </action>
@@ -401,15 +438,22 @@ Provided by Starter: {{yes_if_from_starter}}
 <step n="7" goal="Design novel architectural patterns" optional="true">
   <critical>Some projects require INVENTING new patterns, not just choosing existing ones</critical>
 
-<action>Scan PRD for concepts that don't have standard solutions: - Novel interaction patterns (e.g., "swipe to match" before Tinder existed) - Unique multi-component workflows (e.g., "viral invitation system") - New data relationships (e.g., "social graph" before Facebook) - Unprecedented user experiences (e.g., "ephemeral messages" before Snapchat) - Complex state machines crossing multiple epics
-</action>
+<action>Scan PRD for concepts that don't have standard solutions: - Novel interaction patterns (e.g., "swipe to match" before Tinder existed) - Unique multi-component workflows (e.g., "viral invitation system") - New data relationships (e.g., "social graph" before Facebook) - Unprecedented user experiences (e.g., "ephemeral messages" before Snapchat)
+<check if="{epics_content} is not empty">
+
+- Complex state machines crossing multiple epics
+  </check>
+  <check if="{epics_content} is empty">
+- Complex state machines crossing multiple FR categories
+  </check>
+  </action>
 
   <check if="novel_patterns_detected">
     <action>For each novel pattern identified:</action>
 
-    <action>Engage user in design collaboration:
-      <check if="{user_skill_level} == 'expert'">
-        "The {{pattern_name}} concept requires architectural innovation.
+  <action>Engage user in design collaboration:
+  <check if="{user_skill_level} == 'expert'">
+  "The {{pattern_name}} concept requires architectural innovation.
 
          Core challenge: {{challenge_description}}
 
@@ -423,39 +467,44 @@ Provided by Starter: {{yes_if_from_starter}}
 
          Let me help you think through how this should work:"
       </check>
-    </action>
 
-    <action>Facilitate pattern design:
-      1. Identify core components involved
-      2. Map data flow between components
-      3. Design state management approach
-      4. Create sequence diagrams for complex flows
-      5. Define API contracts for the pattern
-      6. Consider edge cases and failure modes
     </action>
 
-    <action>Use advanced elicitation for innovation:
-      "What if we approached this differently?
-       - What would the ideal user experience look like?
-       - Are there analogies from other domains we could apply?
-       - What constraints can we challenge?"
-    </action>
+  <action>Facilitate pattern design: 1. Identify core components involved 2. Map data flow between components 3. Design state management approach 4. Create sequence diagrams for complex flows 5. Define API contracts for the pattern 6. Consider edge cases and failure modes
+  </action>
+
+  <action>Use advanced elicitation for innovation:
+  "What if we approached this differently? - What would the ideal user experience look like? - Are there analogies from other domains we could apply? - What constraints can we challenge?"
+  </action>
 
-    <action>Document the novel pattern:
-      Pattern Name: {{pattern_name}}
-      Purpose: {{what_problem_it_solves}}
-      Components:
-        {{component_list_with_responsibilities}}
-      Data Flow:
-        {{sequence_description_or_diagram}}
-      Implementation Guide:
-        {{how_agents_should_build_this}}
+  <action>Document the novel pattern:
+  Pattern Name: {{pattern_name}}
+  Purpose: {{what_problem_it_solves}}
+  Components:
+  {{component_list_with_responsibilities}}
+  Data Flow:
+  {{sequence_description_or_diagram}}
+  Implementation Guide:
+  {{how_agents_should_build_this}}
+
+<check if="{epics_content} is not empty">
       Affects Epics:
         {{epics_that_use_this_pattern}}
+</check>
+<check if="{epics_content} is empty">
+      Affects FR Categories:
+        {{fr_categories_that_use_this_pattern}}
+</check>
     </action>
 
     <action>Validate pattern completeness:
+
+<check if="{epics_content} is not empty">
       "Does this {{pattern_name}} design cover all the use cases in your epics?
+</check>
+<check if="{epics_content} is empty">
+      "Does this {{pattern_name}} design cover all the use cases in your requirements?
+</check>
        - {{use_case_1}}: ✓ Handled by {{component}}
        - {{use_case_2}}: ✓ Handled by {{component}}
        ..."
@@ -569,8 +618,14 @@ Enforcement: "All agents MUST follow this pattern"
 <action>Check decision compatibility: - Do all decisions work together? - Are there any conflicting choices? - Do the versions align properly?
 </action>
 
-<action>Verify epic coverage: - Does every epic have architectural support? - Are all user stories implementable with these decisions? - Are there any gaps?
-</action>
+<check if="{epics_content} is not empty">
+  <action>Verify epic coverage: - Does every epic have architectural support? - Are all user stories implementable with these decisions? - Are there any gaps?
+  </action>
+</check>
+<check if="{epics_content} is empty">
+  <action>Verify FR coverage: - Does every functional requirement have architectural support? - Are all capabilities implementable with these decisions? - Are there any gaps?
+  </action>
+</check>
 
 <action>Validate pattern completeness: - Are there any patterns we missed that agents would need? - Do novel patterns integrate with standard architecture? - Are implementation patterns comprehensive enough?
 </action>
@@ -593,7 +648,11 @@ Enforcement: "All agents MUST follow this pattern"
 
 <action>Load template: {architecture_template}</action>
 
-<action>Generate sections: 1. Executive Summary (2-3 sentences about the architecture approach) 2. Project Initialization (starter command if applicable) 3. Decision Summary Table (with verified versions and epic mapping) 4. Complete Project Structure (full tree, no placeholders) 5. Epic to Architecture Mapping (every epic placed) 6. Technology Stack Details (versions, configurations) 7. Integration Points (how components connect) 8. Novel Pattern Designs (if any were created) 9. Implementation Patterns (all consistency rules) 10. Consistency Rules (naming, organization, formats) 11. Data Architecture (models and relationships) 12. API Contracts (request/response formats) 13. Security Architecture (auth, authorization, data protection) 14. Performance Considerations (from NFRs) 15. Deployment Architecture (where and how) 16. Development Environment (setup and prerequisites) 17. Architecture Decision Records (key decisions with rationale)
+<action>Generate sections: 1. Executive Summary (2-3 sentences about the architecture approach) 2. Project Initialization (starter command if applicable) 3. Decision Summary Table (with verified versions and coverage mapping) 4. Complete Project Structure (full tree, no placeholders)
+<check if="{epics_content} is not empty"> 5. Epic to Architecture Mapping (every epic placed)
+</check>
+<check if="{epics_content} is empty"> 5. FR Category to Architecture Mapping (every FR category placed)
+</check> 6. Technology Stack Details (versions, configurations) 7. Integration Points (how components connect) 8. Novel Pattern Designs (if any were created) 9. Implementation Patterns (all consistency rules) 10. Consistency Rules (naming, organization, formats) 11. Data Architecture (models and relationships) 12. API Contracts (request/response formats) 13. Security Architecture (auth, authorization, data protection) 14. Performance Considerations (from NFRs) 15. Deployment Architecture (where and how) 16. Development Environment (setup and prerequisites) 17. Architecture Decision Records (key decisions with rationale)
 </action>
 
 <action>Fill template with all collected decisions and patterns</action>
@@ -622,14 +681,20 @@ Enforcement: "All agents MUST follow this pattern"
 <action>Run validation checklist from {installed_path}/checklist.md</action>
 
 <action>Verify MANDATORY items:
-□ Decision table has Version column with specific versions
-□ Every epic is mapped to architecture components
-□ Source tree is complete, not generic
-□ No placeholder text remains
-□ All FRs from PRD have architectural support
-□ All NFRs from PRD are addressed
-□ Implementation patterns cover all potential conflicts
-□ Novel patterns are fully documented (if applicable)
+
+- [] Decision table has Version column with specific versions
+  <check if="{epics_content} is not empty">
+- [] Every epic is mapped to architecture components
+  </check>
+  <check if="{epics_content} is empty">
+- [] Every FR category is mapped to architecture components
+  </check>
+- [] Source tree is complete, not generic
+- [] No placeholder text remains
+- [] All FRs from PRD have architectural support
+- [] All NFRs from PRD are addressed
+- [] Implementation patterns cover all potential conflicts
+- [] Novel patterns are fully documented (if applicable)
 </action>
 
   <check if="validation_failed">
@@ -663,20 +728,20 @@ Enforcement: "All agents MUST follow this pattern"
 
 <action>Save document to {output_folder}/architecture.md</action>
 
-  <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-    <param>mode: update</param>
-    <param>action: complete_workflow</param>
-    <param>workflow_name: architecture</param>
-  </invoke-workflow>
+  <check if="standalone_mode != true">
+    <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+    <action>Find workflow_status key "create-architecture"</action>
+    <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+    <action>Update workflow_status["create-architecture"] = "{output_folder}/bmm-architecture-{{date}}.md"</action>
+    <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
 
-  <check if="success == true">
-    <output>✅ Decision Architecture workflow complete!
-
-Status updated.
-</output>
+    <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>
 
+<output>✅ Decision Architecture workflow complete!</output>
+
 <output>**Deliverables Created:**
 
 - ✅ architecture.md - Complete architectural decisions document

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

@@ -4,7 +4,7 @@ description: "Collaborative architectural decision facilitation for AI-agent con
 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"
@@ -12,19 +12,32 @@ document_output_language: "{config_source}:document_output_language"
 user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 
-# Input requirements - We work from PRD, Epics, and optionally UX Spec
-recommended_inputs:
-  - prd: "Product Requirements Document with FRs and NFRs"
-  - epics: "Epic definitions with user stories and acceptance criteria"
-  - ux_spec: "UX specification with interface designs and interaction patterns (optional)"
-
-# Input file references (fuzzy matched from output folder)
-prd_file: "{output_folder}/bmm-PRD.md or PRD.md or product-requirements.md"
-epics_file: "{output_folder}/bmm-epics.md or epics.md or user-stories.md"
-ux_spec_file: "{output_folder}/ux-spec.md or ux-specification.md or user-experience.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 and features"
+    whole: "{output_folder}/*prd*.md"
+    sharded: "{output_folder}/*prd*/index.md"
+    load_strategy: "FULL_LOAD"
+  epics:
+    description: "Epic and story breakdown (optional - uses PRD FRs if not present)"
+    whole: "{output_folder}/*epic*.md"
+    sharded: "{output_folder}/*epic*/index.md"
+    load_strategy: "FULL_LOAD"
+  ux_design:
+    description: "UX design specification (optional)"
+    whole: "{output_folder}/*ux*.md"
+    sharded: "{output_folder}/*ux*/index.md"
+    load_strategy: "FULL_LOAD"
+  document_project:
+    description: "Brownfield project documentation (optional)"
+    sharded: "{output_folder}/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/architecture-template.md"
@@ -37,18 +50,51 @@ pattern_categories: "{installed_path}/pattern-categories.csv"
 # Output configuration
 default_output_file: "{output_folder}/architecture.md"
 
-# Workflow metadata
-version: "1.3.2"
-replaces: "architecture"
-paradigm: "facilitation-driven"
-execution_time: "30-90 minutes depending on user skill level"
-features:
-  - "Starter template discovery and integration"
-  - "Dynamic version verification via web search"
-  - "Adaptive facilitation by skill level"
-  - "Decision-focused architecture"
-  - "Novel pattern design for unique concepts"
-  - "Intelligent pattern identification - LLM figures out what patterns matter"
-  - "Implementation patterns for agent consistency"
-
 standalone: true
+
+# Web bundle configuration for standalone deployment
+web_bundle:
+  name: "architecture"
+  description: "Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts."
+  author: "BMad"
+
+  # Core workflow files ({bmad_folder}/-relative paths)
+  instructions: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/instructions.md"
+  validation: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/checklist.md"
+  template: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/architecture-template.md"
+
+  # Knowledge base files for decision making
+  decision_catalog: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml"
+  architecture_patterns: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml"
+  pattern_categories: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/pattern-categories.csv"
+
+  # Task dependencies
+  adv_elicit_task: "{bmad_folder}/core/tasks/advanced-elicitation.xml"
+
+  # Default configuration values (can be overridden during bundle setup)
+  defaults:
+    user_name: "User"
+    communication_language: "English"
+    document_output_language: "English"
+    user_skill_level: "intermediate"
+    output_folder: "./output"
+
+  # Input/output configuration for web deployment
+  default_output_file: "{output_folder}/architecture.md"
+
+  # Complete file list - ALL files this workflow depends on
+  web_bundle_files:
+    # Core workflow files
+    - "{bmad_folder}/bmm/workflows/3-solutioning/architecture/instructions.md"
+    - "{bmad_folder}/bmm/workflows/3-solutioning/architecture/checklist.md"
+    - "{bmad_folder}/bmm/workflows/3-solutioning/architecture/architecture-template.md"
+
+    # Knowledge base data files
+    - "{bmad_folder}/bmm/workflows/3-solutioning/architecture/decision-catalog.yaml"
+    - "{bmad_folder}/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml"
+    - "{bmad_folder}/bmm/workflows/3-solutioning/architecture/pattern-categories.csv"
+
+    # Task dependencies (referenced in instructions.md)
+    - "{bmad_folder}/core/tasks/workflow.xml"
+    - "{bmad_folder}/core/tasks/advanced-elicitation.xml"
+    - "{bmad_folder}/core/tasks/advanced-elicitation-methods.csv"