ma-agents 3.6.2 → 3.8.0

package/lib/bmad-extension-plugin/skills/project-context-expansion/SKILL.md

@@ -0,0 +1,238 @@
+---
+name: project-context-expansion
+description: Post-retrospective workflow to update project-context.md with discovered patterns and conventions
+type: skill
+triggers:
+  - "project context expansion"
+  - "expand project context"
+---
+
+# Project Context Expansion Workflow
+
+Post-retrospective companion workflow to update `_bmad-output/project-context.md` with
+patterns and conventions discovered during the sprint.
+
+Run this workflow at the end of `/bmad-retrospective` to close the living document lifecycle loop.
+The agent proposes additions; the human decides what gets written.
+
+<workflow>
+
+<step n="1" goal="Check whether project-context.md exists">
+
+  <action>Check if `_bmad-output/project-context.md` exists in the project root</action>
+
+  <check if="file does NOT exist">
+    <output>
+ℹ️ **No project-context.md found.**
+
+`_bmad-output/project-context.md` does not exist in this project yet.
+
+To create it, either:
+- Run `npx ma-agents install` at the project level (auto-generates on first install)
+- Run `/bmad-generate-project-context` to create it manually
+
+Skipping project-context expansion — nothing to update.
+    </output>
+    <action>Exit workflow</action>
+  </check>
+
+  <check if="file exists">
+    <output>
+✅ Found `_bmad-output/project-context.md` — proceeding with expansion review.
+    </output>
+  </check>
+
+</step>
+
+<step n="2" goal="Read and present the current Project-Specific Rules section">
+
+  <action>Read the complete contents of `_bmad-output/project-context.md`</action>
+
+  <action>Extract the `## Project-Specific Rules` section:
+    - Find the line starting with `## Project-Specific Rules`
+    - Read all content until the next `##` section header (or end of file)
+    - Store as {{current_rules_content}}
+  </action>
+
+  <check if="{{current_rules_content}} contains only the TODO comment or is effectively empty">
+    <action>Set {{rules_are_empty}} = true</action>
+  </check>
+
+  <check if="{{current_rules_content}} contains substantive rules">
+    <action>Set {{rules_are_empty}} = false</action>
+  </check>
+
+  <output>
+## Current Project-Specific Rules
+
+{{current_rules_content}}
+
+---
+
+I will now review the retrospective discussion to propose additions to this section.
+  </output>
+
+</step>
+
+<step n="3" goal="Gather sprint patterns — from retrospective context or user input">
+
+  <action>Check whether there is active retrospective context in this session (i.e., this workflow
+  was invoked immediately after running /bmad-retrospective and discussion content is available).
+  </action>
+
+  <check if="retrospective context IS present in this session">
+    <action>Use the retrospective discussion to identify patterns, conventions, and lessons.
+    Skip the user prompt below — proceed directly to the proposal step.
+    </action>
+  </check>
+
+  <check if="retrospective context is NOT present (workflow invoked cold or standalone)">
+    <output>
+ℹ️ **No retrospective session detected in this context.**
+
+This workflow is designed to run after `/bmad-retrospective`, but it can also be used
+standalone to capture any conventions or patterns you've observed.
+    </output>
+    <ask>
+Briefly describe the patterns or conventions you want to add to Project-Specific Rules.
+For example: "agents kept omitting error handling in async functions" or
+"we decided all PRs need a test-plan section in the description".
+
+You can also just say "run retrospective first" to cancel.
+    </ask>
+    <check if="user says 'run retrospective first' or equivalent cancel">
+      <output>
+ℹ️ To get the most value, run `/bmad-retrospective` first, then invoke `/project-context-expansion`
+at the end of that session. No changes made.
+      </output>
+      <action>Exit workflow</action>
+    </check>
+    <action>Store the user-described patterns as {{sprint_patterns}} and use them as the source
+    material for the proposal in the next action below.
+    </action>
+  </check>
+
+  <action>Based on the retrospective discussion OR user-described patterns, identify items that
+  should become standing rules for AI agents — specifically:
+    - Coding conventions agents got wrong or needed correction on during the sprint
+    - Patterns agents should consistently apply in this project
+    - Architectural decisions that agents must respect (and that are not obvious from the code)
+    - Testing or review conventions specific to this project
+    - Gotchas or anti-patterns agents kept producing that should be explicitly prohibited
+    - Workflow or communication rules specific to this team's practices
+  </action>
+
+  <action>Filter OUT anything that belongs in other sections:
+    - Technology Stack updates → belongs in `## Technology Stack` (use `/bmad-generate-project-context`)
+    - Mandatory pre-task rules → belongs in `## AI Agent Mandatory Rules` (set at install time)
+    - Do NOT propose changes to any section other than `## Project-Specific Rules`
+  </action>
+
+  <check if="no relevant patterns found from retrospective">
+    <output>
+ℹ️ **No new rules to propose.**
+
+Based on the retrospective discussion, no patterns were identified that would add value
+as standing rules in `## Project-Specific Rules`. The section is already up to date.
+
+If you noticed patterns the agents got wrong, you can manually edit
+`_bmad-output/project-context.md` to add your own rules at any time.
+    </output>
+    <action>Exit workflow</action>
+  </check>
+
+  <action>Draft proposed additions as clear, imperative rules:
+    - Each rule is a single actionable statement (e.g., "Always use X when Y")
+    - Rules are specific enough to change agent behavior, not vague principles
+    - Each rule is distinct — no overlap with existing rules
+    - Store as {{proposed_additions}}
+  </action>
+
+  <output>
+## Proposed Additions to Project-Specific Rules
+
+Based on patterns from this sprint's retrospective, here are the additions I recommend:
+
+{{proposed_additions}}
+
+---
+
+**Review these carefully.** These additions will be appended to `## Project-Specific Rules`
+in `_bmad-output/project-context.md` and will govern all future AI agent sessions.
+  </output>
+
+</step>
+
+<step n="4" goal="Human review and confirmation gate">
+
+  <ask>
+Review the proposed additions above.
+
+Options:
+- **[y] Accept all** — append all proposed additions as shown
+- **[n] Reject all** — skip without any changes
+- **[e] Edit** — describe which rules to add, remove, or reword before writing
+  </ask>
+
+  <check if="user selects 'n'">
+    <output>
+❌ **Expansion skipped.** No changes were made to `_bmad-output/project-context.md`.
+    </output>
+    <action>Exit workflow</action>
+  </check>
+
+  <check if="user selects 'e'">
+    <ask>Describe your edits — which rules to keep, drop, or reword:</ask>
+    <action>Apply user edits to {{proposed_additions}}</action>
+    <action>Re-display the revised proposal</action>
+    <ask>Proceed with this revised version? [y] Yes / [n] Cancel:</ask>
+    <check if="user selects 'n'">
+      <output>
+❌ **Expansion cancelled.** No changes were made to `_bmad-output/project-context.md`.
+      </output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+</step>
+
+<step n="5" goal="Write approved additions to Project-Specific Rules only">
+
+  <action>Read the current full contents of `_bmad-output/project-context.md` again (to ensure freshness)</action>
+
+  <action>Locate the `## Project-Specific Rules` section:
+    - Find the line starting with `## Project-Specific Rules`
+    - Identify the end of the section (next `##` header or end of file)
+    - Preserve all existing content in the section — do NOT remove or reorder existing rules
+  </action>
+
+  <action>Append the approved additions at the END of the `## Project-Specific Rules` section,
+  before the next `##` header. Insert a blank line separator if the section is not empty.
+  </action>
+
+  <action>CRITICAL CONSTRAINTS — do NOT touch any other section:
+    - Do NOT modify `## AI Agent Mandatory Rules`
+    - Do NOT modify `## Technology Stack`
+    - Do NOT modify any other section
+    - Do NOT reformat or reorganize the file
+    - Only append to `## Project-Specific Rules`
+  </action>
+
+  <action>Save the updated `_bmad-output/project-context.md`</action>
+
+  <output>
+✅ **Project-Specific Rules updated successfully!**
+
+- **File:** `_bmad-output/project-context.md`
+- **Rules added:** {{count_of_added_rules}}
+
+The new rules will be active in all AI agent sessions that load `project-context.md`
+via `critical_actions` (all BMAD agents load it automatically on activation).
+
+**Next:** Commit `_bmad-output/project-context.md` to version control so the rules
+are shared across the team and persist across sessions.
+  </output>
+
+</step>
+
+</workflow>

