ma-agents 3.4.7 → 3.4.9

package/.opencode/skills/modify-sprint/SKILL.md

@@ -0,0 +1,322 @@
+---
+name: modify-sprint
+description: Guided workflow to modify an existing sprint — add/remove items, change capacity, update metadata
+type: skill
+triggers:
+  - "modify sprint"
+  - "edit sprint"
+---
+
+<!-- PARTIALLY REWORKED: Item assignment is handled by /add-to-sprint (Story 17.4).
+     Item removal is handled by /remove-from-sprint (Story 17.5).
+     Sprint activation (planning -> active) is handled below (Step 3e).
+     The legacy workflow below still references old sprint-plan-{n}.yaml paths for
+     other operations. A full rework of modify-sprint is planned for a future story. -->
+
+> **Note:** Item assignment and removal are now handled by `/add-to-sprint` and `/remove-from-sprint`. Use the **Activate Sprint** option below to transition a sprint from `planning` to `active`.
+
+# Modify Sprint Workflow
+
+Guided workflow to modify an existing sprint — add/remove items, change capacity, update metadata.
+
+<workflow>
+
+<step n="3e" goal="Activate a sprint (planning -> active)">
+  <action>Glob `_bmad-output/implementation-artifacts/sprints/sprint-*.yaml` to discover all sprint files</action>
+  <check if="no sprint files found">
+    <output>No sprints found. Run `/add-sprint` first.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Read each sprint file; extract: id, name, status, capacity, items count</action>
+  <action>Display sprints table</action>
+  <output>
+## Available Sprints
+
+| # | ID | Name | Status | Items | Capacity |
+|---|---|---|---|---|---|
+{{#each sprints}}
+| {{@index+1}} | {{id}} | {{name}} | {{status}} | {{items_count}} | {{capacity}} |
+{{/each}}
+  </output>
+  <ask>Which sprint to activate? (enter number, or 'q' to cancel):</ask>
+  <check if="user enters 'q'">
+    <output>Cancelled.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Store selected sprint as {{target_sprint}}</action>
+
+  <!-- Validate transition -->
+  <check if="target_sprint.status != 'planning'">
+    <output>Only sprints in `planning` status can be activated. Sprint "{{target_sprint.name}}" is currently `{{target_sprint.status}}`.</output>
+    <action>Exit workflow</action>
+  </check>
+
+  <!-- Check single-active constraint -->
+  <action>Check if any other sprint has status `active`</action>
+  <check if="another sprint is already active">
+    <output>Cannot activate "{{target_sprint.name}}" — sprint "{{active_sprint.name}}" ({{active_sprint.id}}) is already active. Close it first before activating another sprint.</output>
+    <action>Exit workflow</action>
+  </check>
+
+  <ask>Activate "{{target_sprint.name}}" ({{target_sprint.id}})? This will set status to `active`. [y] Yes / [n] Cancel:</ask>
+  <check if="user selects 'n'">
+    <output>Cancelled.</output>
+    <action>Exit workflow</action>
+  </check>
+
+  <action>Set target_sprint.status = "active"</action>
+  <action>Update `last_modified` to current ISO timestamp</action>
+  <action>Write updated sprint file to `_bmad-output/implementation-artifacts/sprints/{{target_sprint.id}}.yaml`</action>
+  <output>
+Sprint "{{target_sprint.name}}" is now **active**.
+
+**Next Steps:**
+- Use `/add-to-sprint` to assign backlog items
+- Use `/sprint-status-view` to see sprint progress
+  </output>
+</step>
+
+<step n="1" goal="List available sprints and select one to modify">
+  <action>Glob `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` to discover all sprint artifact files</action>
+  <check if="no sprint files found">
+    <output>❌ No sprint plans found. Run `/add-sprint` first to create a sprint.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>For each sprint file found, read and extract: sprint_number, sprint_name, capacity, assigned_items, status, last_modified</action>
+  <output>
+## 🏃 Available Sprints
+
+| # | Sprint | Status | Capacity | Assigned | Remaining | Last Modified |
+|---|---|---|---|---|---|---|
+{{#each sprints}}
+| {{@index+1}} | {{sprint_name}} (Sprint {{sprint_number}}) | {{status}} | {{capacity}} | {{assigned_count}} | {{remaining}} | {{last_modified}} |
+{{/each}}
+  </output>
+  <ask>Select sprint to modify (enter number):</ask>
+  <action>Store selected sprint as {{target_sprint}}</action>
+  <action>Store {{session_last_modified}} = {{target_sprint.last_modified}} for later concurrency guard check</action>
+</step>
+
+<step n="2" goal="Display current sprint state">
+  <action>Initialize {{working_assigned_items}} = copy of {{target_sprint.assigned_items}} — this working list accumulates all add/remove changes made during this session before the final save</action>
+  <action>Calculate remaining capacity: {{remaining}} = {{target_sprint.capacity}} - length({{working_assigned_items}})</action>
+  <output>
+## Sprint: {{target_sprint.sprint_name}} (Sprint {{target_sprint.sprint_number}})
+
+- **Status:** {{target_sprint.status}}
+- **Capacity:** {{target_sprint.capacity}} items
+- **Assigned Items:** {{assigned_count}} / {{target_sprint.capacity}} ({{remaining}} remaining)
+- **Start Context:** {{target_sprint.start_context}}
+- **End Context:** {{target_sprint.end_context}}
+- **Last Modified:** {{target_sprint.last_modified}}
+
+### Assigned Items
+{{#if assigned_items_empty}}
+*(No items assigned yet)*
+{{else}}
+{{#each target_sprint.assigned_items}}
+- {{this}}
+{{/each}}
+{{/if}}
+  </output>
+</step>
+
+<step n="3" goal="Present modification menu">
+  <ask>What would you like to modify?
+
+1. **Add item** — assign a new backlog item to this sprint
+2. **Remove item** — remove an assigned item from this sprint
+3. **Change capacity** — update the sprint's maximum item capacity
+4. **Update metadata** — change sprint name, start/end context, or status
+5. **Done** — save all changes and exit
+
+Choice:</ask>
+  <check if="choice == 5 or 'done'">
+    <goto step="5" />
+  </check>
+</step>
+
+<step n="3a" goal="Add item" if="choice == 1">
+  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml` to get all user story keys and statuses</action>
+  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` for bug stories; parse YAML frontmatter for type, severity, title</action>
+  <action>Read ALL `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` files to build {{all_assigned_items}} — flat set of every item identifier assigned to any sprint (including the current sprint's {{working_assigned_items}})</action>
+  <action>Filter user stories: exclude items whose key is in {{all_assigned_items}} (already assigned to any sprint)</action>
+  <action>Filter bug stories: exclude items whose file basename is in {{all_assigned_items}} (already assigned to any sprint)</action>
+  <action>Build {{unassigned_items}} from the filtered stories and bugs, with: id, title, type (Story/Bug), status</action>
+  <output>
+## Unassigned Backlog Items
+
+| # | ID / File | Title | Type | Status |
+|---|---|---|---|---|
+{{#each unassigned_items}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{status}} |
+{{/each}}
+  </output>
+  <ask>Select item to add (enter number):</ask>
+  <action>Store selected item as {{item_to_add}}</action>
+  <action>Calculate: {{new_assigned_count}} = current assigned count + 1</action>
+  <check if="{{new_assigned_count}} > {{target_sprint.capacity}}">
+    <output>⚠️ **Capacity Warning:** Adding "{{item_to_add.title}}" would bring assigned items to {{new_assigned_count}}/{{target_sprint.capacity}} — exceeding capacity by {{overage}}.</output>
+    <ask>Options:
+- [a] Add anyway (over-capacity acknowledged)
+- [s] Skip — do not add this item
+- [c] Change capacity first (select option 3 from menu)
+
+Choice:</ask>
+    <check if="choice == 's'">
+      <goto step="3" />
+    </check>
+    <check if="choice == 'c'">
+      <goto step="3c" />
+    </check>
+  </check>
+  <action>Add {{item_to_add}} identifier to {{working_assigned_items}} list</action>
+  <action>Calculate remaining: {{remaining}} = {{target_sprint.capacity}} - length({{working_assigned_items}})</action>
+  <output>✅ Added "{{item_to_add.title}}" to sprint. Updated capacity: {{length(working_assigned_items)}}/{{target_sprint.capacity}} items ({{remaining}} remaining)</output>
+  <goto step="3" />
+</step>
+
+<step n="3b" goal="Remove item" if="choice == 2">
+  <check if="{{working_assigned_items}} is empty">
+    <output>ℹ️ No items are currently assigned to this sprint.</output>
+    <goto step="3" />
+  </check>
+  <action>Resolve each identifier in {{working_assigned_items}} to its display name and type:
+    - For story identifiers (matching pattern `^\d+-\d+-.+`): infer title from key by converting kebab segments to title case (e.g., `12-1-add-sprint-workflow` → "Add Sprint Workflow"); type = "Story"; look up status in sprint-status.yaml if available
+    - For bug identifiers (matching pattern `^bug-.+`): look up in bug-*.md frontmatter (re-glob if not already loaded this step) for title and severity; type = "Bug"
+    - If resolution fails for any identifier, display the raw identifier as title with type "Unknown"
+  </action>
+  <output>
+## Currently Assigned Items
+
+| # | ID / File | Title | Type |
+|---|---|---|---|
+{{#each working_assigned_items}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} |
+{{/each}}
+  </output>
+  <ask>Select item to remove (enter number):</ask>
+  <action>Remove selected item from {{working_assigned_items}} list</action>
+  <action>Calculate remaining: {{remaining}} = {{target_sprint.capacity}} - length({{working_assigned_items}})</action>
+  <output>✅ Removed item from sprint. Updated capacity: {{length(working_assigned_items)}}/{{target_sprint.capacity}} items ({{remaining}} remaining)</output>
+  <goto step="3" />
+</step>
+
+<step n="3c" goal="Change capacity" if="choice == 3">
+  <ask>Enter new capacity (positive integer — current: {{target_sprint.capacity}}):</ask>
+  <action>Validate input is a positive integer (greater than zero)</action>
+  <check if="input is NOT a positive integer">
+    <output>❌ Invalid capacity. Must be a positive integer greater than zero.</output>
+    <goto step="3c" />
+  </check>
+  <action>Store {{new_capacity}} = validated integer input</action>
+  <action>Calculate: {{new_remaining}} = {{new_capacity}} - length({{working_assigned_items}})</action>
+  <output>✅ Capacity updated: {{target_sprint.capacity}} → {{new_capacity}} ({{new_remaining}} slots remaining with current {{length(working_assigned_items)}} assigned items)</output>
+  <action>Update {{target_sprint.capacity}} = {{new_capacity}} in working state</action>
+  <goto step="3" />
+</step>
+
+<step n="3d" goal="Update metadata" if="choice == 4">
+  <ask>Which metadata to update?
+1. Sprint name (current: "{{target_sprint.sprint_name}}")
+2. Start context (current: "{{target_sprint.start_context}}")
+3. End context (current: "{{target_sprint.end_context}}")
+4. Status (current: {{target_sprint.status}} — options: planning / active / completed)
+5. Back to menu
+
+Choice:</ask>
+  <check if="choice == 1">
+    <ask>New sprint name:</ask>
+    <action>Update {{target_sprint.sprint_name}} in working state</action>
+    <output>✅ Sprint name updated.</output>
+  </check>
+  <check if="choice == 2">
+    <ask>New start context (date or milestone):</ask>
+    <action>Update {{target_sprint.start_context}} in working state</action>
+    <output>✅ Start context updated.</output>
+  </check>
+  <check if="choice == 3">
+    <ask>New end context (date or milestone):</ask>
+    <action>Update {{target_sprint.end_context}} in working state</action>
+    <output>✅ End context updated.</output>
+  </check>
+  <check if="choice == 4">
+    <ask>New status (planning / active / completed):</ask>
+    <action>Validate input is one of: planning, active, completed</action>
+    <check if="invalid status">
+      <output>❌ Invalid status. Choose: planning, active, or completed.</output>
+    </check>
+    <action>Update {{target_sprint.status}} in working state</action>
+    <output>✅ Sprint status updated.</output>
+  </check>
+  <check if="choice == 5">
+    <goto step="3" />
+  </check>
+  <goto step="3" />
+</step>
+
+<step n="4" goal="Concurrency guard — re-read before writing">
+  <action>Re-read the sprint artifact file: `_bmad-output/implementation-artifacts/sprint-plan-{{target_sprint.sprint_number}}.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 artifact was modified externally since this session started.
+
+**Session started with:** `last_modified: {{session_last_modified}}`
+**Current file has:** `last_modified: {{current_file_last_modified}}`
+
+**Current sprint state (re-read from file):**
+    </output>
+    <action>Display the full current state of the sprint artifact (re-read content)</action>
+    <ask>The file has changed. Review the current state above and confirm how to proceed:
+- [o] Overwrite with your changes from this session (your modifications will replace current file content)
+- [m] Merge — restart modifications from the current file state
+- [x] Cancel — discard all session changes
+
+Choice:</ask>
+    <check if="choice == 'x'">
+      <output>❌ Changes discarded. Sprint file not modified.</output>
+      <action>Exit workflow</action>
+    </check>
+    <check if="choice == 'm'">
+      <action>Reload {{target_sprint}} from current file content</action>
+      <action>Update {{session_last_modified}} to current file's last_modified</action>
+      <action>Reset {{working_assigned_items}} to current file's assigned_items</action>
+      <output>🔄 Reloaded sprint from current state. Please re-apply your modifications.</output>
+      <goto step="3" />
+    </check>
+    <!-- if 'o', proceed to write with session changes -->
+  </check>
+</step>
+
+<step n="5" goal="Persist changes to sprint artifact">
+  <action>Invoke concurrency guard (Step 4) before writing</action>
+  <action>Get current ISO timestamp for last_modified</action>
+  <action>Write updated sprint data back to `_bmad-output/implementation-artifacts/sprint-plan-{{target_sprint.sprint_number}}.yaml`:
+    - Update `sprint_name` if changed
+    - Update `capacity` if changed
+    - Update `assigned_items` with final working list
+    - Update `status` if changed
+    - Update `start_context` if changed
+    - Update `end_context` if changed
+    - Update `last_modified` to current ISO timestamp
+    - Preserve `sprint_number`, `created_date` unchanged
+  </action>
+  <action>**Do NOT modify sprint-status.yaml** — sprint membership is exclusively in sprint-plan-{n}.yaml. sprint-status.yaml is read-only from this workflow.</action>
+  <action>Calculate final remaining capacity</action>
+  <output>
+## ✅ Sprint Updated Successfully
+
+**Sprint:** {{target_sprint.sprint_name}} (Sprint {{target_sprint.sprint_number}})
+**File:** `_bmad-output/implementation-artifacts/sprint-plan-{{target_sprint.sprint_number}}.yaml`
+**Capacity:** {{final_capacity}} items ({{final_remaining}} remaining)
+**Assigned Items:** {{final_assigned_count}}
+**Status:** {{target_sprint.status}}
+
+**Next Steps:**
+- Use `/add-to-sprint` to assign more backlog items
+- Use `/sprint-status-view` to view full sprint progress
+  </output>
+</step>
+
+</workflow>

package/.opencode/skills/modify-sprint/bmad-skill-manifest.yaml

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

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