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

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

@@ -1,164 +0,0 @@
-<!-- BMAD BMM Tech Spec Workflow Instructions (v6) -->
-
-```xml
-<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>This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping.</critical>
-<critical>If required inputs cannot be auto-discovered HALT with a clear message listing missing documents, allow user to provide them to proceed.</critical>
-
-<workflow>
-  <step n="1" goal="Collect inputs and discover next epic" tag="sprint-status">
-    <action>Identify PRD and Architecture documents from recommended_inputs. Attempt to auto-discover at default paths.</action>
-    <ask if="inputs are missing">ask the user for file paths. HALT and wait for docs to proceed</ask>
-
-    <!-- Intelligent Epic Discovery -->
-    <critical>MUST read COMPLETE {sprint-status} file to discover next epic</critical>
-    <action>Read ALL development_status entries</action>
-    <action>Find all epics with status "backlog" (not yet contexted)</action>
-    <action>Identify the FIRST backlog epic as the suggested default</action>
-
-    <check if="backlog epics found">
-      <output>📋 **Next Epic Suggested:** Epic {{suggested_epic_id}}: {{suggested_epic_title}}</output>
-      <ask>Use this epic?
-- [y] Yes, use {{suggested_epic_id}}
-- [n] No, let me specify a different epic_id
-      </ask>
-
-      <check if="user selects 'n'">
-        <ask>Enter the epic_id you want to context</ask>
-        <action>Store user-provided epic_id as {{epic_id}}</action>
-      </check>
-
-      <check if="user selects 'y'">
-        <action>Use {{suggested_epic_id}} as {{epic_id}}</action>
-      </check>
-    </check>
-
-    <check if="no backlog epics found">
-      <output>✅ All epics are already contexted!
-
-No epics with status "backlog" found in sprint-status.yaml.
-      </output>
-      <ask>Do you want to re-context an existing epic? Enter epic_id or [q] to quit:</ask>
-
-      <check if="user enters epic_id">
-        <action>Store as {{epic_id}}</action>
-      </check>
-
-      <check if="user enters 'q'">
-        <action>HALT - No work needed</action>
-      </check>
-    </check>
-
-    <action>Resolve output file path using workflow variables and initialize by writing the template.</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: {prd_content}, {gdd_content}, {architecture_content}, {ux_design_content}, {epics_content} (will load only epic-{{epic_id}}.md if sharded), {document_project_content}</note>
-    <action>Extract {{epic_title}} from {prd_content} or {epics_content} based on {{epic_id}}.</action>
-  </step>
-
-  <step n="2" goal="Validate epic exists in sprint status" tag="sprint-status">
-    <action>Look for epic key "epic-{{epic_id}}" in development_status (already loaded from step 1)</action>
-    <action>Get current status value if epic exists</action>
-
-    <check if="epic not found">
-      <output>⚠️ Epic {{epic_id}} not found in sprint-status.yaml
-
-This epic hasn't been registered in the sprint plan yet.
-Run sprint-planning workflow to initialize epic tracking.
-      </output>
-      <action>HALT</action>
-    </check>
-
-    <check if="epic status == 'contexted'">
-      <output>ℹ️ Epic {{epic_id}} already marked as contexted
-
-Continuing to regenerate tech spec...
-      </output>
-    </check>
-  </step>
-
-  <step n="3" goal="Overview and scope">
-    <action>Read COMPLETE found {recommended_inputs}.</action>
-    <template-output file="{default_output_file}">
-      Replace {{overview}} with a concise 1-2 paragraph summary referencing PRD context and goals
-      Replace {{objectives_scope}} with explicit in-scope and out-of-scope bullets
-      Replace {{system_arch_alignment}} with a short alignment summary to the architecture (components referenced, constraints)
-    </template-output>
-  </step>
-
-  <step n="4" goal="Detailed design">
-    <action>Derive concrete implementation specifics from all {recommended_inputs} (CRITICAL: NO invention). If a epic tech spec precedes this one and exists, maintain consistency where appropriate.</action>
-    <template-output file="{default_output_file}">
-      Replace {{services_modules}} with a table or bullets listing services/modules with responsibilities, inputs/outputs, and owners
-      Replace {{data_models}} with normalized data model definitions (entities, fields, types, relationships); include schema snippets where available
-      Replace {{apis_interfaces}} with API endpoint specs or interface signatures (method, path, request/response models, error codes)
-      Replace {{workflows_sequencing}} with sequence notes or diagrams-as-text (steps, actors, data flow)
-    </template-output>
-  </step>
-
-  <step n="5" goal="Non-functional requirements">
-    <template-output file="{default_output_file}">
-      Replace {{nfr_performance}} with measurable targets (latency, throughput); link to any performance requirements in PRD/Architecture
-      Replace {{nfr_security}} with authn/z requirements, data handling, threat notes; cite source sections
-      Replace {{nfr_reliability}} with availability, recovery, and degradation behavior
-      Replace {{nfr_observability}} with logging, metrics, tracing requirements; name required signals
-    </template-output>
-  </step>
-
-  <step n="6" goal="Dependencies and integrations">
-    <action>Scan repository for dependency manifests (e.g., package.json, pyproject.toml, go.mod, Unity Packages/manifest.json).</action>
-    <template-output file="{default_output_file}">
-      Replace {{dependencies_integrations}} with a structured list of dependencies and integration points with version or commit constraints when known
-    </template-output>
-  </step>
-
-  <step n="7" goal="Acceptance criteria and traceability">
-    <action>Extract acceptance criteria from PRD; normalize into atomic, testable statements.</action>
-    <template-output file="{default_output_file}">
-      Replace {{acceptance_criteria}} with a numbered list of testable acceptance criteria
-      Replace {{traceability_mapping}} with a table mapping: AC → Spec Section(s) → Component(s)/API(s) → Test Idea
-    </template-output>
-  </step>
-
-  <step n="8" goal="Risks and test strategy">
-    <template-output file="{default_output_file}">
-      Replace {{risks_assumptions_questions}} with explicit list (each item labeled as Risk/Assumption/Question) with mitigation or next step
-      Replace {{test_strategy}} with a brief plan (test levels, frameworks, coverage of ACs, edge cases)
-    </template-output>
-  </step>
-
-  <step n="9" goal="Validate and mark epic contexted" tag="sprint-status">
-    <invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
-
-    <!-- Mark epic as contexted -->
-    <action>Load the FULL file: {sprint_status}</action>
-    <action>Find development_status key "epic-{{epic_id}}"</action>
-    <action>Verify current status is "backlog" (expected previous state)</action>
-    <action>Update development_status["epic-{{epic_id}}"] = "contexted"</action>
-    <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-    <check if="epic key not found in file">
-      <output>⚠️ Could not update epic status: epic-{{epic_id}} not found</output>
-    </check>
-
-    <output>**✅ Tech Spec Generated Successfully, {user_name}!**
-
-**Epic Details:**
-- Epic ID: {{epic_id}}
-- Epic Title: {{epic_title}}
-- Tech Spec File: {{default_output_file}}
-- Epic Status: contexted (was backlog)
-
-**Note:** This is a JIT (Just-In-Time) workflow - run again for other epics as needed.
-
-**Next Steps:**
-1. Load SM agent and run `create-story` to begin implementing the first story under this epic.
-    </output>
-  </step>
-
-</workflow>
-```

