ma-agents 3.4.7 → 3.4.9

package/lib/bmad-extension/skills/create-bug-story/SKILL.md

@@ -55,32 +55,7 @@ Guided workflow to create a structured bug story from a detected defect and add
   <action>Store as {{actual_behavior}}</action>
 </step>
 
-<step n="4" goal="Gather version and bug type">
-  <ask>What version was this bug found in? (optional — press Enter to skip; e.g., "2.3.1", "v1.0.0-rc2")</ask>
-  <action>Store as {{version_found}} (empty string if skipped)</action>
-
-  <output>
-**Bug type classifications:**
-- `regression` — Previously working feature now broken
-- `functional` — Feature does not work as specified
-- `performance` — Unacceptable latency, throughput, or resource usage
-- `security` — Vulnerability or authentication/authorization flaw
-- `ui` — Visual or interaction defect
-- `data` — Data corruption, loss, or incorrect transformation
-- `integration` — Failure at system/service boundaries
-- `other` — Does not fit the above categories
-  </output>
-  <ask>What is the bug type? [regression / functional / performance / security / ui / data / integration / other] (default: functional)</ask>
-  <action>Store as {{bug_type}}</action>
-  <action>If empty or blank, default to "functional"</action>
-  <action>Normalize to lowercase</action>
-  <check if="{{bug_type}} is not one of: regression, functional, performance, security, ui, data, integration, other">
-    <output>❌ Bug type must be one of: regression, functional, performance, security, ui, data, integration, other.</output>
-    <goto step="4" />
-  </check>
-</step>
-
-<step n="5" goal="Gather root cause hypothesis and affected files">
+<step n="4" goal="Gather root cause hypothesis and affected files">
   <ask>What is your root cause hypothesis? (optional — press Enter to skip; e.g., "Null check missing in validateUser()")</ask>
   <action>Store as {{root_cause}} (empty string if skipped)</action>
 
@@ -92,7 +67,7 @@ Guided workflow to create a structured bug story from a detected defect and add
   <action>Store as {{suggested_fix}} (empty string if skipped)</action>
 </step>
 
-<step n="6" goal="Confirm all bug details before writing">
+<step n="5" goal="Confirm all bug details before writing">
   <action>Derive {{title_slug}} by converting {{bug_title}} to lowercase kebab-case:
     - Convert to lowercase
     - Replace spaces and underscores with hyphens
@@ -107,8 +82,6 @@ Guided workflow to create a structured bug story from a detected defect and add
 
 - **Title:** {{bug_title}}
 - **Severity:** {{severity}}
-- **Bug Type:** {{bug_type}}
-- **Version Found:** {{version_found}} *(empty if skipped)*
 - **Affected Component:** {{affected_component}}
 - **Reproduction Steps:** {{reproduction_steps}}
 - **Expected Behavior:** {{expected_behavior}}
@@ -120,15 +93,14 @@ Guided workflow to create a structured bug story from a detected defect and add
   </output>
   <ask>Confirm creation? [y] Yes / [n] Cancel / [e] Edit a field:</ask>
   <check if="user selects 'e'">
-    <ask>Which field to edit? (title / severity / component / steps / expected / actual / version / bug-type / root-cause / files / fix)</ask>
+    <ask>Which field to edit? (title / severity / component / steps / expected / actual / root-cause / files / fix)</ask>
     <check if="field == 'title' OR field == 'severity'"><goto step="1" /></check>
     <check if="field == 'component' OR field == 'steps'"><goto step="2" /></check>
     <check if="field == 'expected' OR field == 'actual'"><goto step="3" /></check>
-    <check if="field == 'version' OR field == 'bug-type'"><goto step="4" /></check>
-    <check if="field == 'root-cause' OR field == 'files' OR field == 'fix'"><goto step="5" /></check>
+    <check if="field == 'root-cause' OR field == 'files' OR field == 'fix'"><goto step="4" /></check>
     <check if="none of the above matched">
