ma-agents 3.4.8 → 3.5.0

package/skills/modify-sprint/SKILL.md

@@ -0,0 +1,302 @@
+# Modify Sprint Skill
+
+Guided workflow to modify an existing sprint's metadata (name, capacity, dates, status) within the `sprints` section of `sprint-status.yaml`.
+
+> **Scope:** This skill modifies sprint **metadata only** — name, capacity, start date, end date, and status.
+> To assign items to a sprint, use `/add-to-sprint`. To remove items, use `/remove-from-sprint`.
+
+<workflow>
+
+<step n="0" goal="Load configuration and validate file existence">
+  <action>Locate `sprint-status.yaml` at `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
+  <check if="file 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, retaining all three sections: `epics`, `backlog`, and `sprints`</action>
+  <action>Store file contents as {{file_content}} for use in the final atomic write</action>
+</step>
+
+<step n="1" goal="Identify available sprints and select one to modify">
+  <action>Parse the `sprints` section from the loaded file</action>
+  <check if="sprints section is empty ({})">
+    <output>No sprints found. Run `/add-sprint` first to create a sprint.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Build sprint list with: sprint ID (map key), name, status, capacity, item count (length of items array), start, end</action>
+  <output>
+## Available Sprints
+
+| # | Sprint ID | Name | Status | Capacity | Items | Start | End |
+|---|---|---|---|---|---|---|---|
+{{#each sprints}}
+| {{@index+1}} | {{sprint_id}} | {{name}} | {{status}} | {{capacity}} | {{item_count}}/{{capacity}} | {{start_or_not_set}} | {{end_or_not_set}} |
+{{/each}}
+
+Note: closed sprints are immutable and cannot be modified.
+  </output>
+  <ask>Select sprint to modify (enter number):</ask>
+  <action>Store selected sprint as {{target_sprint}} and its map key as {{sprint_id}}</action>
+  <check if="{{target_sprint.status}} == 'closed'">
+    <output>Sprint '{{target_sprint.name}}' ({{sprint_id}}) is closed. Closed sprints are immutable (schema constraint 6.7). Only archival operations are permitted.</output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="2" goal="Display current sprint state">
+  <action>Calculate {{item_count}} = length of {{target_sprint.items}} array</action>
+  <action>Calculate {{remaining}} = {{target_sprint.capacity}} - {{item_count}}</action>
+  <output>
+## Sprint: {{target_sprint.name}} ({{sprint_id}})
+
+- Status: {{target_sprint.status}}
+- Capacity: {{target_sprint.capacity}} items ({{item_count}} assigned, {{remaining}} remaining)
+- Start: {{target_sprint.start || "not set"}}
+- End: {{target_sprint.end || "not set"}}
+- Items: {{item_count}} assigned (use /add-to-sprint or /remove-from-sprint to manage items)
+
+### Assigned Items (read-only)
+{{#if items_empty}}
+*(No items assigned yet)*
+{{else}}
+| ID | Title | Type | Status |
+|---|---|---|---|
+{{#each target_sprint.items}}
+| {{id}} | {{title}} | {{type}} | {{status}} |
+{{/each}}
+{{/if}}
+  </output>
+  <action>Initialize {{working_changes}} = empty map to accumulate changes made during this session</action>
+  <action>Initialize working state aliases: {{current_name}} = {{target_sprint.name}}, {{current_capacity}} = {{target_sprint.capacity}}, {{current_start}} = {{target_sprint.start}}, {{current_end}} = {{target_sprint.end}}, {{current_status}} = {{target_sprint.status}}. These aliases are updated in-place as changes are made so Step 3's menu always shows the latest values.</action>
+  <action>Store {{original_name}} = {{target_sprint.name}} (preserved as the display name in the confirmation summary)</action>
+</step>
+
+<step n="3" goal="Present modification menu">
+  <output>
+## What would you like to modify?
+
+1. Sprint name (current: "{{current_name}}")
+2. Capacity (current: {{current_capacity}})
+3. Start date (current: {{current_start || "not set"}})
+4. End date (current: {{current_end || "not set"}})
+5. Status (current: {{current_status}})
+6. Done -- save all changes and exit
+  </output>
+  <ask>Choice:</ask>
+  <check if="choice == 6 or choice == 'done'">
+    <goto step="4" />
+  </check>
+</step>
+
+<step n="3a" goal="Modify sprint name" if="choice == 1">
+  <ask>New sprint name (current: '{{current_name}}'):</ask>
+  <check if="input is empty">
+    <output>Sprint name cannot be empty. Please enter a valid name.</output>
+    <goto step="3a" />
+  </check>
+  <action>Store {{new_name}} = input</action>
+  <action>Store change: name: {{current_name}} -> {{new_name}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_name}} = {{new_name}}</action>
+  <output>Sprint name updated: '{{old_name}}' -> '{{new_name}}'.</output>
+  <goto step="3" />
+</step>
+
+<step n="3b" goal="Modify capacity" if="choice == 2">
+  <ask>New capacity (positive integer, current: {{current_capacity}}):</ask>
+  <action>Validate input is a positive integer (greater than zero, no decimals, no non-numeric characters)</action>
+  <check if="input is NOT a positive integer">
+    <output>Invalid capacity. Must be a positive integer greater than zero.</output>
+    <goto step="3b" />
+  </check>
+  <action>Store {{new_capacity}} = validated integer input</action>
+  <action>Calculate {{item_count}} = length of {{target_sprint.items}} array</action>
+  <check if="{{new_capacity}} < {{item_count}}">
+    <output>Sprint has {{item_count}} items but new capacity would be {{new_capacity}} ({{new_capacity}} < {{item_count}}). Capacity is advisory -- items will not be removed.</output>
+    <ask>Options:
+- [a] Apply anyway (capacity is advisory per schema section 4.2)
+- [s] Skip -- keep current capacity
+- [r] Remove items first (direct to /remove-from-sprint)
+
+Choice:</ask>
+    <check if="choice == 's'">
+      <goto step="3" />
+    </check>
+    <check if="choice == 'r'">
+      <output>Run `/remove-from-sprint` to remove items, then re-run `/modify-sprint`.</output>
+      <action>Exit workflow</action>
+    </check>
+    <!-- if 'a', proceed with the change -->
+  </check>
+  <action>Calculate {{new_remaining}} = {{new_capacity}} - {{item_count}}</action>
+  <action>Store change: capacity: {{current_capacity}} -> {{new_capacity}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_capacity}} = {{new_capacity}}</action>
+  <output>Capacity updated: {{old_capacity}} -> {{new_capacity}} ({{new_remaining}} slots remaining with {{item_count}} assigned items).</output>
+  <goto step="3" />
+</step>
+
+<step n="3c" goal="Modify start date" if="choice == 3">
+  <ask>New start date (ISO format YYYY-MM-DD, or press Enter to clear):</ask>
+  <check if="input is empty">
+    <action>Store {{new_start}} = "" (clears the date)</action>
+  </check>
+  <check if="input is not empty">
+    <action>Validate input matches ISO date format YYYY-MM-DD (regex: ^\d{4}-\d{2}-\d{2}$) and represents a valid calendar date</action>
+    <check if="invalid format">
+      <output>Invalid date format. Use YYYY-MM-DD (e.g., 2026-05-01).</output>
+      <goto step="3c" />
+    </check>
+    <action>Store {{new_start}} = input</action>
+  </check>
+  <action>Store change: start: {{current_start || "not set"}} -> {{new_start || "not set"}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_start}} = {{new_start}}</action>
+  <output>Start date updated: '{{old_start || "not set"}}' -> '{{new_start || "not set"}}'.</output>
+  <goto step="3" />
+</step>
+
+<step n="3d" goal="Modify end date" if="choice == 4">
+  <ask>New end date (ISO format YYYY-MM-DD, or press Enter to clear):</ask>
+  <check if="input is empty">
+    <action>Store {{new_end}} = "" (clears the date)</action>
+  </check>
+  <check if="input is not empty">
+    <action>Validate input matches ISO date format YYYY-MM-DD (regex: ^\d{4}-\d{2}-\d{2}$) and represents a valid calendar date</action>
+    <check if="invalid format">
+      <output>Invalid date format. Use YYYY-MM-DD (e.g., 2026-05-31).</output>
+      <goto step="3d" />
+    </check>
+    <action>Store {{new_end}} = input</action>
+  </check>
+  <action>Determine effective start: use {{current_start}} if not changed, else use newly entered start</action>
+  <check if="{{new_end}} is not empty AND {{effective_start}} is not empty AND {{new_end}} < {{effective_start}}">
+    <output>Warning: End date ({{new_end}}) is before start date ({{effective_start}}). This may be intentional.</output>
+  </check>
+  <action>Store change: end: {{current_end || "not set"}} -> {{new_end || "not set"}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_end}} = {{new_end}}</action>
+  <output>End date updated: '{{old_end || "not set"}}' -> '{{new_end || "not set"}}'.</output>
+  <goto step="3" />
+</step>
+
+<step n="3e" goal="Modify status" if="choice == 5">
+  <action>Determine valid transitions based on {{current_status}}:
+    - If `planning`: valid next state is `active` only
+    - If `active`: valid next state is `closed` only
+    - If `closed`: no transitions available (immutable)
+  </action>
+  <output>
+Current status: {{current_status}}
+{{#if current_status == 'planning'}}Valid transitions: planning -> active{{/if}}
+{{#if current_status == 'active'}}Valid transitions: active -> closed{{/if}}
+{{#if current_status == 'closed'}}No transitions available. Closed sprints are immutable.{{/if}}
+  </output>
+  <check if="{{current_status}} == 'closed'">
+    <output>Sprint '{{current_name}}' is closed. Closed sprints are immutable (schema constraint 6.7). Only archival operations are permitted.</output>
+    <goto step="3" />
+  </check>
+  <ask>New status:</ask>
+  <action>Validate transition:
+    - planning -> active: allowed (proceed to single-active-sprint check)
+    - active -> closed: allowed (with warning about /close-sprint)
+    - planning -> closed: REJECTED (skip)
+    - active -> planning: REJECTED (backward)
+    - closed -> anything: REJECTED (immutable -- already handled above)
+    - same state -> same state: REJECTED (no change)
+    - any unrecognized value: REJECTED
+  </action>
+  <check if="transition is invalid (backward, skip, or unrecognized)">
+    <output>Invalid status transition: {{current_status}} -> {{requested_status}}. Sprint status transitions are forward-only: planning -> active -> closed.</output>
+    <goto step="3e" />
+  </check>
+  <check if="requested_status == 'closed'">
+    <output>Warning: To properly close a sprint with item disposition (archiving done items, returning incomplete items to backlog), use `/close-sprint` instead. This will only update the status field.</output>
+    <ask>Continue with status-only change? [y/n]</ask>
+    <check if="answer == 'n'">
+      <output>Status change cancelled. Use `/close-sprint` for full sprint close lifecycle.</output>
+      <goto step="3" />
+    </check>
+  </check>
+  <check if="requested_status == 'active'">
+    <action>Scan all other sprints in the `sprints` map for any sprint with status: active</action>
+    <check if="another active sprint found">
+      <output>Sprint '{{other_sprint_name}}' ({{other_sprint_id}}) is already active. Only one sprint can be active at a time (schema constraint 6.4). Close it first or cancel this change.</output>
+      <ask>Options:
+- [c] Cancel status change
+- [x] Exit to run /close-sprint on {{other_sprint_id}} first
+
+Choice:</ask>
+      <check if="choice == 'c'">
+        <goto step="3" />
+      </check>
+      <check if="choice == 'x'">
+        <output>Run `/close-sprint` on {{other_sprint_id}} first, then re-run `/modify-sprint`.</output>
+        <action>Exit workflow</action>
+      </check>
+    </check>
+  </check>
+  <action>Store change: status: {{current_status}} -> {{requested_status}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_status}} = {{requested_status}}</action>
+  <output>Status updated: {{old_status}} -> {{requested_status}}.</output>
+  <goto step="3" />
+</step>
+
+<step n="4" goal="Confirmation -- review and confirm all changes">
+  <check if="{{working_changes}} is empty">
+    <output>No modifications made.</output>
+    <action>Exit workflow</action>
+  </check>
+  <output>
+## Modification Summary -- Please Confirm
+
+Sprint: {{sprint_id}} ("{{original_name}}")
+
+Changes:
+{{#each working_changes}}
+- {{field}}: {{old_value}} -> {{new_value}}
+{{/each}}
+
+All other sprint data (items, other sprints, epics, backlog) will be preserved unchanged.
+  </output>
+  <ask>Confirm changes? [y] Yes / [n] Cancel / [e] Edit more</ask>
+  <check if="choice == 'n'">
+    <output>Changes discarded.</output>
+    <action>Exit workflow</action>
+  </check>
+  <check if="choice == 'e'">
+    <goto step="3" />
+  </check>
+  <!-- if 'y', proceed to Step 5 -->
+</step>
+
+<step n="5" goal="Persist changes to sprint-status.yaml">
+  <action>Re-read `_bmad-output/implementation-artifacts/sprint-status.yaml` to get the latest file state before writing</action>
+  <action>Locate the target sprint entry at `sprints.{{sprint_id}}` in the re-read file</action>
+  <action>Apply all confirmed changes to the target sprint entry:
+    - If name was changed: update `name` field
+    - If capacity was changed: update `capacity` field
+    - If start was changed: update `start` field
+    - If end was changed: update `end` field
+    - If status was changed: update `status` field
+  </action>
+  <action>Preserve the sprint's `items` array exactly as-is (no modifications)</action>
+  <action>Preserve all other sprint entries in the `sprints` map exactly as-is</action>
+  <action>Preserve the `epics` section exactly as-is</action>
+  <action>Preserve the `backlog` section exactly as-is</action>
+  <action>Preserve the `generated` field exactly as-is (never change)</action>
+  <action>Set `last_updated` to the current ISO-8601 timestamp</action>
+  <action>Write the complete updated file in a single atomic write to `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
+  <output>
+Sprint modified successfully!
+
+Sprint: {{sprint_name}} ({{sprint_id}})
+{{#each working_changes}}
+- {{field}}: {{new_value}}
+{{/each}}
+
+Next Steps:
+- Use /add-to-sprint to assign backlog items to this sprint
+- Use /remove-from-sprint to remove items from this sprint
+- Use /sprint-status-view to view sprint progress
+- Use /close-sprint to close this sprint when complete
+  </output>
+</step>
+
+</workflow>

package/skills/modify-sprint/skill.json

@@ -0,0 +1,7 @@
+{
+  "name": "modify-sprint",
+  "version": "1.0.0",
+  "description": "Guided workflow to modify an existing sprint's metadata (name, capacity, dates, status) within the sprints section of sprint-status.yaml",
+  "category": "workflow",
+  "tags": ["sprint-management", "modify-sprint", "capacity", "metadata"]
+}

package/skills/prioritize-backlog/SKILL.md

@@ -0,0 +1,203 @@
+# Prioritize Backlog
+
+Reprioritize backlog items in `sprint-status.yaml` using multiple criteria: severity, business value, dependencies, type, and age.
+
+<workflow>
+
+<step n="0" goal="Load configuration and validate file existence">
+  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml` — the single source of truth for all sprint and backlog state.</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 — do not create any file.</action>
+  </check>
+  <action>Parse the full file: read `epics`, `backlog`, and `sprints` sections plus all metadata fields (`generated`, `last_updated`, `project`, `project_key`, `tracking_system`, `story_location`). Store the entire parsed structure as {{file_data}} for later atomic write.</action>
+  <check if="legacy backlog.yaml exists in _bmad-output/implementation-artifacts/">
+    <output>Note: Legacy backlog.yaml detected. Run migration to consolidate.</output>
+    <action>Continue — do NOT read from or write to the legacy file. Operate on sprint-status.yaml only.</action>
+  </check>
+  <check if="{{file_data.backlog}} is empty or null">
+    <output>Backlog is empty. Nothing to prioritize.</output>
+    <action>Exit workflow — do not modify the file.</action>
+  </check>
+  <action>Store {{backlog_items}} = {{file_data.backlog}} (the array of items to work with).</action>
+  <action>Store {{original_order}} = copy of {{backlog_items}} with their current priority values, for use in the change summary later.</action>
+</step>
+
+<step n="1" goal="Display current backlog order">
+  <action>Read {{backlog_items}} in their current array order (position 0 = highest priority).</action>
+  <output>
+## Current Backlog ({{backlog_items.length}} items)
+
+| Priority | ID | Title | Type | Epic | Severity | Status |
+|---|---|---|---|---|---|---|
+{{#each backlog_items}}
+| {{priority}} | {{id}} | {{title}} | {{type}} | {{#if epic}}epic-{{epic}}{{else}}—{{/if}} | {{severity or "—"}} | {{status}} |
+{{/each}}
+
+*Note: Items assigned to sprints are not shown — only unassigned backlog items are listed here.*
+  </output>
+</step>
+
+<step n="2" goal="Choose prioritization mode">
+  <ask>Select a prioritization mode:
+
+**[f] Full** — Interactive: generates a suggested order, presents current vs proposed side-by-side. You review and approve (or adjust) before any write occurs.
+**[q] Quick** — Automated: applies default multi-criteria rules immediately, then shows a summary of what moved.
+**[a] Auto-suggest** — Read-only: shows the suggested order with per-item rationale. No file is modified.
+**[x] Cancel** — Exit without changes.
+
+Choice:</ask>
+  <check if="user selects 'x'">
+    <output>Cancelled — no changes made.</output>
+    <action>Exit workflow.</action>
+  </check>
+  <action>Store {{selected_mode}} = user choice.</action>
+</step>
+
+<step n="3" goal="Multi-criteria prioritization analysis">
+  <action>For each item in {{backlog_items}}, compute a composite priority score using the following weighted criteria (highest weight listed first):</action>
+
+  <action>**1. Severity weight (highest impact):**
+  - `severity: critical` → +40 points
+  - `severity: high`     → +30 points
+  - `severity: medium`   → +10 points
+  - `severity: low`      → +5 points
+  - `severity: null`     → +0 points (no adjustment for stories)
+  </action>
+
+  <action>**2. Business value weight:**
+  - Use the item's existing `priority` value as a signal for current business value ranking. Items with lower `priority` values (higher priority) receive a proportional boost: score += max(0, ({{backlog_items.length}} - current_priority + 1) * 2). This preserves existing prioritization signals while allowing other criteria to override.
+  - Items from lower-numbered epics (or `epic: null`) receive a slight additional boost: score += max(0, (20 - epic_number)) * 1, treating null as epic 0.
+  </action>
+
+  <action>**3. Dependency weight:**
+  - Read `_bmad-output/planning-artifacts/epics.md` if it exists to identify explicit inter-story dependencies.
+  - Within the same epic, items with lower story numbers are assumed to be prerequisites for higher-numbered stories. Items that block others get a +15 point boost.
+  - Items that are explicitly blocked by other UNASSIGNED backlog items get a -10 point adjustment (they cannot proceed anyway).
+  - If epics.md cannot be read or does not define explicit dependencies, use only the intra-epic ordering heuristic.
+  </action>
+
+  <action>**4. Type weight (tiebreaker):**
+  - `type: bug` → +3 points (bugs receive a slight boost over stories at equal composite score)
+  - `type: story` → +0 points
+  </action>
+
+  <action>**5. Age weight (starvation prevention — weakest signal):**
+  - Items from epics with lower epic numbers receive +1 point per 5 epic numbers below the maximum epic in the backlog (e.g., if max epic is 17, epic-12 gets +1, epic-7 gets +2).
+  - Items with `epic: null` are treated as oldest (receive the maximum age boost among all items).
+  - This is a tiebreaker only — it prevents starvation but does not override higher-priority signals.
+  </action>
+
+  <action>Compute {{composite_score}} for each item = severity_score + business_value_score + dependency_score + type_score + age_score.</action>
+  <action>Sort items by {{composite_score}} descending (highest score = priority 1). Break ties by current `priority` value (lower = higher priority stays higher).</action>
+  <action>Store {{suggested_order}} = sorted list of items. Store {{rationale_map}} = per-item map of score breakdown and reason summary.</action>
+</step>
+
+<step n="3a" goal="Full mode: present comparison and get approval" condition="{{selected_mode}} == 'f'">
+  <output>
+## Prioritization Analysis: Current vs Suggested
+
+| Current Priority | ID | Suggested Priority | Change | Key Rationale |
+|---|---|---|---|---|
+{{#each original_order}}
+| {{priority}} | {{id}} | {{suggested_position}} | {{change_indicator}} | {{rationale}} |
+{{/each}}
+
+*Items highlighted with ↑ move up, ↓ move down, = stay in place.*
+  </output>
+  <ask>Options:
+- **[a]** Accept the suggested order as-is
+- **[m]** Manually adjust — enter item IDs in your preferred order (comma-separated)
+- **[c]** Cancel — exit without changes
+
+Choice:</ask>
+  <check if="user selects 'c'">
+    <output>Cancelled — no changes made.</output>
+    <action>Exit workflow.</action>
+  </check>
+  <check if="user selects 'a'">
+    <action>Set {{final_order}} = {{suggested_order}}.</action>
+  </check>
+  <check if="user selects 'm'">
+    <ask>Enter item IDs in your preferred priority order (highest priority first), comma-separated. You MUST include all {{backlog_items.length}} items — no duplicates or omissions allowed:
+Example: 17-10-rework-generate-backlog, 17-11-rework-add-to-sprint, ...</ask>
+    <action>Parse the user-provided list into {{manual_order_ids}}.</action>
+    <action>Validate:
+    - Count must equal {{backlog_items.length}} (no missing items)
+    - All IDs must exist in {{backlog_items}} (no unknown IDs)
+    - No duplicate IDs
+    </action>
+    <check if="validation fails">
+      <output>Invalid input: {{validation_error}}. Please re-enter the complete list of all {{backlog_items.length}} item IDs in your preferred order.</output>
+      <action>Repeat the manual-entry prompt until valid input is received or user cancels.</action>
+    </check>
+    <action>Reorder {{backlog_items}} to match {{manual_order_ids}} sequence. Set {{final_order}} = reordered list.</action>
+  </check>
+  <action>Proceed to Step 4 with {{final_order}}.</action>
+</step>
+
+<step n="3b" goal="Quick mode: apply suggested order automatically" condition="{{selected_mode}} == 'q'">
+  <action>Set {{final_order}} = {{suggested_order}}.</action>
+  <action>Proceed to Step 4 with {{final_order}}.</action>
+</step>
+
+<step n="3c" goal="Auto-suggest mode: display suggestions without writing" condition="{{selected_mode}} == 'a'">
+  <output>
+## Suggested Backlog Order (Read-Only — No Changes Written)
+
+| New Priority | ID | Title | Old Priority | Change | Rationale |
+|---|---|---|---|---|---|
+{{#each suggested_order}}
+| {{new_priority}} | {{id}} | {{title}} | {{old_priority}} | {{change_indicator}} | {{rationale}} |
+{{/each}}
+
+**Summary:**
+- Items that would move up: {{move_up_count}}
+- Items that would move down: {{move_down_count}}
+- Items unchanged: {{unchanged_count}}
+
+Suggestions displayed. No changes written. Run again in Full or Quick mode to apply.
+  </output>
+  <action>Exit workflow — do NOT proceed to Step 4.</action>
+</step>
+
+<step n="4" goal="Apply reordering and persist">
+  <action>Take {{final_order}} (from Full or Quick mode).</action>
+  <action>Renumber `priority` field on each item sequentially: position 0 in the array gets `priority: 1`, position 1 gets `priority: 2`, and so on through position N-1 gets `priority: N`. This keeps the denormalized index in sync with array position (schema section 3.3).</action>
+  <action>Get the current ISO-8601 timestamp (format: YYYY-MM-DDTHH:MM:SS). Update {{file_data.last_updated}} to this timestamp.</action>
+  <action>Preserve {{file_data.generated}} unchanged.</action>
+  <action>Preserve {{file_data.epics}} section unchanged — do NOT modify any epic entries.</action>
+  <action>Preserve {{file_data.sprints}} section unchanged — do NOT modify any sprint entries or items within sprints.</action>
+  <action>Set {{file_data.backlog}} = {{final_order}} (the reordered array with renumbered priorities).</action>
+  <action>Write the complete updated {{file_data}} back to `_bmad-output/implementation-artifacts/sprint-status.yaml` in a single atomic write (read-modify-write pattern). This single write replaces the file entirely — no partial updates.</action>
+</step>
+
+<step n="5" goal="Display summary output">
+  <action>Compute change summary by comparing {{original_order}} (old positions) against {{final_order}} (new positions).</action>
+  <output>
+## Reprioritization Complete
+
+**Mode:** {{mode_label}} ({{current_datetime}})
+**Items reordered:** {{backlog_items.length}} total
+
+### Changes Made
+
+| ID | Title | Old Priority | New Priority | Direction |
+|---|---|---|---|---|
+{{#each changed_items}}
+| {{id}} | {{title}} | {{old_priority}} | {{new_priority}} | {{direction}} |
+{{/each}}
+
+{{#if unchanged_items.length > 0}}
+**Unchanged ({{unchanged_items.length}} items):** {{unchanged_ids_list}}
+{{/if}}
+
+**sprint-status.yaml updated successfully.**
+
+**Next steps:**
+- `/add-to-sprint` — Assign the top-priority backlog items to the current sprint
+- `/sprint-status-view` — View overall sprint progress and capacity
+  </output>
+</step>
+
+</workflow>

package/skills/prioritize-backlog/skill.json

@@ -0,0 +1,7 @@
+{
+  "name": "prioritize-backlog",
+  "version": "1.0.0",
+  "description": "Reprioritize backlog items using multiple criteria -- severity, business value, dependencies, type, age",
+  "category": "workflow",
+  "tags": ["backlog", "prioritization", "sprint-management"]
+}