package/src/modules/bmm/workflows/4-implementation/epic-tech-context/template.md

@@ -1,76 +0,0 @@
-# Epic Technical Specification: {{epic_title}}
-
-Date: {{date}}
-Author: {{user_name}}
-Epic ID: {{epic_id}}
-Status: Draft
-
----
-
-## Overview
-
-{{overview}}
-
-## Objectives and Scope
-
-{{objectives_scope}}
-
-## System Architecture Alignment
-
-{{system_arch_alignment}}
-
-## Detailed Design
-
-### Services and Modules
-
-{{services_modules}}
-
-### Data Models and Contracts
-
-{{data_models}}
-
-### APIs and Interfaces
-
-{{apis_interfaces}}
-
-### Workflows and Sequencing
-
-{{workflows_sequencing}}
-
-## Non-Functional Requirements
-
-### Performance
-
-{{nfr_performance}}
-
-### Security
-
-{{nfr_security}}
-
-### Reliability/Availability
-
-{{nfr_reliability}}
-
-### Observability
-
-{{nfr_observability}}
-
-## Dependencies and Integrations
-
-{{dependencies_integrations}}
-
-## Acceptance Criteria (Authoritative)
-
-{{acceptance_criteria}}
-
-## Traceability Mapping
-
-{{traceability_mapping}}
-
-## Risks, Assumptions, Open Questions
-
-{{risks_assumptions_questions}}
-
-## Test Strategy Summary
-
-{{test_strategy}}

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