-      <output>❌ Unrecognized field. Valid options: title / severity / component / steps / expected / actual / version / bug-type / root-cause / files / fix</output>
-      <goto step="6" />
+      <output>❌ Unrecognized field. Valid options: title / severity / component / steps / expected / actual / root-cause / files / fix</output>
+      <goto step="5" />
     </check>
   </check>
   <check if="user selects 'n'">
@@ -137,7 +109,7 @@ Guided workflow to create a structured bug story from a detected defect and add
   </check>
 </step>
 
-<step n="7" goal="Write bug story file">
+<step n="6" goal="Write bug story file">
   <action>Check if {{output_file}} already exists</action>
   <check if="file already exists">
     <output>⚠️ A bug story already exists at `{{output_file}}`.</output>
@@ -164,10 +136,7 @@ Guided workflow to create a structured bug story from a detected defect and add
 ```
 ---
 type: bug
-status: backlog
 severity: {{severity}}
-bug_type: {{bug_type}}
-version_found: {{version_found}}
 title: {{bug_title}}
 ---
 
@@ -214,45 +183,8 @@ title: {{bug_title}}
 - **File:** `{{output_file}}`
 - **Title:** {{bug_title}}
 - **Severity:** {{severity}}
-- **Bug Type:** {{bug_type}}
 - **Component:** {{affected_component}}
-  </output>
-</step>
-
-<step n="8" goal="Add bug entry to backlog.yaml">
-  <action>Check if `_bmad-output/implementation-artifacts/backlog.yaml` exists</action>
-
-  <check if="backlog.yaml exists">
-    <action>Read `_bmad-output/implementation-artifacts/backlog.yaml`</action>
-    <action>Determine the next priority number by finding the highest existing priority value and adding 1</action>
-    <action>Append a new entry at the end of the backlog items list with the following format:
-```yaml
-- id: "BUG-{{title_slug}}"
-  type: bug
-  epic: null
-  title: "{{bug_title}}"
-  priority: N
-  status: backlog
-  sprint: null
-  severity: {{severity}}
-```
-    Where N is the next priority number.
-    </action>
-    <action>Re-number all priorities sequentially (1, 2, 3, ...) from top to bottom to ensure no gaps</action>
-    <action>Write the updated backlog.yaml back to disk</action>
-    <output>
-📋 **Backlog updated!** Added `BUG-{{title_slug}}` to `_bmad-output/implementation-artifacts/backlog.yaml` with priority {{N}}.
-    </output>
-  </check>
 
-  <check if="backlog.yaml does not exist">
-    <output>
-ℹ️ No `backlog.yaml` found at `_bmad-output/implementation-artifacts/backlog.yaml`.
-Run `/generate-backlog` to create a backlog that will include this bug story.
-    </output>
-  </check>
-
-  <output>
 **Next Steps:**
 - Use `/add-to-sprint` to assign this bug to the current sprint
 - Use `/sprint-status-view` to see all sprint items including this bug

package/lib/bmad-extension/skills/modify-sprint/SKILL.md

@@ -7,75 +7,12 @@ triggers:
   - "edit sprint"
 ---
 
-<!-- PARTIALLY REWORKED: Item assignment is handled by /add-to-sprint (Story 17.4).
-     Item removal is handled by /remove-from-sprint (Story 17.5).
-     Sprint activation (planning -> active) is handled below (Step 3e).
-     The legacy workflow below still references old sprint-plan-{n}.yaml paths for
-     other operations. A full rework of modify-sprint is planned for a future story. -->
-
-> **Note:** Item assignment and removal are now handled by `/add-to-sprint` and `/remove-from-sprint`. Use the **Activate Sprint** option below to transition a sprint from `planning` to `active`.
-
 # Modify Sprint Workflow
 
 Guided workflow to modify an existing sprint — add/remove items, change capacity, update metadata.
 
 <workflow>
 
-<step n="3e" goal="Activate a sprint (planning -> active)">
-  <action>Glob `_bmad-output/implementation-artifacts/sprints/sprint-*.yaml` to discover all sprint files</action>
-  <check if="no sprint files found">
-    <output>No sprints found. Run `/add-sprint` first.</output>
-    <action>Exit workflow</action>
-  </check>
-  <action>Read each sprint file; extract: id, name, status, capacity, items count</action>
-  <action>Display sprints table</action>
-  <output>
-## Available Sprints
-
-| # | ID | Name | Status | Items | Capacity |
-|---|---|---|---|---|---|
-{{#each sprints}}
-| {{@index+1}} | {{id}} | {{name}} | {{status}} | {{items_count}} | {{capacity}} |
-{{/each}}
-  </output>
-  <ask>Which sprint to activate? (enter number, or 'q' to cancel):</ask>
-  <check if="user enters 'q'">
-    <output>Cancelled.</output>
-    <action>Exit workflow</action>
-  </check>
-  <action>Store selected sprint as {{target_sprint}}</action>
-
-  <!-- Validate transition -->
-  <check if="target_sprint.status != 'planning'">
-    <output>Only sprints in `planning` status can be activated. Sprint "{{target_sprint.name}}" is currently `{{target_sprint.status}}`.</output>
-    <action>Exit workflow</action>
-  </check>
-
-  <!-- Check single-active constraint -->
-  <action>Check if any other sprint has status `active`</action>
-  <check if="another sprint is already active">
-    <output>Cannot activate "{{target_sprint.name}}" — sprint "{{active_sprint.name}}" ({{active_sprint.id}}) is already active. Close it first before activating another sprint.</output>
-    <action>Exit workflow</action>
-  </check>
-
-  <ask>Activate "{{target_sprint.name}}" ({{target_sprint.id}})? This will set status to `active`. [y] Yes / [n] Cancel:</ask>
-  <check if="user selects 'n'">
-    <output>Cancelled.</output>
-    <action>Exit workflow</action>
-  </check>
-
-  <action>Set target_sprint.status = "active"</action>
-  <action>Update `last_modified` to current ISO timestamp</action>
-  <action>Write updated sprint file to `_bmad-output/implementation-artifacts/sprints/{{target_sprint.id}}.yaml`</action>
-  <output>
-Sprint "{{target_sprint.name}}" is now **active**.
-
-**Next Steps:**
-- Use `/add-to-sprint` to assign backlog items
-- Use `/sprint-status-view` to see sprint progress
-  </output>
-</step>
-
 <step n="1" goal="List available sprints and select one to modify">
   <action>Glob `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` to discover all sprint artifact files</action>
   <check if="no sprint files found">

package/lib/bmad-extension/skills/sprint-status-view/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sprint-status-view
-description: Display sprint progress with capacity, items, and backlog. Regenerates sprint-status.yaml.
+description: Display sprint progress with assigned items, type distinction, and remaining capacity
 type: skill
 triggers:
   - "sprint status view"
@@ -9,255 +9,194 @@ triggers:
 
 # Sprint Status View Workflow
 
-Display sprint status with capacity, items, and backlog summary. Regenerates `sprint-status.yaml` from authoritative sources.
+Extension workflow that displays sprint progress with assigned items (stories + bugs), type distinction, and remaining capacity.
 
-<workflow>
-
-<step n="1" goal="Suggest running /cleanup-done first">
-  <output>
-**Tip:** Consider running `/cleanup-done` before viewing sprint status to archive completed items and free capacity.
-  </output>
-  <action>Continue to next step (advisory only -- do not auto-invoke /cleanup-done)</action>
-</step>
-
-<step n="2" goal="Load data sources">
-  <action>Glob `_bmad-output/implementation-artifacts/sprints/sprint-*.yaml` to discover all sprint entity files</action>
-  <action>Store discovered sprint files as {{sprint_files}} list</action>
+> **Architecture mandate:** This workflow is a NEW extension at `lib/bmad-extension/workflows/sprint-status-view/`. It does NOT modify any files under `_bmad/bmm/workflows/`.
 
-  <action>Read `_bmad-output/implementation-artifacts/backlog.yaml` if it exists</action>
-  <action>Store the backlog items list as {{backlog_items}} (or empty list if file not found)</action>
-
-  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` to discover all bug story files (fallback for bug metadata)</action>
-  <action>For each bug file found, parse YAML frontmatter to extract: title, severity, status</action>
-  <action>Store as {{bug_metadata_map}} keyed by file basename (e.g., `bug-login-crash`)</action>
-
-  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml` if it exists (fallback for story status when backlog.yaml is missing or incomplete)</action>
-  <action>Parse development_status section into {{status_fallback_map}} -- key: story key, value: status</action>
-  <action>Exclude epic-* keys and *-retrospective keys from the fallback map</action>
+<workflow>
 
-  <check if="no sprint files found AND no backlog.yaml exists">
+<step n="1" goal="Discover all sprint artifact files">
+  <action>Glob `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` to discover all sprint artifact files</action>
+  <check if="no sprint files found">
     <output>
-**No Sprint Data Found**
+ℹ️ **No Sprints Found**
 
-No sprint files exist (`sprints/sprint-*.yaml`) and no `backlog.yaml` was found.
+No sprint plan files exist yet (`sprint-plan-*.yaml`).
 
 **To get started:**
-1. Run `/generate-backlog` to create a backlog from your epics
-2. Run `/add-sprint` to create your first sprint
-3. Run `/add-to-sprint` to assign backlog items to it
+- Run `/add-sprint` to create your first sprint
+- Run `/add-to-sprint` to assign backlog items to it
     </output>
     <action>Exit workflow</action>
   </check>
+  <action>For each sprint file found, read the full YAML content and store as {{sprint_plans}} list</action>
+  <action>Sort {{sprint_plans}} by sprint_number ascending</action>
 </step>
 
-<step n="3" goal="Display each sprint">
-  <action>For each sprint in {{sprint_files}}, read the full YAML content</action>
-  <action>Sort sprints for display: active first, then planning, then closed</action>
-  <action>Initialize {{total_done_in_sprints}} = 0 for step 4</action>
-
-  <action>For each sprint (in sorted order):
-
-    **If sprint.status is "closed":**
-    - Count total items in sprint.items
-    - Display collapsed summary line only
-
-    **If sprint.status is NOT "closed" (active or planning):**
-    - Calculate {{item_count}} = length(sprint.items)
-    - For each item identifier in sprint.items, resolve details:
-      - Look up item in {{backlog_items}} by matching `id` field
-      - If found in backlog: use `type`, `title`, `status`, `severity` from backlog entry
-      - If NOT found in backlog and item matches `^bug-`: look up in {{bug_metadata_map}} for title/severity, use status from bug frontmatter or default to "backlog"
-      - If NOT found in backlog and item matches a story pattern: look up in {{status_fallback_map}} for status, infer title from key, set type to "story"
-      - If item cannot be resolved from any source: display with raw identifier, type "unknown", status "unknown"
-    - If resolved item status is "done", increment {{total_done_in_sprints}}
-    - Build capacity bar: `[===---]` style where `=` represents filled slots and `-` represents remaining capacity
+<step n="2" goal="Load sprint-status.yaml for user story execution statuses">
+  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
+  <check if="file not found">
+    <output>⚠️ `sprint-status.yaml` not found. User story execution statuses will not be available. Run `/sprint-planning` to initialize.</output>
+    <action>Set {{story_status_map}} = {} (empty — will show data integrity warnings per missing item)</action>
+  </check>
+  <check if="file found">
+    <action>Parse development_status section into {{story_status_map}} — key: story key, value: status</action>
+    <action>Exclude epic-* keys and *-retrospective keys from the map</action>
+  </check>
+</step>
+
+<step n="3" goal="Discover bug stories for type/severity data">
+  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` to discover all bug story files</action>
+  <check if="no bug files found">
+    <action>Set {{bug_metadata_map}} = {} (empty)</action>
+  </check>
+  <check if="bug files found">
+    <action>For each bug file, parse YAML frontmatter to extract: type, severity, title</action>
+    <action>Build {{bug_metadata_map}} — key: file basename (e.g., `bug-login-crash`), value: {severity, title}</action>
+  </check>
+</step>
+
+<step n="4" goal="Display sprint status for each sprint">
+  <action>For each sprint in {{sprint_plans}} (in order):</action>
+  <action>Calculate: {{assigned_count}} = length(sprint.assigned_items)</action>
+  <action>Calculate: {{remaining_capacity}} = sprint.capacity - {{assigned_count}}</action>
+
+  <action>For each item identifier in sprint.assigned_items, resolve item details:
+
+    **If item is a story (key matches regex `^\d+-\d+-.+`):**
+    - Look up status in {{story_status_map}}[item_key]
+    - If NOT found in {{story_status_map}}:
+      → Record as DATA INTEGRITY WARNING: "Item {item_key} has no status entry in sprint-status.yaml — run /sprint-planning to initialize status tracking for this item."
+      → Display item with marker: ⚠️ [status unknown]
+    - If found: display with current status label
+
+    **If item is a bug (key matches regex `^bug-.+`):**
+    - Look up in {{bug_metadata_map}}[item_key]
+    - If NOT found: display with title as item_key, severity as "unknown"
+    - If found: display with title and severity from frontmatter
+    - Bug execution status: use `status` from bug file frontmatter if present; otherwise "not-started"
+
+    **If item matches neither pattern:** display as type "Unknown" with raw identifier as title
   </action>
 
