ma-agents 3.1.0 → 3.2.0

package/lib/bmad-extension/skills/generate-backlog/SKILL.md

@@ -0,0 +1,183 @@
+---
+name: generate-backlog
+description: Generate or refresh a flat backlog.yaml from epics and bug stories, preserving existing priority and sprint assignments
+type: skill
+triggers:
+  - "generate backlog"
+  - "refresh backlog"
+---
+
+# Generate Backlog Workflow
+
+Generate or refresh a flat `backlog.yaml` from epic stories and bug reports. Preserves existing priority and sprint assignments, appends new items, removes stale items, and re-numbers priorities 1..N.
+
+<workflow>
+
+<step n="1" goal="Load sources">
+  <action>Read `_bmad-output/planning-artifacts/epics.md` — this is the master list of epics with their stories.</action>
+  <check if="epics.md does not exist">
+    <output>**Error:** `_bmad-output/planning-artifacts/epics.md` not found. Cannot generate backlog without an epics file.</output>
+    <action>Exit workflow</action>
+  </check>
+
+  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` to discover all bug story files.</action>
+  <action>Store the list of bug files as {{bug_files}} (may be empty — zero bugs is valid).</action>
+
+  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml` if it exists — this provides the current status of each story (done, in-progress, backlog, etc.).</action>
+  <action>Store the status map as {{status_map}} (keyed by story id). If the file does not exist, use an empty map.</action>
+
+  <action>Read `_bmad-output/implementation-artifacts/backlog.yaml` if it exists — this is the existing backlog to merge with.</action>
+  <action>Store the existing backlog items as {{existing_items}} (list). If the file does not exist, use an empty list.</action>
+
+  <output>
+**Sources loaded:**
+- epics.md: found
+- Bug files: {{bug_files | length}} file(s)
+- sprint-status.yaml: {{status_map exists ? "found" : "not found (empty status)"}}
+- Existing backlog.yaml: {{existing_items | length}} item(s)
+  </output>
+</step>
+
+<step n="2" goal="Extract stories from epics">
+  <action>Parse `epics.md` to extract every story from every epic. Each epic is a level-2 heading (`## Epic N: ...`) and each story within it is a level-3 heading (`### Story N.M: ...`) or a list item following the pattern `- **Story N.M:** Title` or `- N.M: Title`.</action>
+
+  <action>For each story found:
+    - Derive {{story_id}} as a kebab-case slug: `"{epic_number}-{story_number}-{title_slug}"` (e.g., `"5-5-explicit-parameter-passing"`)
+      - Title slug: lowercase, replace spaces/underscores with hyphens, remove non-alphanumeric/non-hyphen characters, collapse consecutive hyphens, trim leading/trailing hyphens
+    - Set {{epic}} to the epic number (integer)
+    - Set {{title}} to the story title text
+    - Look up status from {{status_map}} using the story identifier. If found and status is `done`, skip this story (exclude from backlog). If found, use that status. If not found, default to `backlog`.
+    - Set {{type}} = `story`
+    - Set {{severity}} = `null`
+    - Set {{sprint}} = `null`
+    - Set {{priority}} = `null` (will be assigned during merge/sort)
+  </action>
+
+  <action>Store the extracted stories as {{extracted_stories}} list.</action>
+  <output>Extracted {{extracted_stories | length}} active stories from epics (done items excluded).</output>
+</step>
+
+<step n="3" goal="Extract bugs">
+  <action>For each file in {{bug_files}}:
+    - Read the file and parse the YAML frontmatter (between `---` delimiters)
+    - Extract `title`, `severity`, and `status` from frontmatter
+    - Derive {{bug_id}} from the **filename**, not the title: strip the `bug-` prefix and `.md` extension, then uppercase to `"BUG-{slug}"` (e.g., `bug-login-crash.md` → `BUG-login-crash`)
+    - Use `status` from frontmatter directly (bugs track their own status). If `status` is missing, default to `backlog`. If status is `done`, skip this bug (exclude from backlog).
+    - Build a backlog item:
+      - id: {{bug_id}}
+      - type: `bug`
+      - epic: `null`
+      - title: {{title}}
+      - priority: `null` (assigned during merge/sort)
+      - status: {{frontmatter_status or "backlog"}}
+      - sprint: `null`
+      - severity: {{severity}}
+  </action>
+
+  <action>Store the extracted bugs as {{extracted_bugs}} list.</action>
+  <output>Extracted {{extracted_bugs | length}} active bugs (done items excluded).</output>
+</step>
+
+<step n="4" goal="Merge with existing backlog">
+  <action>Combine {{extracted_stories}} and {{extracted_bugs}} into {{new_items}} list.</action>
+
+  <action>Build a lookup map from {{existing_items}} keyed by `id`.</action>
+
+  <action>For each item in {{new_items}}:
+    - If an item with the same `id` exists in {{existing_items}}:
+      - **Preserve** the existing `priority` value
+      - **Preserve** the existing `sprint` assignment
+      - **Update** `status` from the freshly extracted value (which may reflect sprint-status.yaml changes)
+      - **Update** `title`, `type`, `epic`, `severity` from the freshly extracted values (source of truth)
+    - If no matching item exists in {{existing_items}}:
+      - This is a new item — keep all freshly extracted values
+      - Set `priority` to `null` (will be placed at the end during sort)
+  </action>
+
+  <action>Identify stale items: any item in {{existing_items}} whose `id` does NOT appear in {{new_items}}. These items no longer exist in the source files and should be removed.</action>
+
+  <action>Store the final merged list as {{merged_items}}.</action>
+  <action>Store the count of new items added as {{new_count}}.</action>
+  <action>Store the count of stale items removed as {{stale_count}}.</action>
+  <action>Store the count of preserved items as {{preserved_count}}.</action>
+
+  <output>
+**Merge results:**
+- Preserved (existing): {{preserved_count}}
+- New items added: {{new_count}}
+- Stale items removed: {{stale_count}}
+  </output>
+</step>
+
+<step n="5" goal="Write backlog.yaml">
+  <action>Sort {{merged_items}} for final output:
+    1. Items WITH an existing numeric `priority` come first, sorted ascending by priority
+    2. Items WITHOUT a priority (`null`) come after, sorted by:
+       a. `type`: bugs before stories (bugs get priority attention)
+       b. `severity` for bugs: critical > high > medium > low
+       c. `epic` number ascending for stories (lower epics first)
+       d. `id` alphabetically as final tiebreaker
+  </action>
+
+  <action>Re-number priorities sequentially 1..N across all items in the sorted list.</action>
+
+  <action>Get current ISO timestamp as {{generated_at}}.</action>
+
+  <action>Write `_bmad-output/implementation-artifacts/backlog.yaml` with this structure:
+
+```yaml
+# Flat Backlog — auto-generated by generate-backlog
+# Generated: {{generated_at}}
+# Total items: {{merged_items | length}}
+#
+# Schema per item:
+#   id, type, epic, title, priority, status, sprint, severity
+
+backlog:
+  - id: "5-5-explicit-parameter-passing"
+    type: story
+    epic: 5
+    title: "Explicit Parameter Passing"
+    priority: 1
+    status: backlog
+    sprint: null
+    severity: null
+  # ... remaining items ...
+```
+
+  **YAML output rules:**
+  - Always quote `id` and `title` fields (they contain hyphens and special characters)
+  - `epic` is an integer for stories, `null` for bugs
+  - `sprint` is a string like `"sprint-3"` if assigned, or `null`
+  - `severity` is a string (`critical`, `high`, `medium`, `low`) for bugs, `null` for stories
+  - `status` is one of: `backlog`, `ready-for-dev`, `in-progress`, `review` (done items excluded)
+  - `priority` is always a positive integer (1 = highest priority)
+  - Use 2-space indentation for YAML
+  </action>
+
+  <output>Backlog written to `_bmad-output/implementation-artifacts/backlog.yaml` with {{merged_items | length}} items.</output>
+</step>
+
+<step n="6" goal="Report summary">
+  <output>
+## Backlog Generation Complete
+
+| Metric              | Count |
+|----------------------|-------|
+| Total items          | {{merged_items | length}} |
+| Stories              | {{story_count}} |
+| Bugs                 | {{bug_count}} |
+| New items added      | {{new_count}} |
+| Stale items removed  | {{stale_count}} |
+| Items preserved      | {{preserved_count}} |
+
+**Output:** `_bmad-output/implementation-artifacts/backlog.yaml`
+
+**Next Steps:**
+- Review priorities — new items are appended at the end; reorder as needed
+- Use `/add-to-sprint` to assign high-priority items to the current sprint
+- Use `/sprint-status-view` to see sprint progress
+  </output>
+</step>
+
+</workflow>