@@ -1,58 +0,0 @@
-name: epic-tech-context
-description: "Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping"
-author: "BMAD BMM"
-
-# Critical variables
-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"
-
-# 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 (epic_num from context)
-input_file_patterns:
-  prd:
-    description: "Product requirements (optional)"
-    whole: "{output_folder}/*prd*.md"
-    sharded: "{output_folder}/*prd*/*.md"
-    load_strategy: "FULL_LOAD"
-  gdd:
-    description: "Game Design Document (for game projects)"
-    whole: "{output_folder}/*gdd*.md"
-    sharded: "{output_folder}/*gdd*/*.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: "Specific epic for tech spec generation"
-    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"
-
-# Workflow components
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context"
-template: "{installed_path}/template.md"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Output configuration
-default_output_file: "{sprint_artifacts}/tech-spec-epic-{{epic_id}}.md"
-standalone: true
-web_bundle: false

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

@@ -1,16 +0,0 @@
-# Story Context Assembly Checklist
-
-```xml
-<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>
-  <item>Relevant docs (5-15) included with path and snippets</item>
-  <item>Relevant code references included with reason and line hints</item>
-  <item>Interfaces/API contracts extracted if applicable</item>
-  <item>Constraints include applicable dev rules and patterns</item>
-  <item>Dependencies detected from manifests and frameworks</item>
-  <item>Testing standards and locations populated</item>
-  <item>XML structure follows story-context template format</item>
-</checklist>
-```

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

@@ -1,34 +0,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>
-    <title>{{story_title}}</title>
-    <status>{{story_status}}</status>
-    <generatedAt>{{date}}</generatedAt>
-    <generator>BMAD Story Context Workflow</generator>
-    <sourceStoryPath>{{story_path}}</sourceStoryPath>
-  </metadata>
-
-  <story>
-    <asA>{{as_a}}</asA>
-    <iWant>{{i_want}}</iWant>
-    <soThat>{{so_that}}</soThat>
-    <tasks>{{story_tasks}}</tasks>
-  </story>
-
-  <acceptanceCriteria>{{acceptance_criteria}}</acceptanceCriteria>
-
-  <artifacts>
-    <docs>{{docs_artifacts}}</docs>
-    <code>{{code_artifacts}}</code>
-    <dependencies>{{dependencies_artifacts}}</dependencies>
-  </artifacts>
-
-  <constraints>{{constraints}}</constraints>
-  <interfaces>{{interfaces}}</interfaces>
-  <tests>
-    <standards>{{test_standards}}</standards>
-    <locations>{{test_locations}}</locations>
-    <ideas>{{test_ideas}}</ideas>
-  </tests>
-</story-context>

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

