ma-agents 3.4.7 → 3.4.8

package/.opencode/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/.opencode/skills/project-context-expansion/bmad-skill-manifest.yaml

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

package/.opencode/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/.opencode/skills/remove-from-sprint/bmad-skill-manifest.yaml

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

package/.opencode/skills/sprint-status-view/SKILL.md

@@ -0,0 +1,263 @@
+---
+name: sprint-status-view
+description: Display sprint progress with capacity, items, and backlog. Regenerates sprint-status.yaml.
+type: skill
+triggers:
+  - "sprint status view"
+  - "view sprint status"
+---
+
+# Sprint Status View Workflow
+
+Display sprint status with capacity, items, and backlog summary. Regenerates `sprint-status.yaml` from authoritative sources.
+
+<workflow>
+
+<step n="1" goal="Suggest running /cleanup-done first">
+  <output>
+**Tip:** Consider running `/cleanup-done` before viewing sprint status to archive completed items and free capacity.
+  </output>
+  <action>Continue to next step (advisory only -- do not auto-invoke /cleanup-done)</action>
+</step>
+
+<step n="2" goal="Load data sources">
+  <action>Glob `_bmad-output/implementation-artifacts/sprints/sprint-*.yaml` to discover all sprint entity files</action>
+  <action>Store discovered sprint files as {{sprint_files}} list</action>
+
+  <action>Read `_bmad-output/implementation-artifacts/backlog.yaml` if it exists</action>
+  <action>Store the backlog items list as {{backlog_items}} (or empty list if file not found)</action>
+
+  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` to discover all bug story files (fallback for bug metadata)</action>
+  <action>For each bug file found, parse YAML frontmatter to extract: title, severity, status</action>
+  <action>Store as {{bug_metadata_map}} keyed by file basename (e.g., `bug-login-crash`)</action>
+
+  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml` if it exists (fallback for story status when backlog.yaml is missing or incomplete)</action>
+  <action>Parse development_status section into {{status_fallback_map}} -- key: story key, value: status</action>
+  <action>Exclude epic-* keys and *-retrospective keys from the fallback map</action>
+
+  <check if="no sprint files found AND no backlog.yaml exists">
+    <output>
+**No Sprint Data Found**
+
+No sprint files exist (`sprints/sprint-*.yaml`) and no `backlog.yaml` was found.
+
+**To get started:**
+1. Run `/generate-backlog` to create a backlog from your epics
+2. Run `/add-sprint` to create your first sprint
+3. Run `/add-to-sprint` to assign backlog items to it
+    </output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="3" goal="Display each sprint">
+  <action>For each sprint in {{sprint_files}}, read the full YAML content</action>
+  <action>Sort sprints for display: active first, then planning, then closed</action>
+  <action>Initialize {{total_done_in_sprints}} = 0 for step 4</action>
+
+  <action>For each sprint (in sorted order):
+
+    **If sprint.status is "closed":**
+    - Count total items in sprint.items
+    - Display collapsed summary line only
+
+    **If sprint.status is NOT "closed" (active or planning):**
+    - Calculate {{item_count}} = length(sprint.items)
+    - For each item identifier in sprint.items, resolve details:
+      - Look up item in {{backlog_items}} by matching `id` field
+      - If found in backlog: use `type`, `title`, `status`, `severity` from backlog entry
+      - If NOT found in backlog and item matches `^bug-`: look up in {{bug_metadata_map}} for title/severity, use status from bug frontmatter or default to "backlog"
+      - If NOT found in backlog and item matches a story pattern: look up in {{status_fallback_map}} for status, infer title from key, set type to "story"
+      - If item cannot be resolved from any source: display with raw identifier, type "unknown", status "unknown"
+    - If resolved item status is "done", increment {{total_done_in_sprints}}
+    - Build capacity bar: `[===---]` style where `=` represents filled slots and `-` represents remaining capacity
+  </action>
+
+  <action>Display non-closed sprints:</action>
+  <output>
+{{#each non_closed_sprints}}
+---
+
+## {{sprint.name}} ({{sprint.status}}) -- {{item_count}}/{{sprint.capacity}} items
+
+{{#if sprint.start}}**Start:** {{sprint.start}}{{/if}}{{#if sprint.end}} | **End:** {{sprint.end}}{{/if}}
+
+| Item | Type | Status |
+|---|---|---|
+{{#each resolved_items}}
+| {{id}} | {{#if is_story}}[story]{{/if}}{{#if is_bug}}[bug, {{severity}}]{{/if}} | {{status}} |
+{{/each}}
+{{#if items_empty}}
+*(No items assigned)*
+{{/if}}
+
+**Capacity:** {{capacity_bar}}
+{{/each}}
+  </output>
+
+  <action>Display closed sprints:</action>
+  <output>
+{{#each closed_sprints}}
+---
+**{{sprint.name}}** (closed) -- {{item_count}} items completed
+{{/each}}
+  </output>
+</step>
+
+<step n="4" goal="Completed items summary">
+  <action>Count items with status "done" that are still present in non-closed sprint files (use {{total_done_in_sprints}} from step 3)</action>
+  <check if="total_done_in_sprints > 0">
+    <output>
+---
+
+## Completed Items
+
+{{total_done_in_sprints}} done item(s) are still in sprint files. Run `/cleanup-done` to archive them and free capacity.
+    </output>
+  </check>
+  <check if="total_done_in_sprints == 0">
+    <action>Skip this section -- no done items lingering in sprints</action>
+  </check>
+</step>
+
+<step n="5" goal="Unassigned backlog">
+  <action>Filter {{backlog_items}} to find items where sprint is null (unassigned)</action>
+  <action>Exclude items with status "done" from the unassigned list</action>
+  <action>Sort unassigned items by priority ascending (lowest number = highest priority)</action>
+  <action>Store as {{unassigned_items}}</action>
+  <action>Store total count as {{unassigned_total}}</action>
+  <action>Take top 15 items for display as {{unassigned_display}}</action>
+
+  <check if="unassigned_total > 0">
+    <output>
+---
+
+## Unassigned Backlog
+
+| # | Item | Type | Priority | Status |
+|---|---|---|---|---|
+{{#each unassigned_display}}
+| {{priority}} | {{id}} | {{type}} | {{priority}} | {{status}} |
+{{/each}}
+{{#if unassigned_total > 15}}
+
+... and {{unassigned_total - 15}} more
+{{/if}}
+    </output>
+  </check>
+  <check if="unassigned_total == 0">
+    <output>
+---
+
+## Unassigned Backlog
+
+*(All backlog items are assigned to sprints)*
+    </output>
+  </check>
+</step>
+
+<step n="6" goal="Next actions menu">
+  <ask>
+**Next Actions:**
+[1] Full backlog
+[2] /add-to-sprint
+[3] /remove-from-sprint
+[4] /prioritize-backlog
+[5] /add-sprint
+[6] /cleanup-done
+[7] Exit
+
+Choice:
+  </ask>
+  <check if="choice == 1">
+    <action>Display all items from {{backlog_items}} in a table: id, type, priority, status, sprint, severity</action>
+    <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 `/remove-from-sprint` to remove items from a sprint.</output>
+  </check>
+  <check if="choice == 4">
+    <output>Run `/prioritize-backlog` to reorder backlog priorities.</output>
+  </check>
+  <check if="choice == 5">
+    <output>Run `/add-sprint` to create a new sprint.</output>
+  </check>
+  <check if="choice == 6">
+    <output>Run `/cleanup-done` to archive completed items from sprints.</output>
+  </check>
+  <check if="choice == 7">
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="7" goal="Regenerate sprint-status.yaml (internal)" internal="true">
+  <action>This step runs automatically after display (steps 3-6) completes, before the workflow exits.</action>
+
+  <action>Read existing `_bmad-output/implementation-artifacts/sprint-status.yaml` if it exists</action>
+  <action>Preserve the STATUS DEFINITIONS comment block at the top of the file (lines starting with `#` that define status values)</action>
+  <action>Preserve any epic-* keys and *-retrospective keys from the existing file</action>
+
+  <action>Build the new development_status section:
+    - Source 1: {{backlog_items}} from backlog.yaml -- for each item where status is NOT "done", add an entry: key = item.id, value = item.status
+    - Source 2: sprint entity files -- for each sprint, for each item in sprint.items, ensure the item has an entry. If the item was already added from backlog.yaml, the backlog value wins. If the item is NOT in backlog.yaml, look up status from {{bug_metadata_map}} or {{status_fallback_map}}.
+    - Exclude items with status "done" -- only non-done items appear in sprint-status.yaml
+  </action>
+
+  <action>Collect sprint metadata for header comments:
+    - For each sprint: id, name, status, item count, capacity
+  </action>
+
+  <action>Get current ISO timestamp as {{generated_at}}</action>
+
+  <action>Write `_bmad-output/implementation-artifacts/sprint-status.yaml` with this structure:
+
+```yaml
+# generated: {{original_generated_date or generated_at}}
+# updated: {{generated_at}} — regenerated by sprint-status-view
+# project: {{project_name from existing file or "unknown"}}
+# project_key: {{project_key from existing file or "NOKEY"}}
+# tracking_system: file-system
+# story_location: _bmad-output/implementation-artifacts
+#
+# Sprints:
+{{#each sprints}}
+#   {{sprint.id}}: {{sprint.name}} ({{sprint.status}}) — {{item_count}}/{{sprint.capacity}} items
+{{/each}}
+#
+# STATUS DEFINITIONS:
+# ==================
+# (preserve the full STATUS DEFINITIONS block from the existing file verbatim)
+# If no existing file, use these defaults:
+# backlog        — item is in the backlog, not yet started
+# ready-for-dev  — story file created, ready for development
+# in-progress    — item is actively being worked on
+# review         — item is in review
+# done           — item is complete (excluded from this file)
+
+{{#if preserved_epic_keys}}
+# Epic tracking
+{{#each preserved_epic_keys}}
+{{key}}: {{value}}
+{{/each}}
+{{/if}}
+
+development_status:
+{{#each active_items}}
+  {{id}}: {{status}}
+{{/each}}
+
+{{#if preserved_retro_keys}}
+# Retrospective tracking
+{{#each preserved_retro_keys}}
+{{key}}: {{value}}
+{{/each}}
+{{/if}}
+```
+
+  </action>
+</step>
+
+</workflow>

package/.opencode/skills/sprint-status-view/bmad-skill-manifest.yaml

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