ma-agents 3.4.9 → 3.5.1

package/lib/bmad-extension/workflows/remove-from-sprint/workflow.md

@@ -0,0 +1,164 @@
+# Remove-from-Sprint Workflow
+
+Guided workflow to move sprint items back to the backlog in the unified `sprint-status.yaml` using reverse movement semantics (inverse of `add-to-sprint`).
+
+<workflow>
+
+<step n="0" goal="Load configuration and validate file existence">
+  <action>Resolve the sprint-status.yaml path: check `_bmad/bmm/config.yaml` for `sprint_management_path`; if not set, default to `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
+  <action>Read the resolved `sprint-status.yaml` — the unified single source of truth for sprint and backlog state</action>
+  <check if="file does not exist">
+    <output>No sprint-status.yaml found. Run sprint planning first to initialize the file (`/bmad-sprint-planning`).</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Parse the full file: metadata fields (`generated`, `last_updated`, `project`, `project_key`, `tracking_system`, `story_location`), `epics` section, `backlog` array, and `sprints` map</action>
+  <action>Store parsed data as {{sprint_file}}</action>
+</step>
+
+<step n="1" goal="Identify sprints with removable items">
+  <action>Scan the `sprints` map in {{sprint_file}}. For each sprint entry, check if its `items` array has at least one element.</action>
+  <action>Build {{sprints_with_items}} = list of sprints where `items` is non-empty, ordered by sprint key (sprint-1, sprint-2, …)</action>
+  <check if="{{sprints_with_items}} is empty">
+    <output>No sprints with assigned items found. Nothing to remove.</output>
+    <action>Exit workflow</action>
+  </check>
+  <check if="exactly one sprint has items">
+    <action>Auto-select that sprint. Store as {{selected_sprint_id}} and {{selected_sprint}}</action>
+    <output>Auto-selected the only sprint with items: **{{selected_sprint.name}}** ({{selected_sprint.status}})</output>
+  </check>
+  <check if="multiple sprints have items">
+    <output>
+## Sprints with Assigned Items
+
+| # | Sprint ID | Name | Status | Capacity | Items |
+|---|-----------|------|--------|----------|-------|
+{{#each sprints_with_items}}
+| {{@index+1}} | {{id}} | {{name}} | {{status}} | {{capacity}} | {{items.length}} |
+{{/each}}
+    </output>
+    <ask>Select sprint to remove items from (enter number):</ask>
+    <action>Store selected sprint as {{selected_sprint_id}} and {{selected_sprint}}</action>
+  </check>
+  <check if="selected_sprint.status == 'closed'">
+    <output>Cannot remove items from a closed sprint. Closed sprints are immutable (schema section 6.7). Use `/close-sprint` or `/cleanup-done` to disposition items in closed sprints.</output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="2" goal="Display sprint items and identify eligible items for removal">
+  <action>Read {{selected_sprint.items}} array</action>
+  <action>Partition items into two groups:
+    - {{ineligible_items}} = items where `status` is `done` or `cancelled`
+    - {{eligible_items}} = all other items (status: ready-for-dev, in-progress, review, on-hold, backlog)
+  </action>
+  <check if="{{ineligible_items}} is non-empty">
+    <output>
+> **Note:** {{ineligible_items.length}} done/cancelled item(s) cannot be removed. Use `/cleanup-done` or `/close-sprint` to archive them.
+>
+> Ineligible items: {{#each ineligible_items}}{{id}} ({{status}}){{#unless @last}}, {{/unless}}{{/each}}
+    </output>
+  </check>
+  <check if="{{eligible_items}} is empty">
+    <output>All items in **{{selected_sprint.name}}** are done or cancelled. Use `/cleanup-done` or `/close-sprint` to archive them.</output>
+    <action>Exit workflow</action>
+  </check>
+  <output>
+## Items in {{selected_sprint.name}} — Eligible for Removal
+
+| # | ID | Title | Type | Epic | Status | Severity |
+|---|----|-------|------|------|--------|----------|
+{{#each eligible_items}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{epic ?? "—"}} | {{status}} | {{severity ?? "—"}} |
+{{/each}}
+
+*Sprint capacity: {{selected_sprint.items.length}}/{{selected_sprint.capacity}}*
+  </output>
+</step>
+
+<step n="3" goal="Select items to remove">
+  <ask>Which items do you want to remove from the sprint? Enter item numbers (comma-separated) or "all" to remove all eligible items:</ask>
+  <check if="user enters 'all'">
+    <action>Set {{items_to_remove}} = all items in {{eligible_items}}</action>
+  </check>
+  <check if="user enters item numbers">
+    <action>Resolve entered numbers against the eligible_items table. Validate all numbers are in range.</action>
+    <check if="any number is out of range">
+      <output>Invalid selection: number(s) out of range. Please enter valid item numbers from the table above.</output>
+      <goto step="3" />
+    </check>
+    <action>Set {{items_to_remove}} = items at the specified positions in {{eligible_items}}</action>
+  </check>
+</step>
+
+<step n="4" goal="Confirmation — warn about status resets">
+  <output>
+## Confirm Removal from {{selected_sprint.name}}
+
+The following items will be moved back to the backlog:
+
+| ID | Title | Current Status | Backlog Status After |
+|----|-------|---------------|----------------------|
+{{#each items_to_remove}}
+| {{id}} | {{title}} | {{status}} | ready-for-dev{{#if (ne status "ready-for-dev")}} ⚠️ status will be reset{{/if}} |
+{{/each}}
+
+**Effect on sprint capacity:** {{selected_sprint.items.length}} → {{selected_sprint.items.length - items_to_remove.length}} / {{selected_sprint.capacity}} items
+
+**Note:** Each removed item will be appended to the end of the backlog with `status: ready-for-dev`. Run `/prioritize-backlog` after this operation to reorder the backlog.
+  </output>
+  <check if="any item_to_remove has status != 'ready-for-dev'">
+    <output>
+> **Warning:** {{#each items_to_remove}}{{#if (ne status "ready-for-dev")}}**{{id}}** is currently `{{status}}` — its status will be reset to `ready-for-dev`. Any in-progress work tracking will be lost.{{/if}}{{/each}}
+    </output>
+  </check>
+  <ask>Options: [c] Confirm removal / [x] Cancel:</ask>
+  <check if="user selects 'x'">
+    <output>Removal cancelled — no changes made.</output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="5" goal="Execute reverse movement — atomic write">
+  <action>Load current {{sprint_file}} state (re-read if needed to get latest data)</action>
+  <action>Determine {{current_max_priority}}:
+    - If {{sprint_file.backlog}} is empty, set {{current_max_priority}} = 0
+    - Otherwise, set {{current_max_priority}} = max(item.priority for item in sprint_file.backlog)
+  </action>
+  <action>For each item in {{items_to_remove}} (in the order they appear in the sprint's items array):
+    1. REMOVE the item object from {{selected_sprint_id}}.items in the sprints map
+    2. INCREMENT {{current_max_priority}} by 1
+    3. SET item.status = "ready-for-dev"
+    4. ADD item.priority = {{current_max_priority}}
+    5. APPEND the item (with fields: id, type, epic, title, priority, status, severity) to the backlog array
+  </action>
+  <action>After all items are moved: renumber ALL backlog items' priority values sequentially (1..N) to match their array positions. First item in array gets priority 1, second gets priority 2, etc. Track each removed item's final renumbered priority in {{items_to_remove[n].final_priority}} for use in the summary.</action>
+  <action>Set {{sprint_file.last_updated}} = current ISO-8601 timestamp (e.g., "2026-04-06T12:00:00Z")</action>
+  <action>Write the complete updated sprint-status.yaml in a SINGLE atomic operation. The write MUST include all three sections (epics, backlog, sprints) and all metadata fields. Preserve the `generated` timestamp unchanged.</action>
+</step>
+
+<step n="6" goal="Display removal summary">
+  <output>
+## Removal Complete
+
+**Sprint:** {{selected_sprint.name}}
+**Items removed this session:** {{items_to_remove.length}}
+**Updated sprint capacity:** {{selected_sprint.items.length - items_to_remove.length}}/{{selected_sprint.capacity}} items
+
+### Removed Items — Now in Backlog
+
+| ID | Title | Backlog Priority | Status |
+|----|-------|-----------------|--------|
+{{#each items_to_remove}}
+| {{id}} | {{title}} | {{final_priority}} | ready-for-dev |
+{{/each}}
+
+**Updated backlog count:** {{sprint_file.backlog.length}} items
+
+**Next Steps:**
+- Run `/prioritize-backlog` to reorder the backlog after removals
+- Run `/add-to-sprint` to reassign items to a sprint
+- Run `/sprint-status-view` to view the updated sprint status
+  </output>
+</step>
+
+</workflow>

package/lib/bmad-extension/workflows/sprint-status-view/workflow.md

@@ -1,193 +1,166 @@
-# 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)*`
+
+---
+
+## 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`.
+
 ---
 
-## 🏃 {{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>
+## 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).
+
 ---
 
-## 📦 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 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/mil498/README.md

@@ -0,0 +1,4 @@
+MIL-STD-498 DIDs converted to HTML.
+
+For more information (what is it, why do you need it), see the article at [http://kkovacs.eu/free-project-management-template-mil-std-498]!
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ma-agents",
-  "version": "3.4.9",
+  "version": "3.5.1",
   "description": "NPX tool to install skills for AI coding agents (Claude Code, Gemini, Copilot, Kilocode, Cline, Cursor, Roo Code)",
   "main": "index.js",
   "bin": {