package/lib/bmad-extension-plugin/skills/project-context-expansion/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: project-context-expansion
+module: ma-skills

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

@@ -0,0 +1,184 @@
+---
+name: remove-from-sprint
+description: Guided workflow to move sprint items back to the backlog in the unified sprint-status.yaml using reverse movement semantics
+type: skill
+triggers:
+  - "remove from sprint"
+  - "move back to backlog"
+---
+
+# 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>**Pre-write: single-location invariant check.** Build {{current_backlog_ids}} = set of all item IDs currently in {{sprint_file}}.backlog. For each item in {{items_to_remove}}: check if its ID exists in {{current_backlog_ids}}. If ANY match is found:
+    <output>**Error:** Data integrity violation — item {{item.id}} already exists in the backlog. Aborting to prevent duplicate. The sprint-status.yaml file may be corrupted. No changes have been written.</output>
+    <action>Exit workflow without writing</action>
+  </action>
+
+  <action>**Pre-write: required field validation.** For each item in {{items_to_remove}}: verify it has all 6 required backlog fields present (the key must exist; epic and severity may be null by schema): id, type, epic, title, status, severity. (priority will be assigned by this skill.) If ANY item is missing a required field:
+    <output>**Error:** Item {{item.id}} is missing required field '{{missing_field}}'. Cannot safely return this item to the backlog. No changes have been written. Please inspect sprint-status.yaml manually.</output>
+    <action>Exit workflow without writing</action>
+  </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-plugin/skills/remove-from-sprint/bmad-skill-manifest.yaml

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

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

@@ -0,0 +1,177 @@
+---
+name: sprint-status-view
+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
+
+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`.
+
+---
+
+## 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-plugin/skills/sprint-status-view/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: sprint-status-view
+module: ma-skills