ma-agents 3.4.9 → 3.5.0

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

@@ -1,202 +1,177 @@
 ---
 name: sprint-status-view
-description: Display sprint progress with assigned items, type distinction, and remaining capacity
+description: Display formatted sprint progress, backlog, and epic status from the unified sprint-status.yaml
 type: skill
 triggers:
   - "sprint status view"
   - "view sprint status"
+  - "/sprint-status-view"
 ---
 
-# Sprint Status View Workflow
-
-Extension workflow that displays sprint progress with assigned items (stories + bugs), type distinction, and remaining capacity.
-
-> **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/`.
-
-<workflow>
-
-<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 Sprints Found**
-
-No sprint plan files exist yet (`sprint-plan-*.yaml`).
-
-**To get started:**
-- 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="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>
-
-  <output>
+# Sprint Status View
+
+Display a formatted, read-only dashboard of all sprint, backlog, and epic data from the unified `sprint-status.yaml` file.
+
+> **READ-ONLY SKILL:** This skill NEVER writes to `sprint-status.yaml` or any other file. It is purely a display/reporting skill.
+
+---
+
+## Step 1 — Load sprint-status.yaml
+
+Resolve the path to `sprint-status.yaml` using the BMAD config:
+- Check `_bmad/bmm/config.yaml` for `sprint_management_path` (if configured for multi-repo mode)
+- Default path: `_bmad-output/implementation-artifacts/sprint-status.yaml`
+
+Read the file. If it does not exist:
+- Output: "No sprint-status.yaml found. Run `/bmad-sprint-planning` to initialize."
+- Exit without error.
+
+Parse all sections from the file:
+- **Metadata:** `project`, `last_updated` (plus `generated`, `project_key`, `tracking_system`, `story_location` if present)
+- **`epics`** — map of epic entries (keys: `epic-N`)
+- **`backlog`** — array of unassigned item objects
+- **`sprints`** — map of sprint entries (keys: `sprint-N`)
+
+If the file exists but uses the old flat `development_status` schema (no `epics`/`backlog`/`sprints` sections), output:
+"sprint-status.yaml uses the pre-Epic-17 schema. Run `/bmad-sprint-planning` to migrate to the unified schema."
+Then exit.
+
+---
+
+## Step 2 — Classify Sprints
+
+Partition the `sprints` map into three groups:
+- **active** — entries where `status: active`
+- **planning** — entries where `status: planning`
+- **closed** — entries where `status: closed`
+
+Sort each group by sprint key (`sprint-N`) ascending by numeric value of N.
+
+---
+
+## Step 3 — Render Header
+
+Output:
+
+```
+# Sprint Status — {project}
+*Last updated: {last_updated}*
+
 ---
+```
+
+---
+
+## Step 4 — Render Active Sprints
+
+If there are active sprints, output a `## Active Sprints` section header.
+
+For each active sprint (sorted by key ascending):
+
+1. Sprint header:
+   ```
+   ### {sprint.name}
+   **Status:** active | **Capacity:** {items.length} / {capacity} | **Start:** {start or "—"} | **End:** {end or "—"}
+   ```
+   If `items.length > capacity`, append inline: `⚠️ over capacity by {items.length - capacity} item(s)`
+
+2. Items table (if items array is non-empty):
+   ```
+   | Item | Title | Type | Status | Severity |
+   |------|-------|------|--------|----------|
+   | {id} | {title} | Story | {status} | — |
+   | {id} | {title} | Bug   | {status} | {severity} |
+   ```
+   - Type column: use "Story" for `type: story`, "Bug" for `type: bug`
+   - Severity column: show severity value for bugs, "—" for stories
+
+3. If items array is empty, output: `*(No items assigned to this sprint)*`
 