package/lib/bmad-extension/skills/generate-backlog/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: generate-backlog
+module: ma-skills

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

@@ -7,12 +7,75 @@ 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/prioritize-backlog/SKILL.md

@@ -0,0 +1,195 @@
+---
+name: prioritize-backlog
+description: Reprioritize backlog items using multiple criteria — severity, business value, dependencies, type, age
+type: skill
+triggers:
+  - "prioritize backlog"
+  - "reorder backlog"
+  - "reprioritize"
+---
+
+# Prioritize-Backlog Workflow
+
+Reprioritize backlog items using multiple criteria — severity, business value, dependencies, type, and age.
+
+<workflow>
+
+<step n="1" goal="Load backlog and dependency data">
+  <action>Read `_bmad-output/implementation-artifacts/backlog.yaml`</action>
+  <check if="file missing or empty (no items)">
+    <output>No backlog found or backlog is empty. Nothing to prioritize.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Store all backlog items as {{backlog_items}}</action>
+  <action>Infer implicit dependencies: stories belonging to the same epic are assumed to be sequential (lower story number before higher)</action>
+  <action>Read `_bmad-output/implementation-artifacts/epics.md` (or equivalent epics source) for any explicitly declared dependencies</action>
+  <action>Build {{dependency_map}} — for each item, list the IDs it depends on (must be completed before it can start)</action>
+</step>
+
+<step n="2" goal="Display current backlog ordering">
+  <output>
+## Current Backlog
+
+| # | Priority | ID | Title | Type | Epic | Status | Sprint | Severity | Dependencies |
+|---|---|---|---|---|---|---|---|---|---|
+{{#each backlog_items}}
+| {{@index+1}} | {{priority}} | {{id}} | {{title}} | {{type}} | {{epic}} | {{status}} | {{sprint}} | {{severity}} | {{dependencies}} |
+{{/each}}
+
+*Total: {{backlog_items.length}} items*
+  </output>
+</step>
+
+<step n="3" goal="Choose prioritization mode">
+  <ask>Choose prioritization mode:
+1. **Full reprioritization** — enter items in desired order, remaining appended at end
+2. **Quick adjust** — move individual items up/down
+3. **Auto-suggest** — AI analysis with weighted criteria
+4. **Cancel**
+
+Choice:</ask>
+  <check if="choice == 4">
+    <output>Cancelled. No changes made.</output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="3a" goal="Full reprioritization" if="choice == 1">
+  <ask>Enter item numbers in your desired priority order (comma-separated). Items not listed will be appended in their current relative order:</ask>
+  <action>Resolve entered numbers against the backlog table from step 2</action>
+  <action>Build {{new_order}}: user-specified items first (in given order), then remaining items appended in their original relative order</action>
+  <goto step="4" />
+</step>
+
+<step n="3b" goal="Quick adjust" if="choice == 2">
+  <action>Initialize {{new_order}} as a copy of the current {{backlog_items}} list (preserving current ordering)</action>
+  <ask>Select item number to move:</ask>
+  <action>Store selected item as {{item_to_move}}</action>
+  <ask>Move to:
+- Enter a position number (1 = top, N = bottom)
+- Or enter 'u' to move up one position, 'd' to move down one position
+
+Target:</ask>
+  <action>Move {{item_to_move}} to the specified position in {{new_order}}</action>
+  <output>Moved "{{item_to_move.title}}" to position {{new_position}}.</output>
+  <ask>Continue? [m] Move another item / [d] Done adjusting:</ask>
+  <check if="user selects 'm'">
+    <action>Display current ordering</action>
+    <goto step="3b" />
+  </check>
+  <check if="user selects 'd'">
+    <goto step="4" />
+  </check>
+</step>
+
+<step n="3c" goal="Auto-suggest prioritization" if="choice == 3">
+  <action>Analyze all backlog items using weighted criteria:
+    1. **Blocking dependencies** (highest weight) — items that block other items should come first
+    2. **Severity** (bugs only) — critical > high > medium > low
+    3. **Business value** — infer from epic priority, item description, and type
+    4. **Type priority** — bugs generally before stories of equal value
+    5. **Age** — older items (lower story numbers, earlier creation) get slight priority boost
+  </action>
+  <action>Generate {{suggested_order}} with rationale for each item's position</action>
+  <output>
+## Auto-Suggested Priority Order
+
+| New # | ID | Title | Type | Rationale |
+|---|---|---|---|---|
+{{#each suggested_order}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{rationale}} |
+{{/each}}
+  </output>
+  <ask>Options:
+- [a] Accept this ordering
+- [m] Modify (switch to full reprioritization with this as starting point)
+- [r] Reject (return to mode selection)
+
+Choice:</ask>
+  <check if="user selects 'a'">
+    <action>Set {{new_order}} = {{suggested_order}}</action>
+    <goto step="4" />
+  </check>
+  <check if="user selects 'm'">
+    <action>Set current backlog display to {{suggested_order}}</action>
+    <goto step="3a" />
+  </check>
+  <check if="user selects 'r'">
+    <goto step="3" />
+  </check>
+</step>
+
+<step n="4" goal="Dependency validation">
+  <action>For each item in {{new_order}}, check if it appears before any item it depends on</action>
+  <check if="dependency violations found">
+    <output>
+**Dependency Warning:** The following items appear before their dependencies:
+
+{{#each violations}}
+- **{{item.id}}** (position {{item.position}}) depends on **{{dependency.id}}** (position {{dependency.position}})
+{{/each}}
+    </output>
+    <ask>How to proceed?
+- [o] Override — keep current order despite dependency warnings
+- [f] Fix — automatically reorder to satisfy dependencies
+- [c] Cancel — return to mode selection
+
+Choice:</ask>
+    <check if="user selects 'f'">
+      <action>Reorder {{new_order}} to satisfy dependency constraints (move dependency items before their dependents, preserving relative order otherwise)</action>
+      <output>Dependencies fixed. Updated ordering applied.</output>
+    </check>
+    <check if="user selects 'c'">
+      <goto step="3" />
+    </check>
+    <!-- if 'o', proceed with current order -->
+  </check>
+</step>
+
+<step n="5" goal="Confirm and persist new ordering">
+  <output>
+## Old vs New Priority Order
+
+| Position | Old | New |
+|---|---|---|
+{{#each comparison}}
+| {{position}} | {{old_id}} — {{old_title}} | {{new_id}} — {{new_title}} |
+{{/each}}
+  </output>
+  <ask>Provide a brief reason for this reprioritization:</ask>
+  <action>Store as {{reason}}</action>
+  <ask>Confirm? [y] Apply / [n] Cancel / [e] Edit order:</ask>
+  <check if="user selects 'n'">
+    <output>Cancelled. No changes made.</output>
+    <action>Exit workflow</action>
+  </check>
+  <check if="user selects 'e'">
+    <goto step="3" />
+  </check>
+  <check if="user input is not 'y', 'n', or 'e'">
+    <output>Unrecognized option: "{{user_input}}". Please enter [y], [n], or [e].</output>
+    <goto step="5" />
+  </check>
+
+  <action>Update `_bmad-output/implementation-artifacts/backlog.yaml`:
+    - Rewrite items in {{new_order}} sequence
+    - Set priority fields sequentially: 1, 2, 3, ..., N
+    - Add or update header comment: `# Reprioritized: {{current_date}} — {{reason}}`
+    - Preserve all other item fields unchanged
+  </action>
+  <output>
+## Reprioritization Complete
+
+**Items reordered:** {{new_order.length}}
+**Reason:** {{reason}}
+**Date:** {{current_date}}
+
+Updated priorities written to `_bmad-output/implementation-artifacts/backlog.yaml`.
+
+**Next Steps:**
+- Use `/sprint-status-view` to review sprint assignments
+- Use `/add-to-sprint` to assign top-priority items to a sprint
+  </output>
+</step>
+
+</workflow>

package/lib/bmad-extension/skills/prioritize-backlog/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: prioritize-backlog
+module: ma-skills

package/lib/bmad-extension/skills/remove-from-sprint/SKILL.md

@@ -0,0 +1,163 @@
+---
+name: remove-from-sprint
+description: Remove items from a sprint and return them to the unassigned backlog
+type: skill
+triggers:
+  - "remove from sprint"
+  - "unassign from sprint"
+---
+
+# Remove-from-Sprint Workflow
+
+Remove items from a sprint and return them to the unassigned backlog.
+
+<workflow>
+
+<step n="1" goal="List sprints that have items and select one">
+  <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 to create a sprint.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>For each sprint file, read and extract: id, name, status, capacity, items (array), last_modified</action>
+  <action>Filter to sprints that have at least 1 item in their items array</action>
+  <check if="no sprints have items">
+    <output>No sprints contain any items. Nothing to remove.</output>
+    <action>Exit workflow</action>
+  </check>
+  <output>
+## Sprints with Items
+
+| # | Sprint | Status | Items | Capacity | Last Modified |
+|---|---|---|---|---|---|
+{{#each filtered_sprints}}
+| {{@index+1}} | {{name}} ({{id}}) | {{status}} | {{items_count}} | {{capacity}} | {{last_modified}} |
+{{/each}}
+  </output>
+  <ask>Select sprint (enter number):</ask>
+  <action>Store selected sprint as {{target_sprint}}</action>
+  <action>Store {{session_last_modified}} = {{target_sprint.last_modified}} for concurrency guard</action>
+</step>
+
+<step n="2" goal="Display sprint items with backlog metadata">
+  <action>Read `_bmad-output/implementation-artifacts/backlog.yaml`</action>
+  <action>For each item ID in {{target_sprint.items}}, look up metadata from backlog.yaml to get: title, type, status, priority</action>
+  <action>If an item is not found in backlog.yaml, infer title from ID (kebab-case to title case) and mark type/status/priority as "unknown"</action>
+  <output>
+## Items in {{target_sprint.name}}
+
+| # | ID | Title | Type | Status | Priority |
+|---|---|---|---|---|---|
+{{#each sprint_items}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{status}} | {{priority}} |
+{{/each}}
+  </output>
+</step>
+
+<step n="3" goal="Prompt for items to remove">
+  <ask>Which items to remove? Enter item numbers (comma-separated), 'all' to remove all, or 'q' to cancel:</ask>
+  <check if="user enters 'q'">
+    <output>Cancelled. No changes made.</output>
+    <action>Exit workflow</action>
+  </check>
+  <check if="user enters 'all'">
+    <action>Set {{items_to_remove}} = all items in {{target_sprint.items}}</action>
+  </check>
+  <check if="user enters item numbers">
+    <action>Resolve entered numbers against the table from step 2</action>
+    <action>Set {{items_to_remove}} = selected items</action>
+  </check>
+</step>
+
+<step n="4" goal="Confirm removal">
+  <output>
+## Confirm Removal
+
+The following items will be removed from **{{target_sprint.name}}** and returned to the unassigned backlog:
+
+{{#each items_to_remove}}
+- {{id}} — {{title}}
+{{/each}}
+
+**Note:** Item status will NOT be changed. Items retain their current status.
+  </output>
+  <ask>Proceed? [y] Yes / [n] Cancel / [e] Edit selection:</ask>
+  <check if="user selects 'n'">
+    <output>Cancelled. No changes made.</output>
+    <action>Exit workflow</action>
+  </check>
+  <check if="user selects 'e'">
+    <goto step="3" />
+  </check>
+  <check if="user input is not 'y', 'n', or 'e'">
+    <output>Unrecognized option: "{{user_input}}". Please enter [y], [n], or [e].</output>
+    <goto step="4" />
+  </check>
+</step>
+
+<step n="5" goal="Concurrency guard — re-read sprint before writing">
+  <action>Re-read the sprint file: `_bmad-output/implementation-artifacts/sprints/{{target_sprint.id}}.yaml`</action>
+  <action>Extract the current `last_modified` timestamp from the file</action>
+  <check if="current file last_modified != {{session_last_modified}}">
+    <output>
+**Conflict Detected:** The sprint file was modified since this session started.
+
+**Session started with:** `last_modified: {{session_last_modified}}`
+**Current file has:** `last_modified: {{current_file_last_modified}}`
+    </output>
+    <ask>How to proceed?
+- [o] Overwrite with your changes (your modifications replace current file)
+- [r] Reload — restart from current file state
+- [x] Cancel — discard all changes
+
+Choice:</ask>
+    <check if="choice == 'x'">
+      <output>Cancelled. Sprint file not modified.</output>
+      <action>Exit workflow</action>
+    </check>
+    <check if="choice == 'r'">
+      <action>Reload {{target_sprint}} from current file content</action>
+      <action>Update {{session_last_modified}} to current file's last_modified</action>
+      <output>Reloaded sprint from current state. Restarting item selection.</output>
+      <goto step="2" />
+    </check>
+    <!-- if 'o', proceed to write with session changes -->
+  </check>
+</step>
+
+<step n="6" goal="Remove items from sprint and update backlog">
+  <action>For each item in {{items_to_remove}}:
+    1. Remove the item ID from the sprint's `items` array
+    2. In `backlog.yaml`, find the matching backlog entry and set its `sprint` field to null (or remove it)
+    3. Do NOT change the item's `status` field — status is preserved as-is
+  </action>
+  <action>**Dual-write — both files must be updated for consistency:**</action>
+  <action>Update `last_modified` in the sprint file to current ISO timestamp</action>
+  <action>Write the updated sprint file: `_bmad-output/implementation-artifacts/sprints/{{target_sprint.id}}.yaml`</action>
+  <check if="sprint file write fails">
+    <output>**Error:** Failed to write sprint file. No changes persisted. Backlog NOT modified.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Write the updated `_bmad-output/implementation-artifacts/backlog.yaml`</action>
+  <check if="backlog.yaml write fails">
+    <output>**Warning: Inconsistent state!** Sprint file was updated but backlog.yaml write failed. Items have been removed from the sprint's `items` array but their `sprint` field in backlog.yaml still references {{target_sprint.id}}. Re-run `/remove-from-sprint` or manually fix backlog.yaml.</output>
+  </check>
+  <output>
+## Removal Complete
+
+**Sprint:** {{target_sprint.name}} ({{target_sprint.id}})
+
+**Removed items:**
+{{#each items_to_remove}}
+- {{id}} — {{title}} (status unchanged: {{status}})
+{{/each}}
+
+**Updated sprint capacity:** {{new_items_count}}/{{target_sprint.capacity}} items ({{new_remaining}} remaining)
+
+**Next Steps:**
+- Use `/add-to-sprint` to reassign items to a different sprint
+- Use `/sprint-status-view` to view sprint progress
+  </output>
+</step>
+
+</workflow>

package/lib/bmad-extension/skills/remove-from-sprint/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: remove-from-sprint
+module: ma-skills