bmad-method 6.0.0-alpha.9 → 6.0.1

package/src/modules/bmgd/workflows/4-production/retrospective/workflow.yaml

@@ -1,52 +0,0 @@
-# Retrospective - Epic Completion Review Workflow
-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_folder}/bmgd/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_folder}/bmm/workflows/4-implementation/retrospective"
-template: false
-instructions: "{installed_path}/instructions.md"
-
-required_inputs:
-  - 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:
-    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:
-    pattern: "{sprint_artifacts}/**/epic-{{prev_epic_num}}-retro-*.md"
-    load_strategy: "SELECTIVE_LOAD"
-  architecture:
-    whole: "{output_folder}/*architecture*.md"
-    sharded: "{output_folder}/*architecture*/*.md"
-    load_strategy: "FULL_LOAD"
-  prd:
-    whole: "{output_folder}/*prd*.md"
-    sharded: "{output_folder}/*prd*/*.md"
-    load_strategy: "FULL_LOAD"
-  document_project:
-    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/bmgd/workflows/4-production/sprint-planning/instructions.md

@@ -1,234 +0,0 @@
-# Sprint Planning - Sprint Status Generator
-
-<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>
-
-<step n="1" goal="Parse epic files and extract all work items">
-<action>Communicate in {communication_language} with {user_name}</action>
-<action>Look for all files matching `{epics_pattern}` in {epics_location}</action>
-<action>Could be a single `epics.md` file or multiple `epic-1.md`, `epic-2.md` files</action>
-
-<action>For each epic file found, extract:</action>
-
-- Epic numbers from headers like `## Epic 1:` or `## Epic 2:`
-- Story IDs and titles from patterns like `### Story 1.1: User Authentication`
-- Convert story format from `Epic.Story: Title` to kebab-case key: `epic-story-title`
-
-**Story ID Conversion Rules:**
-
-- Original: `### Story 1.1: User Authentication`
-- Replace period with dash: `1-1`
-- Convert title to kebab-case: `user-authentication`
-- Final key: `1-1-user-authentication`
-
-<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>
-
-1. **Epic entry** - Key: `epic-{num}`, Default status: `backlog`
-2. **Story entries** - Key: `{epic}-{story}-{title}`, Default status: `backlog`
-3. **Retrospective entry** - Key: `epic-{num}-retrospective`, Default status: `optional`
-
-**Example structure:**
-
-```yaml
-development_status:
-  epic-1: backlog
-  1-1-user-authentication: backlog
-  1-2-account-management: backlog
-  epic-1-retrospective: optional
-```
-
-</step>
-
-<step n="3" goal="Apply intelligent status detection">
-<action>For each epic, check if tech context file exists:</action>
-
-- Check: `{output_folder}/epic-{num}-context.md`
-- If exists → set epic status to `contexted`
-- Else → keep as `backlog`
-
-<action>For each story, detect current status by checking files:</action>
-
-**Story file detection:**
-
-- Check: `{story_location_absolute}/{story-key}.md` (e.g., `stories/1-1-user-authentication.md`)
-- If exists → upgrade status to at least `drafted`
-
-**Story context detection:**
-
-- Check: `{story_location_absolute}/{story-key}-context.md` (e.g., `stories/1-1-user-authentication-context.md`)
-- If exists → upgrade status to at least `ready-for-dev`
-
-**Preservation rule:**
-
-- If existing `{status_file}` exists and has more advanced status, preserve it
-- Never downgrade status (e.g., don't change `done` to `drafted`)
-
-**Status Flow Reference:**
-
-- Epic: `backlog` → `contexted`
-- Story: `backlog` → `drafted` → `ready-for-dev` → `in-progress` → `review` → `done`
-- Retrospective: `optional` ↔ `completed`
-  </step>
-
-<step n="4" goal="Generate sprint status file">
-<action>Create or update {status_file} with:</action>
-
-**File Structure:**
-
-```yaml
-# generated: {date}
-# project: {project_name}
-# project_key: {project_key}
-# tracking_system: {tracking_system}
-# story_location: {story_location}
-
-# STATUS DEFINITIONS:
-# ==================
-# Epic Status:
-#   - backlog: Epic exists in epic file but not contexted
-#   - contexted: Epic tech context created (required before drafting stories)
-#
-# Story Status:
-#   - backlog: Story only exists in epic file
-#   - drafted: Story file created in stories folder
-#   - ready-for-dev: Draft approved and story context created
-#   - in-progress: Developer actively working on implementation
-#   - review: Under SM review (via code-review workflow)
-#   - done: Story completed
-#
-# Retrospective Status:
-#   - optional: Can be completed but not required
-#   - completed: Retrospective has been done
-#
-# WORKFLOW NOTES:
-# ===============
-# - Epics should be 'contexted' before stories can be 'drafted'
-# - Stories can be worked in parallel if team capacity allows
-# - SM typically drafts next story after previous one is 'done' to incorporate learnings
-# - Dev moves story to 'review', SM reviews, then Dev moves to 'done'
-
-generated: { date }
-project: { project_name }
-project_key: { project_key }
-tracking_system: { tracking_system }
-story_location: { story_location }
-
-development_status:
-  # All epics, stories, and retrospectives in order
-```
-
-<action>Write the complete sprint status YAML to {status_file}</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>
-
-<step n="5" goal="Validate and report">
-<action>Perform validation checks:</action>
-
-- [ ] 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 {status_file} that don't exist in epic files
-- [ ] All status values are legal (match state machine definitions)
-- [ ] File is valid YAML syntax
-
-<action>Count totals:</action>
-
-- Total epics: {{epic_count}}
-- Total stories: {{story_count}}
-- Epics contexted: {{contexted_count}}
-- Stories in progress: {{in_progress_count}}
-- Stories done: {{done_count}}
-
-<action>Display completion summary to {user_name} in {communication_language}:</action>
-
-**Sprint Status Generated Successfully**
-
-- **File Location:** {status_file}
-- **Total Epics:** {{epic_count}}
-- **Total Stories:** {{story_count}}
-- **Contexted Epics:** {{contexted_count}}
-- **Stories In Progress:** {{in_progress_count}}
-- **Stories Completed:** {{done_count}}
-
-**Next Steps:**
-
-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
-
-</step>
-
-</workflow>
-
-## Additional Documentation
-
-### Status State Machine
-
-**Epic Status Flow:**
-
-```
-backlog → contexted
-```
-
-- **backlog**: Epic exists in epic file but tech context not created
-- **contexted**: Epic tech context has been generated (prerequisite for story drafting)
-
-**Story Status Flow:**
-
-```
-backlog → drafted → ready-for-dev → in-progress → review → done
-```
-
-- **backlog**: Story only exists in epic file
-- **drafted**: Story file created (e.g., `stories/1-3-plant-naming.md`)
-- **ready-for-dev**: Draft approved + story context created
-- **in-progress**: Developer actively working
-- **review**: Under SM review (via code-review workflow)
-- **done**: Completed
-
-**Retrospective Status:**
-
-```
-optional ↔ completed
-```
-
-- **optional**: Can be done but not required
-- **completed**: Retrospective has been completed
-
-### Guidelines
-
-1. **Epic Context Recommended**: Epics should be `contexted` before stories can be `drafted`
-2. **Sequential Default**: Stories are typically worked in order, but parallel work is supported
-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

package/src/modules/bmgd/workflows/4-production/sprint-planning/sprint-status-template.yaml

@@ -1,55 +0,0 @@
-# Sprint Status Template
-# This is an EXAMPLE showing the expected format
-# The actual file will be generated with all epics/stories from your epic files
-
-# generated: {date}
-# project: {project_name}
-# project_key: {project_key}
-# tracking_system: {tracking_system}
-# story_location: {story_location}
-
-# STATUS DEFINITIONS:
-# ==================
-# Epic Status:
-#   - backlog: Epic exists in epic file but not contexted
-#   - contexted: Next epic tech context created by *epic-tech-context (required)
-#
-# Story Status:
-#   - backlog: Story only exists in epic file
-#   - drafted: Story file created in stories folder by *create-story
-#   - ready-for-dev: Draft approved and story context created by *story-ready
-#   - in-progress: Developer actively working on implementation by *dev-story
-#   - review: Implementation complete, ready for review by *code-review
-#   - done: Story completed by *story-done
-#
-# Retrospective Status:
-#   - optional: Can be completed but not required
-#   - completed: Retrospective has been done by *retrospective
-#
-# WORKFLOW NOTES:
-# ===============
-# - Epics should be 'contexted' before stories can be 'drafted'
-# - SM typically drafts next story ONLY after previous one is 'done' to incorporate learnings
-# - Dev moves story to 'review', dev reviews, then Dev moves to 'done'
-
-# EXAMPLE STRUCTURE (your actual epics/stories will replace these):
-
-generated: 05-06-2-2025 21:30
-project: My Awesome Project
-project_key: jira-1234
-tracking_system: file-system
-story_location: "{story_location}"
-
-development_status:
-  epic-1: contexted
-  1-1-user-authentication: done
-  1-2-account-management: drafted
-  1-3-plant-data-model: backlog
-  1-4-add-plant-manual: backlog
-  epic-1-retrospective: optional
-
-  epic-2: backlog
-  2-1-personality-system: backlog
-  2-2-chat-interface: backlog
-  2-3-llm-integration: backlog
-  epic-2-retrospective: optional

package/src/modules/bmgd/workflows/4-production/sprint-planning/workflow.yaml

@@ -1,50 +0,0 @@
-name: sprint-planning
-description: "Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle"
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmgd/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_folder}/bmm/workflows/4-implementation/sprint-planning"
-instructions: "{installed_path}/instructions.md"
-template: "{installed_path}/sprint-status-template.yaml"
-validation: "{installed_path}/checklist.md"
-
-# Variables and inputs
-variables:
-  # Project identification
-  project_name: "{config_source}:project_name"
-
-  # 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: "{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: "{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:
-    whole: "{output_folder}/*epic*.md"
-    sharded: "{output_folder}/*epic*/*.md"
-    load_strategy: "FULL_LOAD"
-
-# Output configuration
-default_output_file: "{status_file}"
-
-standalone: true
-
-web_bundle: false

package/src/modules/bmgd/workflows/4-production/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/bmgd/workflows/4-production/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/bmgd/workflows/4-production/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>
-```