ma-agents 3.6.2 → 3.9.0

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

@@ -0,0 +1,350 @@
+---
+name: modify-sprint
+description: Guided workflow to modify an existing sprint's metadata (name, capacity, dates, status) within the sprints section of sprint-status.yaml
+type: skill
+triggers:
+  - "modify sprint"
+  - "edit sprint"
+---
+
+# Modify Sprint Workflow
+
+Guided workflow to modify an existing sprint's metadata (name, capacity, dates, status) within the `sprints` section of `sprint-status.yaml`.
+
+> **Scope:** This skill modifies sprint **metadata only** — name, capacity, start date, end date, and status.
+> To assign items to a sprint, use `/add-to-sprint`. To remove items, use `/remove-from-sprint`.
+
+## Backend Routing
+
+Before executing any file-system operations, determine and route to the correct backend:
+
+1. Read `_bmad-output/implementation-artifacts/sprint-status.yaml` and extract the `tracking_system` field.
+   If the field is absent or the file does not exist, default to `file-system`.
+
+2. If `tracking_system` is `file-system`:
+   Proceed with the **File-System Backend** instructions below.
+
+3. If `tracking_system` is `jira`:
+   a. Perform the Jira operation: Find the sprint by name or ID in the board for project `{jira_project_key}` at `{jira_url}`. Update the sprint's name, dates, or goal using the sprint update API. If the status is being changed to `active`: start the sprint using the sprint start API (transitions the sprint from future/planning to active state — enforces the single-active-sprint constraint).
+      Use whatever Jira-capable tool is available in your current tool context.
+      Map Jira entities to the canonical schema (Sprint → sprints[], Backlog → backlog[],
+      Epic → epics[], Jira status → canonical vocabulary per Section 6.3 of the routing spec).
+   b. If the Jira operation SUCCEEDS: continue with the Jira data returned. Jira is the source of truth.
+   c. If the Jira operation FAILS for any reason:
+      - If no Jira-capable tool is available in your current context:
+        Pause and present the user with:
+        > "No Jira-capable tool is available. To use Jira tracking, configure a Jira integration
+        > in your agent (an MCP server, plugin, or native integration connected to the Jira
+        > instance at `{jira_url}`). How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again once a Jira tool is configured
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      - If a Jira tool attempted the operation but returned an error:
+        Pause and present the user with:
+        > "The Jira operation failed: {actual Jira error details}. How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      If user chooses (b) in either case: write `tracking_system: file-system` to `sprint-status.yaml`,
+      update `sprint_backend: file-system` in `_bmad/bmm/config.yaml`,
+      then proceed with **File-System Backend** instructions below.
+
+4. **File-System Backend** — execute the workflow steps below.
+
+---
+
+<workflow>
+
+<step n="0" goal="Load configuration and validate file existence">
+  <action>Resolve the path to `sprint-status.yaml` using `_bmad/bmm/config.yaml` if available; default path is `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
+  <check if="file does not exist">
+    <output>❌ No sprint-status.yaml found. Run sprint planning first to initialize the file.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Read and parse the full file, retaining all three sections: `epics`, `backlog`, and `sprints`</action>
+  <action>Store file contents as {{file_content}} for use in the final atomic write</action>
+</step>
+
+<step n="1" goal="Identify available sprints and select one to modify">
+  <action>Parse the `sprints` section from the loaded file</action>
+  <check if="sprints section is empty ({})">
+    <output>❌ No sprints found. Run `/add-sprint` first to create a sprint.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Build sprint list with: sprint ID (map key), name, status, capacity, item count (length of items array), start, end</action>
+  <output>
+## 🏃 Available Sprints
+
+| # | Sprint ID | Name | Status | Capacity | Items | Start | End |
+|---|---|---|---|---|---|---|---|
+{{#each sprints}}
+| {{@index+1}} | {{sprint_id}} | {{name}} | {{status}} | {{capacity}} | {{item_count}}/{{capacity}} | {{start_or_not_set}} | {{end_or_not_set}} |
+{{/each}}
+
+Note: closed sprints are immutable and cannot be modified.
+  </output>
+  <ask>Select sprint to modify (enter number):</ask>
+  <action>Store selected sprint as {{target_sprint}} and its map key as {{sprint_id}}</action>
+  <check if="{{target_sprint.status}} == 'closed'">
+    <output>⚠️ Sprint '{{target_sprint.name}}' ({{sprint_id}}) is closed. Closed sprints are immutable (schema constraint 6.7). Only archival operations are permitted.</output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="2" goal="Display current sprint state">
+  <action>Calculate {{item_count}} = length of {{target_sprint.items}} array</action>
+  <action>Calculate {{remaining}} = {{target_sprint.capacity}} - {{item_count}}</action>
+  <output>
+## Sprint: {{target_sprint.name}} ({{sprint_id}})
+
+- **Status:** {{target_sprint.status}}
+- **Capacity:** {{target_sprint.capacity}} items ({{item_count}} assigned, {{remaining}} remaining)
+- **Start:** {{target_sprint.start || "not set"}}
+- **End:** {{target_sprint.end || "not set"}}
+- **Items:** {{item_count}} assigned (use /add-to-sprint or /remove-from-sprint to manage items)
+
+### Assigned Items (read-only)
+{{#if items_empty}}
+*(No items assigned yet)*
+{{else}}
+| ID | Title | Type | Status |
+|---|---|---|---|
+{{#each target_sprint.items}}
+| {{id}} | {{title}} | {{type}} | {{status}} |
+{{/each}}
+{{/if}}
+  </output>
+  <action>Initialize {{working_changes}} = empty map to accumulate changes made during this session</action>
+  <action>Initialize working state aliases: {{current_name}} = {{target_sprint.name}}, {{current_capacity}} = {{target_sprint.capacity}}, {{current_start}} = {{target_sprint.start}}, {{current_end}} = {{target_sprint.end}}, {{current_status}} = {{target_sprint.status}}. These aliases are updated in-place as changes are made so Step 3's menu always shows the latest values.</action>
+  <action>Store {{original_name}} = {{target_sprint.name}} (preserved as the display name in the confirmation summary)</action>
+</step>
+
+<step n="3" goal="Present modification menu">
+  <output>
+## What would you like to modify?
+
+1. **Sprint name** (current: "{{current_name}}")
+2. **Capacity** (current: {{current_capacity}})
+3. **Start date** (current: {{current_start || "not set"}})
+4. **End date** (current: {{current_end || "not set"}})
+5. **Status** (current: {{current_status}})
+6. **Done** -- save all changes and exit
+  </output>
+  <ask>Choice:</ask>
+  <check if="choice == 6 or choice == 'done'">
+    <goto step="4" />
+  </check>
+</step>
+
+<step n="3a" goal="Modify sprint name" if="choice == 1">
+  <ask>New sprint name (current: '{{current_name}}'):</ask>
+  <check if="input is empty">
+    <output>❌ Sprint name cannot be empty. Please enter a valid name.</output>
+    <goto step="3a" />
+  </check>
+  <action>Store {{new_name}} = input</action>
+  <action>Store change: name: {{current_name}} -> {{new_name}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_name}} = {{new_name}}</action>
+  <output>✅ Sprint name updated: '{{old_name}}' -> '{{new_name}}'.</output>
+  <goto step="3" />
+</step>
+
+<step n="3b" goal="Modify capacity" if="choice == 2">
+  <ask>New capacity (positive integer, current: {{current_capacity}}):</ask>
+  <action>Validate input is a positive integer (greater than zero, no decimals, no non-numeric characters)</action>
+  <check if="input is NOT a positive integer">
+    <output>❌ Invalid capacity. Must be a positive integer greater than zero.</output>
+    <goto step="3b" />
+  </check>
+  <action>Store {{new_capacity}} = validated integer input</action>
+  <action>Calculate {{item_count}} = length of {{target_sprint.items}} array</action>
+  <check if="{{new_capacity}} < {{item_count}}">
+    <output>⚠️ Sprint has {{item_count}} items but new capacity would be {{new_capacity}} ({{new_capacity}} < {{item_count}}). Capacity is advisory -- items will not be removed.</output>
+    <ask>Options:
+- [a] Apply anyway (capacity is advisory per schema section 4.2)
+- [s] Skip -- keep current capacity
+- [r] Remove items first (direct to /remove-from-sprint)
+
+Choice:</ask>
+    <check if="choice == 's'">
+      <goto step="3" />
+    </check>
+    <check if="choice == 'r'">
+      <output>Run `/remove-from-sprint` to remove items, then re-run `/modify-sprint`.</output>
+      <action>Exit workflow</action>
+    </check>
+    <!-- if 'a', proceed with the change -->
+  </check>
+  <action>Calculate {{new_remaining}} = {{new_capacity}} - {{item_count}}</action>
+  <action>Store change: capacity: {{current_capacity}} -> {{new_capacity}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_capacity}} = {{new_capacity}}</action>
+  <output>✅ Capacity updated: {{old_capacity}} -> {{new_capacity}} ({{new_remaining}} slots remaining with {{item_count}} assigned items).</output>
+  <goto step="3" />
+</step>
+
+<step n="3c" goal="Modify start date" if="choice == 3">
+  <ask>New start date (ISO format YYYY-MM-DD, or press Enter to clear):</ask>
+  <check if="input is empty">
+    <action>Store {{new_start}} = "" (clears the date)</action>
+  </check>
+  <check if="input is not empty">
+    <action>Validate input matches ISO date format YYYY-MM-DD (regex: ^\d{4}-\d{2}-\d{2}$) and represents a valid calendar date</action>
+    <check if="invalid format">
+      <output>❌ Invalid date format. Use YYYY-MM-DD (e.g., 2026-05-01).</output>
+      <goto step="3c" />
+    </check>
+    <action>Store {{new_start}} = input</action>
+  </check>
+  <action>Store change: start: {{current_start || "not set"}} -> {{new_start || "not set"}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_start}} = {{new_start}}</action>
+  <output>✅ Start date updated: '{{old_start || "not set"}}' -> '{{new_start || "not set"}}'.</output>
+  <goto step="3" />
+</step>
+
+<step n="3d" goal="Modify end date" if="choice == 4">
+  <ask>New end date (ISO format YYYY-MM-DD, or press Enter to clear):</ask>
+  <check if="input is empty">
+    <action>Store {{new_end}} = "" (clears the date)</action>
+  </check>
+  <check if="input is not empty">
+    <action>Validate input matches ISO date format YYYY-MM-DD (regex: ^\d{4}-\d{2}-\d{2}$) and represents a valid calendar date</action>
+    <check if="invalid format">
+      <output>❌ Invalid date format. Use YYYY-MM-DD (e.g., 2026-05-31).</output>
+      <goto step="3d" />
+    </check>
+    <action>Store {{new_end}} = input</action>
+  </check>
+  <action>Determine effective start: use {{current_start}} if start not changed this session, else use newly entered start</action>
+  <check if="{{new_end}} is not empty AND {{effective_start}} is not empty AND {{new_end}} < {{effective_start}}">
+    <output>⚠️ Warning: End date ({{new_end}}) is before start date ({{effective_start}}). This may be intentional.</output>
+  </check>
+  <action>Store change: end: {{current_end || "not set"}} -> {{new_end || "not set"}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_end}} = {{new_end}}</action>
+  <output>✅ End date updated: '{{old_end || "not set"}}' -> '{{new_end || "not set"}}'.</output>
+  <goto step="3" />
+</step>
+
+<step n="3e" goal="Modify status" if="choice == 5">
+  <action>Determine valid transitions based on {{current_status}}:
+    - If `planning`: valid next state is `active` only
+    - If `active`: valid next state is `closed` only
+    - If `closed`: no transitions available (immutable)
+  </action>
+  <output>
+Current status: **{{current_status}}**
+{{#if current_status == 'planning'}}Valid transitions: planning -> active{{/if}}
+{{#if current_status == 'active'}}Valid transitions: active -> closed{{/if}}
+{{#if current_status == 'closed'}}No transitions available. Closed sprints are immutable.{{/if}}
+  </output>
+  <check if="{{current_status}} == 'closed'">
+    <output>⚠️ Sprint '{{current_name}}' is closed. Closed sprints are immutable (schema constraint 6.7). Only archival operations are permitted.</output>
+    <goto step="3" />
+  </check>
+  <ask>New status:</ask>
+  <action>Validate transition:
+    - planning -> active: allowed (proceed to single-active-sprint check)
+    - active -> closed: allowed (with warning about /close-sprint)
+    - planning -> closed: REJECTED (skip)
+    - active -> planning: REJECTED (backward)
+    - closed -> anything: REJECTED (immutable -- already handled above)
+    - same state -> same state: REJECTED (no change)
+    - any unrecognized value: REJECTED
+  </action>
+  <check if="transition is invalid (backward, skip, or unrecognized)">
+    <output>❌ Invalid status transition: {{current_status}} -> {{requested_status}}. Sprint status transitions are forward-only: planning -> active -> closed.</output>
+    <goto step="3e" />
+  </check>
+  <check if="requested_status == 'closed'">
+    <output>⚠️ To properly close a sprint with item disposition (archiving done items, returning incomplete items to backlog), use `/close-sprint` instead. This will only update the status field.</output>
+    <ask>Continue with status-only change? [y/n]</ask>
+    <check if="answer == 'n'">
+      <output>Status change cancelled. Use `/close-sprint` for full sprint close lifecycle.</output>
+      <goto step="3" />
+    </check>
+  </check>
+  <check if="requested_status == 'active'">
+    <action>Scan all other sprints in the `sprints` map for any sprint with status: active</action>
+    <check if="another active sprint found">
+      <output>⚠️ Sprint '{{other_sprint_name}}' ({{other_sprint_id}}) is already active. Only one sprint can be active at a time (schema constraint 6.4). Close it first or cancel this change.</output>
+      <ask>Options:
+- [c] Cancel status change
+- [x] Exit to run /close-sprint on {{other_sprint_id}} first
+
+Choice:</ask>
+      <check if="choice == 'c'">
+        <goto step="3" />
+      </check>
+      <check if="choice == 'x'">
+        <output>Run `/close-sprint` on {{other_sprint_id}} first, then re-run `/modify-sprint`.</output>
+        <action>Exit workflow</action>
+      </check>
+    </check>
+  </check>
+  <action>Store change: status: {{current_status}} -> {{requested_status}} in {{working_changes}}</action>
+  <action>Update current display value: {{current_status}} = {{requested_status}}</action>
+  <output>✅ Status updated: {{old_status}} -> {{requested_status}}.</output>
+  <goto step="3" />
+</step>
+
+<step n="4" goal="Confirmation -- review and confirm all changes">
+  <check if="{{working_changes}} is empty">
+    <output>ℹ️ No modifications made.</output>
+    <action>Exit workflow</action>
+  </check>
+  <output>
+## Modification Summary -- Please Confirm
+
+Sprint: {{sprint_id}} ("{{original_name}}")
+
+Changes:
+{{#each working_changes}}
+- {{field}}: {{old_value}} -> {{new_value}}
+{{/each}}
+
+All other sprint data (items, other sprints, epics, backlog) will be preserved unchanged.
+  </output>
+  <ask>Confirm changes? [y] Yes / [n] Cancel / [e] Edit more</ask>
+  <check if="choice == 'n'">
+    <output>❌ Changes discarded.</output>
+    <action>Exit workflow</action>
+  </check>
+  <check if="choice == 'e'">
+    <goto step="3" />
+  </check>
+  <!-- if 'y', proceed to Step 5 -->
+</step>
+
+<step n="5" goal="Persist changes to sprint-status.yaml">
+  <action>Re-read `sprint-status.yaml` (using the resolved path from Step 0) to get the latest file state before writing</action>
+  <action>Locate the target sprint entry at `sprints.{{sprint_id}}` in the re-read file</action>
+  <action>Apply all confirmed changes to the target sprint entry:
+    - If name was changed: update `name` field
+    - If capacity was changed: update `capacity` field
+    - If start was changed: update `start` field
+    - If end was changed: update `end` field
+    - If status was changed: update `status` field
+  </action>
+  <action>Preserve the sprint's `items` array exactly as-is (no modifications)</action>
+  <action>Preserve all other sprint entries in the `sprints` map exactly as-is</action>
+  <action>Preserve the `epics` section exactly as-is</action>
+  <action>Preserve the `backlog` section exactly as-is</action>
+  <action>Preserve the `generated` field exactly as-is (never change)</action>
+  <action>Set `last_updated` to the current ISO-8601 timestamp</action>
+  <action>Write the complete updated file in a single atomic write to `sprint-status.yaml`</action>
+  <output>
+## ✅ Sprint Modified Successfully!
+
+**Sprint:** {{sprint_name}} ({{sprint_id}})
+{{#each working_changes}}
+- **{{field}}:** {{new_value}}
+{{/each}}
+
+**Next Steps:**
+- Use `/add-to-sprint` to assign backlog items to this sprint
+- Use `/remove-from-sprint` to remove items from this sprint
+- Use `/sprint-status-view` to view sprint progress
+- Use `/close-sprint` to close this sprint when complete
+  </output>
+</step>
+
+</workflow>

package/lib/bmad-extension-plugin/skills/modify-sprint/bmad-skill-manifest.yaml

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

package/lib/bmad-extension-plugin/skills/module-help.csv

@@ -0,0 +1,62 @@
+module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
+ma-skills,anytime,SRE Agent,ma-agent-sre,,skill:ma-agent-sre,ma-agent-sre,false,bmm-sre,,"Site Reliability Engineer agent for system availability, reliability, and Kubernetes operations.",output_folder,"agent customization",
+ma-skills,anytime,DevOps Agent,ma-agent-devops,,skill:ma-agent-devops,ma-agent-devops,false,bmm-devops,,"DevOps Engineer agent for CI/CD pipeline automation, Infrastructure as Code, and cloud-native technologies.",output_folder,"agent customization",
+ma-skills,anytime,Cyber Agent,ma-agent-cyber,,skill:ma-agent-cyber,ma-agent-cyber,false,bmm-cyber,,"Cyber Security Analyst agent for vulnerability assessment, threat modeling, and system hardening.",output_folder,"agent customization",
+ma-skills,anytime,ML Scientist Agent,ma-agent-ml,,skill:ma-agent-ml,ma-agent-ml,false,bmm-demerzel,,"Machine Learning Scientist agent for hypothesis-driven ML lifecycle with scientific rigor.",output_folder,"agent customization",
+ma-skills,anytime,SQA Agent,ma-agent-sqa,,skill:ma-agent-sqa,ma-agent-sqa,false,bmm-qa,,"Software Quality Assurance agent (Gad) for project auditing, compliance verification, and quality reporting.",output_folder,"agent customization",
+ma-skills,4-implementation,Generate SSS,mil498-sss,,skill:mil498-sss,bmad-mil-generate-sss,false,bmm-mil498,,"Generate a MIL-STD-498 System/Subsystem Specification (SSS).",output_folder,"MIL-498 document",
+ma-skills,4-implementation,Generate SSDD,mil498-ssdd,,skill:mil498-ssdd,bmad-mil-generate-ssdd,false,bmm-mil498,,"Generate a MIL-STD-498 System/Subsystem Design Description (SSDD).",output_folder,"MIL-498 document",
+ma-skills,4-implementation,Generate OCD,mil498-ocd,,skill:mil498-ocd,bmad-mil-generate-ocd,false,bmm-mil498,,"Generate a MIL-STD-498 Operational Concept Description (OCD).",output_folder,"MIL-498 document",
+ma-skills,4-implementation,Generate SDP,mil498-sdp,,skill:mil498-sdp,bmad-mil-generate-sdp,false,bmm-mil498,,"Generate a MIL-STD-498 Software Development Plan (SDP).",output_folder,"MIL-498 document",
+ma-skills,4-implementation,Generate SRS,mil498-srs,,skill:mil498-srs,bmad-mil-generate-srs,false,bmm-mil498,,"Generate a MIL-STD-498 Software Requirements Specification (SRS).",output_folder,"MIL-498 document",
+ma-skills,4-implementation,Generate SDD,mil498-sdd,,skill:mil498-sdd,bmad-mil-generate-sdd,false,bmm-mil498,,"Generate a MIL-STD-498 Software Design Description (SDD).",output_folder,"MIL-498 document",
+ma-skills,4-implementation,Generate STD,mil498-std,,skill:mil498-std,bmad-mil-generate-std,false,bmm-mil498,,"Generate a MIL-STD-498 Software Test Description (STD).",output_folder,"MIL-498 document",
+ma-skills,4-implementation,Requirements Quality,mil498-requirement-quality,,skill:mil498-requirement-quality,mil498-requirement-quality,false,bmm-mil498,,"Evaluate requirements against 14 quality criteria — produces per-requirement audit table, Missing Elements report, and Overall Quality Score.",output_folder,"requirements audit",
+ma-skills,4-implementation,Check Deployment Status,sre-check-deployment-status,,skill:sre-check-deployment-status,bmad-sre-check-deployment-status,false,bmm-sre,,"Check deployment status across Kubernetes namespaces and report issues.",output_folder,"status report",
+ma-skills,4-implementation,Check Secrets,sre-check-secrets,,skill:sre-check-secrets,bmad-sre-check-secrets,false,bmm-sre,,"Debug and verify secret configurations in Kubernetes clusters.",output_folder,"status report",
+ma-skills,4-implementation,Check System Status,sre-check-system-status,,skill:sre-check-system-status,bmad-sre-check-system-status,false,bmm-sre,,"Perform overall system status check across cluster resources.",output_folder,"status report",
+ma-skills,4-implementation,Day 2 Ops,sre-day-2-ops,,skill:sre-day-2-ops,bmad-sre-day-2-ops,false,bmm-sre,,"Execute Day 2 operations and maintenance tasks for running systems.",output_folder,"operations report",
+ma-skills,4-implementation,Deployment Strategies,sre-deployment-strategies,,skill:sre-deployment-strategies,bmad-sre-deployment-strategies,false,bmm-sre,,"Evaluate and recommend deployment strategies (blue-green, canary, rolling).",output_folder,"strategy report",
+ma-skills,4-implementation,Fix Deployments,sre-fix-deployments,,skill:sre-fix-deployments,bmad-sre-fix-deployments,false,bmm-sre,,"Troubleshoot and fix failed or degraded deployments.",output_folder,"fix report",
+ma-skills,4-implementation,GitOps Status,sre-gitops-status,,skill:sre-gitops-status,bmad-sre-gitops-status,false,bmm-sre,,"Check GitOps sync status and detect configuration drift.",output_folder,"status report",
+ma-skills,4-implementation,Configure Infrastructure,devops-configure-infrastructure,,skill:devops-configure-infrastructure,bmad-devops-configure-infrastructure,false,bmm-devops,,"Configure infrastructure components using Infrastructure as Code patterns.",output_folder,"infrastructure config",
+ma-skills,4-implementation,Disconnected Deployment,devops-disconnected-deployment,,skill:devops-disconnected-deployment,bmad-devops-disconnected-deployment,false,bmm-devops,,"Deploy to air-gapped or disconnected environments.",output_folder,"deployment guide",
+ma-skills,4-implementation,Docker Compose Setup,devops-docker-compose-setup,,skill:devops-docker-compose-setup,bmad-devops-docker-compose-setup,false,bmm-devops,,"Set up and manage Docker Compose configurations.",output_folder,"compose config",
+ma-skills,4-implementation,Manage Helm,devops-manage-helm,,skill:devops-manage-helm,bmad-devops-manage-helm,false,bmm-devops,,"Deploy and manage Helm charts for Kubernetes.",output_folder,"helm config",
+ma-skills,4-implementation,Sign Docker Image,devops-sign-docker-image,,skill:devops-sign-docker-image,bmad-devops-sign-docker-image,false,bmm-devops,,"Sign Docker images using Cosign/Notary for supply chain security.",output_folder,"signing report",
+ma-skills,4-implementation,Generate Certs,cyber-generate-certs,,skill:cyber-generate-certs,bmad-cyber-generate-certs,false,bmm-cyber,,"Generate secure self-signed certificates and Root CAs using OpenSSL.",output_folder,"certificates",
+ma-skills,4-implementation,Immunity Estimation,cyber-immunity-estimation,,skill:cyber-immunity-estimation,bmad-cyber-immunity-estimation,false,bmm-cyber,,"Estimate cyber immunity posture and resilience metrics.",output_folder,"immunity report",
+ma-skills,4-implementation,Security Audit,cyber-security-audit,,skill:cyber-security-audit,bmad-cyber-security-audit,false,bmm-cyber,,"Perform comprehensive security audit against industry standards.",output_folder,"audit report",
+ma-skills,4-implementation,Vault Secrets,cyber-vault-secrets,,skill:cyber-vault-secrets,bmad-cyber-vault-secrets,false,bmm-cyber,,"Manage HashiCorp Vault secret configurations and policies.",output_folder,"vault config",
+ma-skills,4-implementation,Verify Docker Users,cyber-verify-docker-users,,skill:cyber-verify-docker-users,bmad-cyber-verify-docker-users,false,bmm-cyber,,"Verify Docker image user configurations and hardening compliance.",output_folder,"verification report",
+ma-skills,4-implementation,Verify Image Signature,cyber-verify-image-signature,,skill:cyber-verify-image-signature,bmad-cyber-verify-image-signature,false,bmm-cyber,,"Verify Docker image signatures for supply chain integrity.",output_folder,"verification report",
+ma-skills,4-implementation,Vulnerability Scan,cyber-vulnerability-scan,,skill:cyber-vulnerability-scan,bmad-cyber-vulnerability-scan,false,bmm-cyber,,"Orchestrate vulnerability scanning across project components.",output_folder,"scan report",
+ma-skills,4-implementation,ML Ideation,ml-ideation,,skill:ml-ideation,ml-ideation,false,bmm-demerzel,,"Frame an ML research problem, produce a Research Thesis and PRD.",_bmad-output,"research thesis",
+ma-skills,4-implementation,ML EDA,ml-eda,,skill:ml-eda,ml-eda,false,bmm-demerzel,,"Exploratory Data Analysis — establish baselines and produce an EDA report.",_bmad-output,"EDA report",
+ma-skills,4-implementation,ML Architecture,ml-architecture,,skill:ml-architecture,ml-architecture,false,bmm-demerzel,,"Define model architecture, stack, and experiment tracking strategy.",_bmad-output,"architecture spec",
+ma-skills,4-implementation,ML Detailed Design,ml-detailed-design,,skill:ml-detailed-design,ml-detailed-design,false,bmm-demerzel,,"Break implementation into INF-* and EXP-* tasks.",_bmad-output,"task breakdown",
+ma-skills,4-implementation,ML TechSpec,ml-techspec,,skill:ml-techspec,ml-techspec,false,bmm-demerzel,,"Lock experiment parameters and performance tiers before training.",_bmad-output,"TechSpec",
+ma-skills,4-implementation,ML Infra,ml-infra,,skill:ml-infra,ml-infra,false,bmm-demerzel,,"Build ML infrastructure, manage dependencies, and run smoke tests.",_bmad-output,"infra report",
+ma-skills,4-implementation,ML Experiment,ml-experiment,,skill:ml-experiment,ml-experiment,false,bmm-demerzel,,"Execute training experiments against locked TechSpec and log metrics.",_bmad-output,"experiment log",
+ma-skills,4-implementation,ML Analysis,ml-analysis,,skill:ml-analysis,ml-analysis,false,bmm-demerzel,,"Evaluate experiment outcomes against TechSpec success tiers.",_bmad-output,"analysis report",
+ma-skills,4-implementation,ML Hyperparameter Optimization,ml-hparam,,skill:ml-hparam,ml-hparam,false,bmm-demerzel,,"Automated hyperparameter optimization (Optuna, W&B Sweeps, Ray Tune).",_bmad-output,"hparam report",
+ma-skills,4-implementation,ML Revision,ml-revision,,skill:ml-revision,ml-revision,false,bmm-demerzel,,"Amend hypothesis and requirements based on experiment findings.",_bmad-output,"revision doc",
+ma-skills,4-implementation,ML Advise,ml-advise,,skill:ml-advise,ml-advise,false,bmm-demerzel,,"Search past experiments, surface findings and failure warnings.",_bmad-output,"advisory report",
+ma-skills,4-implementation,ML Retrospective,ml-retrospective,,skill:ml-retrospective,ml-retrospective,false,bmm-demerzel,,"Capture session learnings and update project context.",_bmad-output,"retrospective",
+ma-skills,4-implementation,SQA Audit,sqa-audit,,skill:sqa-audit,sqa-audit,false,bmm-qa,,"Comprehensive project quality audit covering code-to-story traceability, story-to-architecture alignment, process compliance, sprint health, and release state.",_bmad-output,"audit report",
+ma-skills,4-implementation,IEEE 12207 Compliance,sqa-ieee12207,,skill:sqa-ieee12207,sqa-ieee12207,false,bmm-qa,,"Evaluate the project against IEEE/ISO/IEC 12207:2017 software lifecycle processes — produces a compliance matrix and gap analysis report.",_bmad-output,"compliance report",
+ma-skills,4-implementation,Create Bug Story,create-bug-story,,skill:create-bug-story,create-bug-story,false,bmm-dev,,"Create a structured bug story from a detected defect and add to backlog.",_bmad-output/implementation-artifacts,"bug story",
+ma-skills,4-implementation,Dev Story,bmad-dev-story,,skill:bmad-dev-story,bmad-dev-story,false,bmm-dev,,"Execute story implementation following a context filled story spec file.",_bmad-output/implementation-artifacts,"story implementation",
+ma-skills,4-implementation,Sprint Planning,bmad-sprint-planning,,skill:bmad-sprint-planning,bmad-sprint-planning,false,bmm-sm,,"Bootstrap or update the unified sprint-status.yaml from epics with three sections (epics, backlog, sprints).",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Generate Backlog,generate-backlog,,skill:generate-backlog,generate-backlog,false,bmm-sm,,"Generate or refresh the backlog section of sprint-status.yaml from epics and bug stories.",_bmad-output/implementation-artifacts,"backlog",
+ma-skills,4-implementation,Add Sprint,add-sprint,,skill:add-sprint,add-sprint,false,bmm-sm,,"Create a new sprint entry in the sprints section of sprint-status.yaml with capacity limits, optional ISO dates, and auto-incremented ID.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Add to Sprint,add-to-sprint,,skill:add-to-sprint,add-to-sprint,false,bmm-sm,,"Move backlog items to a sprint in the unified sprint-status.yaml using movement semantics.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Remove from Sprint,remove-from-sprint,,skill:remove-from-sprint,remove-from-sprint,false,bmm-sm,,"Move items from a sprint back to the backlog in the unified sprint-status.yaml using reverse movement semantics.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Modify Sprint,modify-sprint,,skill:modify-sprint,modify-sprint,false,bmm-sm,,"Modify an existing sprint's metadata (name, capacity, dates, status) within the sprints section of sprint-status.yaml.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Sprint Status View,sprint-status-view,,skill:sprint-status-view,sprint-status-view,false,bmm-sm,,"Display formatted sprint progress, backlog, and epic status from the unified sprint-status.yaml.",_bmad-output/implementation-artifacts,"status display",
+ma-skills,4-implementation,Sprint Status Health,bmad-sprint-status,,skill:bmad-sprint-status,bmad-sprint-status,false,bmm-sm,,"Analyze sprint health, surface risk flags, and recommend next actions from the unified sprint-status.yaml.",_bmad-output/implementation-artifacts,"health summary",
+ma-skills,4-implementation,Cleanup Done,cleanup-done,,skill:cleanup-done,cleanup-done,false,bmm-sm,,"Archive done and cancelled items — remove from sprint-status.yaml and move files to done/ subfolder.",_bmad-output/implementation-artifacts,"archival",
+ma-skills,4-implementation,Close Sprint,close-sprint,,skill:close-sprint,close-sprint,false,bmm-sm,,"Close an active sprint — archive done/cancelled items, disposition incomplete items, set sprint status to closed.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Prioritize Backlog,prioritize-backlog,,skill:prioritize-backlog,prioritize-backlog,false,bmm-sm,,"Reprioritize backlog items using multiple criteria -- severity, business value, dependencies, type, age.",_bmad-output/implementation-artifacts,"backlog",
+ma-skills,4-implementation,Project Context Expansion,project-context-expansion,,skill:project-context-expansion,project-context-expansion,false,bmm-sm,,"Post-retrospective companion to update project-context.md with new rules.",_bmad-output,"project context",
+ma-skills,4-implementation,Requirements Quality Audit,sqa-requirements-quality,,skill:sqa-requirements-quality,sqa-requirements-quality,false,bmm-qa,,"Evaluate project requirements against 14 quality criteria — produces a per-requirement audit table, missing-elements section, and overall quality score.",_bmad-output,"quality report",

package/lib/bmad-extension-plugin/skills/module.yaml

@@ -0,0 +1,20 @@
+# ma-skills module manifest (BMAD v6.5.0 schema)
+#
+# Canonical location: `skills/module.yaml` (BMAD 6.2.2+ / 6.3.0). The previous
+# location `lib/bmad-extension/module.yaml` was moved here during Story 22.5.
+# PluginResolver (tools/installer/modules/plugin-resolver.js) discovers this
+# file as the "common parent of all skills" under Strategy 1.
+#
+# module_version policy (Story 22.5 / AC 7):
+#   - Patch: bug fixes within existing skills
+#   - Minor: skill added, additive change
+#   - Major: skill removed, renamed, or breaking change to skill behavior
+# Bump this whenever marketplace.json.template's skills[] list or any
+# bmad-skill-manifest.yaml is modified.
+
+code: ma-skills
+name: "MA-Agents Skills & Agents"
+description: "Enterprise methodology enforcement, specialized agents, and operational workflows"
+module_version: "3.6.2"
+extends-module: bmm
+default_selected: false