-## 🏃 {{sprint.sprint_name}} (Sprint {{sprint.sprint_number}})
-
-**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}}
-
-{{#if over_capacity}}
-⚠️ **Over capacity by {{overage}} item(s)**
-{{/if}}
-
-### 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}}
-
-{{#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="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>
 ---
 
-## 📦 Unassigned Backlog
-
-### 📋 Unassigned Stories
-
-| Status | Count |
-|---|---|
-| backlog | {{count_backlog}} |
-| ready-for-dev | {{count_ready}} |
-| in-progress | {{count_in_progress}} |
-| review | {{count_review}} |
-| done | {{count_done}} |
-
-*Total unassigned stories: {{total_unassigned}}*
-
-### 🐛 Unassigned Bugs
-
-{{#if unassigned_bugs}}
-| ID / File | Title | Severity |
-|---|---|---|
-{{#each unassigned_bugs}}
-| {{id}} | {{title}} | {{severity}} |
-{{/each}}
-{{else}}
-*(No unassigned bugs)*
-{{/if}}
-
-**Tip:** Use `/add-to-sprint` to assign unassigned items to a sprint.
-  </output>
-</step>
-
-<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>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>
-  </check>
-  <check if="choice == 3">
-    <output>▶️ Run `/modify-sprint` to add/remove items or change sprint settings.</output>
-  </check>
-  <check if="choice == 4">
-    <output>▶️ Run `/add-sprint` to create a new sprint.</output>
-  </check>
-  <check if="choice == 5">
-    <action>Exit workflow</action>
-  </check>
-</step>
-
-</workflow>
+## Step 5 — Render Planning Sprints
+
+If there are planning sprints, output a `## Planning Sprints` section header.
+
+For each planning sprint (sorted by key ascending), use the same format as Step 4 with `status: planning`.
+
+---
+
+## Step 6 — Render Closed Sprint Summaries
+
+If there are closed sprints, output a `## Closed Sprints` section header followed by a summary table:
+
+```
+| Sprint | Items | Start | End |
+|--------|-------|-------|-----|
+| {sprint.name} | {items.length} items (archived) | {start or "—"} | {end or "—"} |
+```
+
+Do NOT list individual items within closed sprints (collapsed view by default).
+
+---
+
+## Step 7 — Render Backlog
+
+Count total backlog items: `{backlog.length}`.
+
+Output a `## Backlog — {backlog.length} items` section header.
+
+If backlog is empty, output: `*(No items in backlog)*`
+
+Otherwise, output a table in array order (position = priority):
+
+```
+| # | Item | Title | Type | Status | Severity |
+|---|------|-------|------|--------|----------|
+| 1 | {id} | {title} | Story | {status} | — |
+| 2 | {id} | {title} | Bug   | {status} | {severity} |
+```
+
+- `#` column: 1-based position in the array (= priority rank)
+- Severity column: show severity for bugs, "—" for stories
+
+---
+
+## Step 8 — Render Epics Overview
+
+Output a `## Epics` section header.
+
+If the `epics` map is empty, output: `*(No epics defined)*`
+
+Otherwise, for each epic in the map (sorted by key ascending by numeric value of N):
+
+1. Count items referencing this epic across all sections:
+   - Scan `backlog` items where `epic == N` (N = epic number, e.g., `17` for `epic-17`)
+   - Scan all `sprints[*].items` where `epic == N`
+   - Tally counts by status
+
+2. Output a table row:
+   ```
+   | Epic | Status | Retrospective | Items (active) |
+   |------|--------|---------------|----------------|
+   | epic-4 | on-hold | optional | {count} total ({status breakdown}) |
+   ```
+   - Status breakdown: list non-zero status counts, e.g., "2 in-progress, 1 ready-for-dev"
+   - If no items reference the epic, show "0 total"
+   - `retrospective` field: show value or "—" if null
+
+---
+
+## Step 9 — Render Alerts (Conditional)
+
+Scan for alert conditions:
+
+1. **Over-capacity sprints:** Any sprint where `items.length > capacity`
+   - Alert: `Over capacity: {sprint.name} is over capacity by {items.length - capacity} item(s) ({items.length} / {capacity})`
+
+2. **Stale in-progress items:** Items with `status: in-progress` in **active** sprints where the sprint's `start` date is more than 14 days before today
+   - Alert: `Stale in-progress: {item.id} has been in-progress for {N} days ({sprint.name} started {start})`
+
+3. **Empty active sprints:** Active sprints with zero items
+   - Alert: `Empty active sprint: {sprint.name} is active but has no items assigned`
+
+If NO alert conditions exist, omit this section entirely (do not output "No alerts" or any placeholder).
+
+If alerts exist, output a `## Alerts` section header followed by a bulleted list.
+

package/lib/bmad-extension/workflows/add-sprint/workflow.md

@@ -1,111 +1,165 @@
 # Add Sprint Workflow
 
-Guided workflow to create a new sprint with capacity limits for realistic sprint planning.
+Guided workflow to create a new sprint entry in the `sprints` section of `sprint-status.yaml` with capacity limits, optional ISO dates, and auto-incremented sprint ID.
 
 <workflow>
 
-<step n="1" goal="Gather sprint number and name">
-  <action>Ask the user for the sprint number (e.g., 1, 2, 3)</action>
-  <ask>What is the sprint number? (e.g., 1)</ask>
-  <action>Store as {{sprint_number}}</action>
-  <ask>What is the sprint name? (e.g., "Sprint 1 — Foundation") — press Enter to use "Sprint {{sprint_number}}"</ask>
-  <action>If user presses Enter or leaves blank, default to "Sprint {{sprint_number}}"</action>
-  <action>Store as {{sprint_name}}</action>
+<step n="0" goal="Load configuration and validate file existence">
+  <action>Resolve the path to `sprint-status.yaml`. Check `_bmad/bmm/config.yaml` for a configured `story_location` path; if not set, default to `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
+  <action>Attempt to read the file at the resolved path</action>
+  <check if="sprint-status.yaml does not exist">
+    <output>No sprint-status.yaml found. Run sprint planning first to initialize the file.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Read and parse the full file: `epics`, `backlog`, and `sprints` sections plus all metadata fields</action>
+  <action>Store parsed content as {{file_content}}</action>
 </step>
 
-<step n="2" goal="Gather capacity as positive integer">
-  <action>Explain capacity: the maximum number of items (stories + bugs) that can be assigned to this sprint</action>
-  <ask>What is the sprint capacity? (Enter a positive integer — the maximum number of stories/bugs for this sprint)</ask>
+<step n="1" goal="Auto-increment sprint ID and derive default name">
+  <action>Extract all keys from the `sprints` map in {{file_content}}</action>
+  <action>Parse numeric suffix from each key matching pattern `sprint-N` (e.g., `sprint-1` → 1, `sprint-3` → 3)</action>
+  <check if="no sprint keys exist in sprints map">
+    <action>Set {{new_number}} = 1</action>
+    <action>Set {{default_name}} = "Sprint 1"</action>
+  </check>
+  <check if="sprint keys exist">
+    <action>Find the highest numeric suffix among all sprint keys; store as {{max_number}}</action>
+    <action>Set {{new_number}} = {{max_number}} + 1</action>
+    <action>Look up the sprint entry whose key has suffix {{max_number}}; read its `name` field</action>
+    <action>If the name matches pattern "Sprint N" or "Sprint N — description" or "Sprint N - description", set {{default_name}} = "Sprint {{new_number}}"; otherwise set {{default_name}} = "Sprint {{new_number}}" as safe fallback</action>
+  </check>
+  <action>Set {{sprint_id}} = "sprint-{{new_number}}"</action>
+  <action>Set {{sprint_name}} = {{default_name}}</action>
+  <output>
+Auto-generated Sprint ID: **{{sprint_id}}**
+Default Sprint Name: **{{sprint_name}}**
+  </output>
+  <ask>Sprint ID: {{sprint_id}} — press Enter to accept or type a different number:</ask>
+  <check if="user provides a different number">
+    <action>Set {{sprint_id}} = "sprint-{user_number}"</action>
+    <action>Check if {{sprint_id}} already exists as a key in the `sprints` map</action>
+    <check if="sprint_id already exists">
+      <output>Sprint ID {{sprint_id}} already exists in sprint-status.yaml. Please choose a different number.</output>
+      <goto step="1" sub="re-prompt for number only" />
+    </check>
+    <action>Update {{sprint_name}} default to "Sprint {user_number}"</action>
+  </check>
+  <ask>Sprint name: '{{sprint_name}}' — press Enter to accept or type a different name:</ask>
+  <check if="user provides a different name">
+    <action>Set {{sprint_name}} = user input</action>
+  </check>
+</step>
+
+<step n="2" goal="Gather capacity (required)">
+  <action>Explain: capacity is the maximum number of items (stories + bugs) that can be assigned to this sprint. This is advisory — skills will warn but not block when exceeded (per schema section 4.2).</action>
+  <ask>What is the sprint capacity? (Enter a positive integer)</ask>
   <action>Store input as {{capacity_input}}</action>
   <action>Validate {{capacity_input}} is a positive integer (greater than zero, no decimals, no non-numeric characters)</action>
   <check if="{{capacity_input}} is NOT a positive integer">
-    <output>❌ Invalid capacity: "{{capacity_input}}". Capacity must be a positive integer (e.g., 5, 10, 20). Zero and negative values are not allowed.</output>
+    <output>Invalid capacity: "{{capacity_input}}". Capacity must be a positive integer (e.g., 5, 10, 20). Zero and negative values are not allowed.</output>
     <goto step="2" />
   </check>
   <action>Store as {{capacity}} (integer)</action>
 </step>
 
-<step n="3" goal="Gather optional start and end context">
-  <action>Explain: start/end context can be dates (e.g., "2026-03-18") or milestone descriptions (e.g., "Q1 Planning Complete")</action>
-  <ask>Optional — Sprint start context (date or milestone, press Enter to skip):</ask>
-  <action>Store as {{start_context}} (empty string if skipped)</action>
-  <ask>Optional — Sprint end context (date or milestone, press Enter to skip):</ask>
-  <action>Store as {{end_context}} (empty string if skipped)</action>
+<step n="3" goal="Gather optional start and end dates">
+  <ask>Optional — Sprint start date (ISO format YYYY-MM-DD, press Enter to skip):</ask>
+  <action>Store as {{start_input}}</action>
+  <check if="start_input is not empty">
+    <action>Validate {{start_input}} matches ISO date pattern YYYY-MM-DD (4-digit year, 2-digit month 01-12, 2-digit day 01-31)</action>
+    <check if="start_input does not match ISO date pattern">
+      <output>Invalid date format: "{{start_input}}". Please use YYYY-MM-DD (e.g., 2026-04-15).</output>
+      <goto step="3" sub="re-prompt for start date only" />
+    </check>
+    <action>Store as {{start}} = {{start_input}}</action>
+  </check>
+  <check if="start_input is empty">
+    <action>Store as {{start}} = "" (empty string)</action>
+  </check>
+  <ask>Optional — Sprint end date (ISO format YYYY-MM-DD, press Enter to skip):</ask>
+  <action>Store as {{end_input}}</action>
+  <check if="end_input is not empty">
+    <action>Validate {{end_input}} matches ISO date pattern YYYY-MM-DD</action>
+    <check if="end_input does not match ISO date pattern">
+      <output>Invalid date format: "{{end_input}}". Please use YYYY-MM-DD (e.g., 2026-04-28).</output>
+      <goto step="3" sub="re-prompt for end date only" />
+    </check>
+    <check if="end_input is before start and start is not empty">
+      <output>Warning: end date {{end_input}} is before start date {{start}}. Continuing as requested.</output>
+    </check>
+    <action>Store as {{end}} = {{end_input}}</action>
+  </check>
+  <check if="end_input is empty">
+    <action>Store as {{end}} = "" (empty string)</action>
+  </check>
 </step>
 
-<step n="4" goal="Confirm and validate all inputs">
+<step n="4" goal="Confirmation">
   <output>
-## Sprint Summary — Please Confirm
+## New Sprint Summary — Please Confirm
 
-- **Sprint Number:** {{sprint_number}}
-- **Sprint Name:** {{sprint_name}}
-- **Capacity (max items):** {{capacity}}
-- **Start Context:** {{start_context}} *(empty if skipped)*
-- **End Context:** {{end_context}} *(empty if skipped)*
-- **Output File:** `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`
+- Sprint ID: {{sprint_id}}
+- Sprint Name: {{sprint_name}}
+- Capacity: {{capacity}} items
+- Start Date: {{start}} *(empty if skipped)*
+- End Date: {{end}} *(empty if skipped)*
+- Status: planning
+- Items: [] *(empty — use /add-to-sprint to assign items)*
+- Target: sprint-status.yaml sprints section
   </output>
-  <ask>Confirm creation? [y] Yes / [n] Cancel / [e] Edit a field:</ask>
+  <ask>Confirm creation? [y] Yes / [n] Cancel / [e] Edit a field</ask>
   <check if="user selects 'e'">
-    <ask>Which field to edit? (number / name / capacity / start / end)</ask>
-    <check if="field == 'number'">
-      <ask>New sprint number:</ask>
-      <action>Store as {{sprint_number}}</action>
-      <action>If sprint name was auto-defaulted to the old "Sprint {n}", update it to "Sprint {{sprint_number}}"</action>
-      <goto step="4" />
-    </check>
+    <ask>Which field to edit? (id / name / capacity / start / end)</ask>
+    <check if="field == 'id'"><goto step="1" /></check>
     <check if="field == 'name'">
-      <ask>New sprint name (or press Enter to use "Sprint {{sprint_number}}"):</ask>
-      <action>If blank, set {{sprint_name}} = "Sprint {{sprint_number}}"; else store user input as {{sprint_name}}</action>
+      <ask>Sprint name (or press Enter to use "{{sprint_name}}"):</ask>
+      <check if="input is not empty"><action>Set {{sprint_name}} = user input</action></check>
       <goto step="4" />
     </check>
     <check if="field == 'capacity'"><goto step="2" /></check>
-    <check if="field == 'start'"><goto step="3" /></check>
-    <check if="field == 'end'"><goto step="3" /></check>
+    <check if="field == 'start'"><goto step="3" sub="start date only" /></check>
+    <check if="field == 'end'"><goto step="3" sub="end date only" /></check>
   </check>
   <check if="user selects 'n'">
-    <output>❌ Sprint creation cancelled.</output>
+    <output>Sprint creation cancelled.</output>
     <action>Exit workflow</action>
   </check>
 </step>
 
-<step n="5" goal="Generate sprint artifact file">
-  <action>Determine output path: `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`</action>
-  <action>Check if file already exists at output path</action>
-  <check if="file already exists">
-    <output>⚠️ A sprint plan already exists at `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`.</output>
-    <ask>Overwrite existing sprint plan? [y] Yes / [n] Cancel:</ask>
-    <check if="user selects 'n'">
-      <output>❌ Sprint creation cancelled to preserve existing sprint plan.</output>
-      <action>Exit workflow</action>
-    </check>
-  </check>
-  <action>Get current ISO timestamp for created_date and last_modified</action>
-  <action>Write sprint artifact YAML to `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml` with this structure:
-
+<step n="5" goal="Write sprint entry to sprint-status.yaml">
+  <action>Re-read the current content of `sprint-status.yaml` (resolved path from Step 0) to get the latest state</action>
+  <action>Get the current ISO-8601 timestamp for `last_updated`</action>
+  <action>Append a new entry to the `sprints` map with this structure:
 ```yaml
-sprint_number: {{sprint_number}}
-sprint_name: "{{sprint_name}}"
-capacity: {{capacity}}
-assigned_items: []
-status: planning
-start_context: "{{start_context}}"
-end_context: "{{end_context}}"
-created_date: "{{current_iso_timestamp}}"
-last_modified: "{{current_iso_timestamp}}"
+  {{sprint_id}}:
+    name: "{{sprint_name}}"
+    status: planning
+    capacity: {{capacity}}
+    start: "{{start}}"
+    end: "{{end}}"
+    items: []
 ```
   </action>
+  <action>Preserve the `epics` section unchanged</action>
+  <action>Preserve the `backlog` section unchanged</action>
+  <action>Preserve all existing entries in the `sprints` section unchanged</action>
+  <action>Update the `last_updated` metadata field to the current ISO-8601 timestamp</action>
+  <action>Preserve the `generated` field unchanged (never modify)</action>
+  <action>Write the complete updated file in a single atomic write (read-modify-write pattern)</action>
+</step>
+
+<step n="6" goal="Summary output">
   <output>
-✅ **Sprint created successfully!**
+Sprint created successfully!
 
-- **File:** `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`
-- **Sprint:** {{sprint_name}}
-- **Capacity:** {{capacity}} items
-- **Status:** planning
+- Sprint: {{sprint_name}} ({{sprint_id}})
+- Capacity: {{capacity}} items
+- Status: planning
 
-**Next Steps:**
-- Use `/add-to-sprint` to assign backlog items to this sprint
-- Use `/modify-sprint` to update sprint details later
-- Use `/sprint-status-view` to view sprint progress
+Next Steps:
+- Use /add-to-sprint to assign backlog items to this sprint
+- Use /modify-sprint to update sprint details later
+- Use /sprint-status-view to view sprint progress
   </output>
 </step>