ma-agents 3.4.8 → 3.5.0

package/.opencode/skills/prioritize-backlog/SKILL.md

@@ -1,195 +0,0 @@
----
-name: prioritize-backlog
-description: Reprioritize backlog items using multiple criteria — severity, business value, dependencies, type, age
-type: skill
-triggers:
-  - "prioritize backlog"
-  - "reorder backlog"
-  - "reprioritize"
----
-
-# Prioritize-Backlog Workflow
-
-Reprioritize backlog items using multiple criteria — severity, business value, dependencies, type, and age.
-
-<workflow>
-
-<step n="1" goal="Load backlog and dependency data">
-  <action>Read `_bmad-output/implementation-artifacts/backlog.yaml`</action>
-  <check if="file missing or empty (no items)">
-    <output>No backlog found or backlog is empty. Nothing to prioritize.</output>
-    <action>Exit workflow</action>
-  </check>
-  <action>Store all backlog items as {{backlog_items}}</action>
-  <action>Infer implicit dependencies: stories belonging to the same epic are assumed to be sequential (lower story number before higher)</action>
-  <action>Read `_bmad-output/implementation-artifacts/epics.md` (or equivalent epics source) for any explicitly declared dependencies</action>
-  <action>Build {{dependency_map}} — for each item, list the IDs it depends on (must be completed before it can start)</action>
-</step>
-
-<step n="2" goal="Display current backlog ordering">
-  <output>
-## Current Backlog
-
-| # | Priority | ID | Title | Type | Epic | Status | Sprint | Severity | Dependencies |
-|---|---|---|---|---|---|---|---|---|---|
-{{#each backlog_items}}
-| {{@index+1}} | {{priority}} | {{id}} | {{title}} | {{type}} | {{epic}} | {{status}} | {{sprint}} | {{severity}} | {{dependencies}} |
-{{/each}}
-
-*Total: {{backlog_items.length}} items*
-  </output>
-</step>
-
-<step n="3" goal="Choose prioritization mode">
-  <ask>Choose prioritization mode:
-1. **Full reprioritization** — enter items in desired order, remaining appended at end
-2. **Quick adjust** — move individual items up/down
-3. **Auto-suggest** — AI analysis with weighted criteria
-4. **Cancel**
-
-Choice:</ask>
-  <check if="choice == 4">
-    <output>Cancelled. No changes made.</output>
-    <action>Exit workflow</action>
-  </check>
-</step>
-
-<step n="3a" goal="Full reprioritization" if="choice == 1">
-  <ask>Enter item numbers in your desired priority order (comma-separated). Items not listed will be appended in their current relative order:</ask>
-  <action>Resolve entered numbers against the backlog table from step 2</action>
-  <action>Build {{new_order}}: user-specified items first (in given order), then remaining items appended in their original relative order</action>
-  <goto step="4" />
-</step>
-
-<step n="3b" goal="Quick adjust" if="choice == 2">
-  <action>Initialize {{new_order}} as a copy of the current {{backlog_items}} list (preserving current ordering)</action>
-  <ask>Select item number to move:</ask>
-  <action>Store selected item as {{item_to_move}}</action>
-  <ask>Move to:
-- Enter a position number (1 = top, N = bottom)
-- Or enter 'u' to move up one position, 'd' to move down one position
-
-Target:</ask>
-  <action>Move {{item_to_move}} to the specified position in {{new_order}}</action>
-  <output>Moved "{{item_to_move.title}}" to position {{new_position}}.</output>
-  <ask>Continue? [m] Move another item / [d] Done adjusting:</ask>
-  <check if="user selects 'm'">
-    <action>Display current ordering</action>
-    <goto step="3b" />
-  </check>
-  <check if="user selects 'd'">
-    <goto step="4" />
-  </check>
-</step>
-
-<step n="3c" goal="Auto-suggest prioritization" if="choice == 3">
-  <action>Analyze all backlog items using weighted criteria:
-    1. **Blocking dependencies** (highest weight) — items that block other items should come first
-    2. **Severity** (bugs only) — critical > high > medium > low
-    3. **Business value** — infer from epic priority, item description, and type
-    4. **Type priority** — bugs generally before stories of equal value
-    5. **Age** — older items (lower story numbers, earlier creation) get slight priority boost
-  </action>
-  <action>Generate {{suggested_order}} with rationale for each item's position</action>
-  <output>
-## Auto-Suggested Priority Order
-
-| New # | ID | Title | Type | Rationale |
-|---|---|---|---|---|
-{{#each suggested_order}}
-| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{rationale}} |
-{{/each}}
-  </output>
-  <ask>Options:
-- [a] Accept this ordering
-- [m] Modify (switch to full reprioritization with this as starting point)
-- [r] Reject (return to mode selection)
-
-Choice:</ask>
-  <check if="user selects 'a'">
-    <action>Set {{new_order}} = {{suggested_order}}</action>
-    <goto step="4" />
-  </check>
-  <check if="user selects 'm'">
-    <action>Set current backlog display to {{suggested_order}}</action>
-    <goto step="3a" />
-  </check>
-  <check if="user selects 'r'">
-    <goto step="3" />
-  </check>
-</step>
-
-<step n="4" goal="Dependency validation">
-  <action>For each item in {{new_order}}, check if it appears before any item it depends on</action>
-  <check if="dependency violations found">
-    <output>
-**Dependency Warning:** The following items appear before their dependencies:
-
-{{#each violations}}
-- **{{item.id}}** (position {{item.position}}) depends on **{{dependency.id}}** (position {{dependency.position}})
-{{/each}}
-    </output>
-    <ask>How to proceed?
-- [o] Override — keep current order despite dependency warnings
-- [f] Fix — automatically reorder to satisfy dependencies
-- [c] Cancel — return to mode selection
-
-Choice:</ask>
-    <check if="user selects 'f'">
-      <action>Reorder {{new_order}} to satisfy dependency constraints (move dependency items before their dependents, preserving relative order otherwise)</action>
-      <output>Dependencies fixed. Updated ordering applied.</output>
-    </check>
-    <check if="user selects 'c'">
-      <goto step="3" />
-    </check>
-    <!-- if 'o', proceed with current order -->
-  </check>
-</step>
-
-<step n="5" goal="Confirm and persist new ordering">
-  <output>
-## Old vs New Priority Order
-
-| Position | Old | New |
-|---|---|---|
-{{#each comparison}}
-| {{position}} | {{old_id}} — {{old_title}} | {{new_id}} — {{new_title}} |
-{{/each}}
-  </output>
-  <ask>Provide a brief reason for this reprioritization:</ask>
-  <action>Store as {{reason}}</action>
-  <ask>Confirm? [y] Apply / [n] Cancel / [e] Edit order:</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="5" />
-  </check>
-
-  <action>Update `_bmad-output/implementation-artifacts/backlog.yaml`:
-    - Rewrite items in {{new_order}} sequence
-    - Set priority fields sequentially: 1, 2, 3, ..., N
-    - Add or update header comment: `# Reprioritized: {{current_date}} — {{reason}}`
-    - Preserve all other item fields unchanged
-  </action>
-  <output>
-## Reprioritization Complete
-
-**Items reordered:** {{new_order.length}}
-**Reason:** {{reason}}
-**Date:** {{current_date}}
-
-Updated priorities written to `_bmad-output/implementation-artifacts/backlog.yaml`.
-
-**Next Steps:**
-- Use `/sprint-status-view` to review sprint assignments
-- Use `/add-to-sprint` to assign top-priority items to a sprint
-  </output>
-</step>
-
-</workflow>

package/.opencode/skills/prioritize-backlog/bmad-skill-manifest.yaml

@@ -1,3 +0,0 @@
-type: skill
-name: prioritize-backlog
-module: ma-skills

package/.opencode/skills/project-context-expansion/SKILL.md

@@ -1,238 +0,0 @@
----
-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

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