@@ -1,209 +0,0 @@
-<!-- BMAD BMM Story Context Assembly Instructions (v6) -->
-
-```xml
-<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>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>
-
-<workflow>
-  <step n="1" goal="Find drafted story and check for existing context" tag="sprint-status">
-    <check if="{{story_path}} is provided">
-      <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 "drafted" - if not, HALT with message: "Story status must be 'drafted' to generate context"</action>
-    </check>
-
-    <check if="{{story_path}} is NOT provided">
-      <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>
-      <action>Read ALL lines from beginning to end - do not skip any content</action>
-      <action>Parse the development_status section completely</action>
-
-      <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 "drafted"
-      </action>
-
-      <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.
-
-          **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_path}} using story_key pattern</action>
-      <action>Read the COMPLETE story file</action>
-    </check>
-
-    <action>Extract {{epic_id}}, {{story_id}}, {{story_title}}, {{story_status}} from filename/content</action>
-    <action>Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes</action>
-    <action>Extract user story fields (asA, iWant, soThat)</action>
-    <template-output file="{default_output_file}">story_tasks</template-output>
-    <template-output file="{default_output_file}">acceptance_criteria</template-output>
-
-    <!-- Check if context file already exists -->
-    <action>Check if file exists at {default_output_file}</action>
-
-    <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
-      </output>
-      <ask>Choose action (replace/verify/cancel):</ask>
-
-      <check if="user chooses verify">
-        <action>GOTO validation_step</action>
-      </check>
-
-      <check if="user chooses cancel">
-        <action>HALT with message: "Context generation cancelled"</action>
-      </check>
-
-      <check if="user chooses replace">
-        <action>Continue to generate new context file</action>
-      </check>
-    </check>
-
-    <action>Store project root path for relative path conversion: extract from {project-root} variable</action>
-    <action>Define path normalization function: convert any absolute path to project-relative by removing project root prefix</action>
-    <action>Initialize output by writing template to {default_output_file}</action>
-    <template-output file="{default_output_file}">as_a</template-output>
-    <template-output file="{default_output_file}">i_want</template-output>
-    <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>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}:
-      - path: PROJECT-RELATIVE path only (strip {project-root} prefix)
-      - title: Document title
-      - section: Relevant section name
-      - snippet: Brief excerpt (2-3 sentences max, NO invention)
-    </template-output>
-  </step>
-
-  <step n="3" goal="Analyze existing code, interfaces, and constraints">
-    <action>Search source tree for modules, files, and symbols matching story intent and AC keywords (controllers, services, components, tests).</action>
-    <action>Identify existing interfaces/APIs the story should reuse rather than recreate.</action>
-    <action>Extract development constraints from Dev Notes and architecture (patterns, layers, testing requirements).</action>
-    <action>For all discovered code artifacts: convert absolute paths to project-relative format (strip {project-root} prefix).</action>
-    <template-output file="{default_output_file}">
-      Add artifacts.code entries with {path, kind, symbol, lines, reason}:
-      - path: PROJECT-RELATIVE path only (e.g., "src/services/api.js" not full path)
-      - kind: file type (controller, service, component, test, etc.)
-      - symbol: function/class/interface name
-      - lines: line range if specific (e.g., "45-67")
-      - reason: brief explanation of relevance to this story
-
-      Populate interfaces with API/interface signatures:
-      - name: Interface or API name
-      - kind: REST endpoint, GraphQL, function signature, class interface
-      - signature: Full signature or endpoint definition
-      - path: PROJECT-RELATIVE path to definition
-
-      Populate constraints with development rules:
-      - Extract from Dev Notes and architecture
-      - Include: required patterns, layer restrictions, testing requirements, coding standards
-    </template-output>
-  </step>
-
-  <step n="4" goal="Gather dependencies and frameworks">
-    <action>Detect dependency manifests and frameworks in the repo:
-      - Node: package.json (dependencies/devDependencies)
-      - Python: pyproject.toml/requirements.txt
-      - Go: go.mod
-      - Unity: Packages/manifest.json, Assets/, ProjectSettings/
-      - Other: list notable frameworks/configs found</action>
-    <template-output file="{default_output_file}">
-      Populate artifacts.dependencies with keys for detected ecosystems and their packages with version ranges where present
-    </template-output>
-  </step>
-
-  <step n="5" goal="Testing standards and ideas">
-    <action>From Dev Notes, architecture docs, testing docs, and existing tests, extract testing standards (frameworks, patterns, locations).</action>
-    <template-output file="{default_output_file}">
-      Populate tests.standards with a concise paragraph
-      Populate tests.locations with directories or glob patterns where tests live
-      Populate tests.ideas with initial test ideas mapped to acceptance criteria IDs
-    </template-output>
-  </step>
-
-  <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_folder}/core/tasks/validate-workflow.xml</invoke-task>
-  </step>
-
-  <step n="7" goal="Update story file and mark ready for dev" tag="sprint-status">
-    <action>Open {{story_path}}</action>
-    <action>Find the "Status:" line (usually at the top)</action>
-    <action>Update story file: Change Status to "ready-for-dev"</action>
-    <action>Under 'Dev Agent Record' → 'Context Reference' (create if missing), add or update a list item for {default_output_file}.</action>
-    <action>Save the story file.</action>
-
-    <!-- Update sprint status to mark ready-for-dev -->
-    <action>Load the FULL file: {{output_folder}}/sprint-status.yaml</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>
-    <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-    <check if="story key not found in file">
-      <output>⚠️ Story file updated, but could not update sprint-status: {{story_key}} not found
-
-You may need to run sprint-planning to refresh tracking.
-      </output>
-    </check>
-
-    <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
-- Testing standards and ideas
-- 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
-    </output>
-  </step>
-
-</workflow>
-```

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

@@ -1,63 +0,0 @@
-# Story Context Creation Workflow
-name: story-context
-description: "Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story"
-author: "BMad"
-
-# Critical variables
-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}:sprint_artifacts"
-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_folder}/bmm/workflows/4-implementation/story-context"
-template: "{installed_path}/context-template.xml"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# 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_path}/{{story_key}}.context.xml"
-
-standalone: true
-
-web_bundle: false