-  <action>Display non-closed sprints:</action>
   <output>
-{{#each non_closed_sprints}}
 ---
 
-## {{sprint.name}} ({{sprint.status}}) -- {{item_count}}/{{sprint.capacity}} items
+## 🏃 {{sprint.sprint_name}} (Sprint {{sprint.sprint_number}})
 
-{{#if sprint.start}}**Start:** {{sprint.start}}{{/if}}{{#if sprint.end}} | **End:** {{sprint.end}}{{/if}}
+**Status:** {{sprint.status}} | **Capacity:** {{sprint.capacity}} items | **Assigned:** {{assigned_count}} | **Remaining:** {{remaining_capacity}}
+{{#if sprint.start_context}}**Start:** {{sprint.start_context}}{{/if}} {{#if sprint.end_context}}| **End:** {{sprint.end_context}}{{/if}}
 
-| Item | Type | Status |
-|---|---|---|
-{{#each resolved_items}}
-| {{id}} | {{#if is_story}}[story]{{/if}}{{#if is_bug}}[bug, {{severity}}]{{/if}} | {{status}} |
-{{/each}}
-{{#if items_empty}}
-*(No items assigned)*
+{{#if over_capacity}}
+⚠️ **Over capacity by {{overage}} item(s)**
 {{/if}}
 
-**Capacity:** {{capacity_bar}}
+### Assigned Items
+
+| Item | Title | Type | Status / Severity |
+|---|---|---|---|
+{{#each resolved_items}}
+{{#if is_story}}
+| {{item_key}} | {{title}} | 📋 Story | {{status}} |
+{{/if}}
+{{#if is_bug}}
+| {{item_key}} | {{title}} | 🐛 Bug | Severity: {{severity}} / {{bug_status}} |
+{{/if}}
 {{/each}}
-  </output>
 
-  <action>Display closed sprints:</action>
-  <output>
-{{#each closed_sprints}}
----
-**{{sprint.name}}** (closed) -- {{item_count}} items completed
+{{#if data_integrity_warnings}}
+**⚠️ Data Integrity Warnings:**
+{{#each data_integrity_warnings}}
+- {{this}}
 {{/each}}
+{{/if}}
+
+{{#if assigned_items_empty}}
+*(No items assigned to this sprint)*
+{{/if}}
   </output>
 </step>
 
-<step n="4" goal="Completed items summary">
-  <action>Count items with status "done" that are still present in non-closed sprint files (use {{total_done_in_sprints}} from step 3)</action>
-  <check if="total_done_in_sprints > 0">
-    <output>
+<step n="5" goal="Display unassigned backlog summary">
+  <action>Collect all item keys from {{story_status_map}} that are NOT in any sprint's assigned_items list — these are unassigned user stories</action>
+  <action>Collect all bug basenames from {{bug_metadata_map}} that are NOT in any sprint's assigned_items list — these are unassigned bugs</action>
+  <action>Count unassigned stories by status: {{unassigned_by_status}}</action>
+  <output>
 ---
 
-## Completed Items
+## 📦 Unassigned Backlog
 
-{{total_done_in_sprints}} done item(s) are still in sprint files. Run `/cleanup-done` to archive them and free capacity.
-    </output>
-  </check>
-  <check if="total_done_in_sprints == 0">
-    <action>Skip this section -- no done items lingering in sprints</action>
-  </check>
-</step>
+### 📋 Unassigned Stories
 
-<step n="5" goal="Unassigned backlog">
-  <action>Filter {{backlog_items}} to find items where sprint is null (unassigned)</action>
-  <action>Exclude items with status "done" from the unassigned list</action>
-  <action>Sort unassigned items by priority ascending (lowest number = highest priority)</action>
-  <action>Store as {{unassigned_items}}</action>
-  <action>Store total count as {{unassigned_total}}</action>
-  <action>Take top 15 items for display as {{unassigned_display}}</action>
+| Status | Count |
+|---|---|
+| backlog | {{count_backlog}} |
+| ready-for-dev | {{count_ready}} |
+| in-progress | {{count_in_progress}} |
+| review | {{count_review}} |
+| done | {{count_done}} |
 
-  <check if="unassigned_total > 0">
-    <output>
----
+*Total unassigned stories: {{total_unassigned}}*
 
-## Unassigned Backlog
+### 🐛 Unassigned Bugs
 
-| # | Item | Type | Priority | Status |
-|---|---|---|---|---|
-{{#each unassigned_display}}
-| {{priority}} | {{id}} | {{type}} | {{priority}} | {{status}} |
+{{#if unassigned_bugs}}
+| ID / File | Title | Severity |
+|---|---|---|
+{{#each unassigned_bugs}}
+| {{id}} | {{title}} | {{severity}} |
 {{/each}}
-{{#if unassigned_total > 15}}
-
-... and {{unassigned_total - 15}} more
+{{else}}
+*(No unassigned bugs)*
 {{/if}}
-    </output>
-  </check>
-  <check if="unassigned_total == 0">
-    <output>
----
-
-## Unassigned Backlog
 
-*(All backlog items are assigned to sprints)*
-    </output>
-  </check>
+**Tip:** Use `/add-to-sprint` to assign unassigned items to a sprint.
+  </output>
 </step>
 
-<step n="6" goal="Next actions menu">
-  <ask>
-**Next Actions:**
-[1] Full backlog
-[2] /add-to-sprint
-[3] /remove-from-sprint
-[4] /prioritize-backlog
-[5] /add-sprint
-[6] /cleanup-done
-[7] Exit
-
-Choice:
-  </ask>
+<step n="6" goal="Offer next actions">
+  <ask>Options:
+1. Show full unassigned backlog item list (IDs + titles + statuses)
+2. Add items to a sprint — run `/add-to-sprint`
+3. Modify a sprint — run `/modify-sprint`
+4. Create a new sprint — run `/add-sprint`
+5. Exit
+
+Choice:</ask>
   <check if="choice == 1">
-    <action>Display all items from {{backlog_items}} in a table: id, type, priority, status, sprint, severity</action>
+    <action>For each unassigned story key in {{story_status_map}} not assigned to any sprint, display: key, inferred title, status</action>
+    <action>For each unassigned bug in {{bug_metadata_map}} not assigned to any sprint, display: id, title, severity</action>
+    <output>
+### Full Unassigned Backlog
+
+**Stories:**
+| Key | Title | Status |
+|---|---|---|
+{{#each unassigned_story_items}}
+| {{key}} | {{title}} | {{status}} |
+{{/each}}
+
+**Bugs:**
+| ID | Title | Severity |
+|---|---|---|
+{{#each unassigned_bugs}}
+| {{id}} | {{title}} | {{severity}} |
+{{/each}}
+    </output>
     <goto step="6" />
   </check>
   <check if="choice == 2">
-    <output>Run `/add-to-sprint` to assign backlog items to a sprint.</output>
+    <output>▶️ Run `/add-to-sprint` to assign backlog items to a sprint.</output>
   </check>
   <check if="choice == 3">
-    <output>Run `/remove-from-sprint` to remove items from a sprint.</output>
+    <output>▶️ Run `/modify-sprint` to add/remove items or change sprint settings.</output>
   </check>
   <check if="choice == 4">
-    <output>Run `/prioritize-backlog` to reorder backlog priorities.</output>
+    <output>▶️ Run `/add-sprint` to create a new sprint.</output>
   </check>
   <check if="choice == 5">
-    <output>Run `/add-sprint` to create a new sprint.</output>
-  </check>
-  <check if="choice == 6">
-    <output>Run `/cleanup-done` to archive completed items from sprints.</output>
-  </check>
-  <check if="choice == 7">
     <action>Exit workflow</action>
   </check>
 </step>
 
-<step n="7" goal="Regenerate sprint-status.yaml (internal)" internal="true">
-  <action>This step runs automatically after display (steps 3-6) completes, before the workflow exits.</action>
-
-  <action>Read existing `_bmad-output/implementation-artifacts/sprint-status.yaml` if it exists</action>
-  <action>Preserve the STATUS DEFINITIONS comment block at the top of the file (lines starting with `#` that define status values)</action>
-  <action>Preserve any epic-* keys and *-retrospective keys from the existing file</action>
-
-  <action>Build the new development_status section:
-    - Source 1: {{backlog_items}} from backlog.yaml -- for each item where status is NOT "done", add an entry: key = item.id, value = item.status
-    - Source 2: sprint entity files -- for each sprint, for each item in sprint.items, ensure the item has an entry. If the item was already added from backlog.yaml, the backlog value wins. If the item is NOT in backlog.yaml, look up status from {{bug_metadata_map}} or {{status_fallback_map}}.
-    - Exclude items with status "done" -- only non-done items appear in sprint-status.yaml
-  </action>
-
-  <action>Collect sprint metadata for header comments:
-    - For each sprint: id, name, status, item count, capacity
-  </action>
-
-  <action>Get current ISO timestamp as {{generated_at}}</action>
-
-  <action>Write `_bmad-output/implementation-artifacts/sprint-status.yaml` with this structure:
-
-```yaml
-# generated: {{original_generated_date or generated_at}}
-# updated: {{generated_at}} — regenerated by sprint-status-view
-# project: {{project_name from existing file or "unknown"}}
-# project_key: {{project_key from existing file or "NOKEY"}}
-# tracking_system: file-system
-# story_location: _bmad-output/implementation-artifacts
-#
-# Sprints:
-{{#each sprints}}
-#   {{sprint.id}}: {{sprint.name}} ({{sprint.status}}) — {{item_count}}/{{sprint.capacity}} items
-{{/each}}
-#
-# STATUS DEFINITIONS:
-# ==================
-# (preserve the full STATUS DEFINITIONS block from the existing file verbatim)
-# If no existing file, use these defaults:
-# backlog        — item is in the backlog, not yet started
-# ready-for-dev  — story file created, ready for development
-# in-progress    — item is actively being worked on
-# review         — item is in review
-# done           — item is complete (excluded from this file)
-
-{{#if preserved_epic_keys}}
-# Epic tracking
-{{#each preserved_epic_keys}}
-{{key}}: {{value}}
-{{/each}}
-{{/if}}
-
-development_status:
-{{#each active_items}}
-  {{id}}: {{status}}
-{{/each}}
-
-{{#if preserved_retro_keys}}
-# Retrospective tracking
-{{#each preserved_retro_keys}}
-{{key}}: {{value}}
-{{/each}}
-{{/if}}
-```
-
-  </action>
-</step>
-
 </workflow>