ma-agents 3.4.7 → 3.4.9

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

package/.opencode/skills/sre-check-deployment-status/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: sre-check-deployment-status
+description: Check deployment status across environments
+type: skill
+triggers:
+  - "check deployment status"
+  - "deployment status"
+---
+
+# workflow-check-deployment-status.md
+# Deployment Status Check Workflow
+
+This workflow guides the agent through checking the status of a specific deployment in a Kubernetes cluster.
+
+## Parameters
+- `{namespace}`: The namespace of the deployment (default: `default`)
+- `{deployment_name}`: The name of the deployment to check
+
+## Instructions
+1.  **Identify Resource**: Determine the `{deployment_name}` and `{namespace}` from user input or context.
+2.  **Run Diagnostics**:
+    -   `kubectl get deployment {deployment_name} -n {namespace}`
+    -   `kubectl describe deployment {deployment_name} -n {namespace}`
+3.  **Check Pods**:
+    -   `kubectl get pods -l app={deployment_name} -n {namespace}`
+    -   Identify any pods that are NOT in `Running` state.
+4.  **Analyze Events**:
+    -   Look at the `Events` section of the `describe` output for error messages (e.g., `ImagePullBackOff`, `CrashLoopBackOff`).
+5.  **Report**:
+    -   Summarize the current status.
+    -   Highlight any issues found.
+    -   Suggest next steps (e.g., "Check logs", "Check resource limits").

package/.opencode/skills/sre-check-deployment-status/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: sre-check-deployment-status
+module: ma-skills

package/.opencode/skills/sre-check-secrets/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: sre-check-secrets
+description: Debug and resolve Kubernetes secret issues
+type: skill
+triggers:
+  - "check secrets"
+  - "debug secrets"
+---
+
+# workflow-check-secrets.md
+# Secret Debugging Workflow
+
+This workflow helps identify and resolve problems related to Kubernetes Secrets.
+
+## Instructions
+1.  **Check Visibility**: `kubectl get secret -n {namespace}`
+2.  **Verify Mounting**:
+    -   Check if the deployment actually mounts the secret.
+    -   `kubectl get deployment {deployment_name} -o yaml | grep secret`
+3.  **Check Permissions**: Verify ServiceAccount has permissions to read the secret (RBAC).
+4.  **Content Verification**: (Safety first!) Offer to check if keys exist WITHOUT displaying sensitive values unless explicitly requested.
+    -   `kubectl get secret {name} -n {namespace} -o jsonpath='{.data}'`
+5.  **Common Errors**: Look for "Secret not found" or "Authorization" errors in pod events.

package/.opencode/skills/sre-check-secrets/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: sre-check-secrets
+module: ma-skills

package/.opencode/skills/sre-check-system-status/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: sre-check-system-status
+description: Overall system health check across container runtimes
+type: skill
+triggers:
+  - "check system status"
+  - "system status"
+---
+
+# workflow-check-system-status.md
+# Overall System Status Workflow
+
+This workflow provides a high-level overview of the health of the container runtime and orchestration environment.
+
+## Instructions
+1.  **Detect Runtime**: Check if reachable:
+    -   `kubectl cluster-info` (Kubernetes)
+    -   `docker info` (Docker)
+    -   `podman info` (Podman)
+2.  **Resource Overview**:
+    -   **K8s**: `kubectl get nodes`, `kubectl get pods -A | grep -v Running`
+    -   **Docker**: `docker ps`, `docker stats --no-stream`
+    -   **Podman**: `podman ps`, `podman stats --no-stream`
+3.  **Cross-Platform Diagnostics**:
+    -   Check for resource exhaustion (High CPU/Memory).
+    -   Verify network connectivity between key services.
+4.  **Summary Table**: Present a status table of all detected environments.

package/.opencode/skills/sre-check-system-status/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: sre-check-system-status
+module: ma-skills

package/.opencode/skills/sre-day-2-ops/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: sre-day-2-ops
+description: Day 2 operations and maintenance for long-term cluster stability
+type: skill
+triggers:
+  - "day 2 ops"
+  - "day 2 operations"
+  - "maintenance"
+---
+
+# workflow-day-2-ops.md
+# Day 2 Operations & Maintenance Workflow
+
+Focuses on long-term stability, cluster-to-config verification, and periodic maintenance.
+
+## Instructions
+1.  **Config Verification**:
+    - Check current cluster status against the master configuration templates.
+    - Verify consistency of secrets, configmaps, and resource limits.
+2.  **Resource Optimization**:
+    - Review `top nodes` and `top pods`.
+    - Identify over-provisioned or under-utilized resources.
+3.  **Maintenance Tasks**:
+    - Node drain/uncordon (safe handling).
+    - Certificate rotation check.
+4.  **Automation**: Propose cronjobs for periodic backups or diagnostic reports.

package/.opencode/skills/sre-day-2-ops/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: sre-day-2-ops
+module: ma-skills

package/.opencode/skills/sre-deployment-strategies/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: sre-deployment-strategies
+description: Guide advanced deployment strategies including Blue-Green, Canary, and Rolling Updates
+type: skill
+triggers:
+  - "deployment strategies"
+  - "canary deployment"
+  - "blue green deployment"
+---
+
+# workflow-deployment-strategies.md
+# Deployment Strategies Workflow
+
+Guides on implementing and monitoring advanced deployment techniques like Blue-Green, Canary, and Rolling Updates.
+
+## Instructions
+1.  **Select Strategy**:
+    -   **Rolling Update**: Standard Kubernetes strategy.
+    -   **Canary**: Gradual traffic shift (requires Service Mesh or specialized CRDs like Argo Rollouts).
+    -   **Blue-Green**: Instant switch between versions.
+2.  **Strategy Status**:
+    -   `kubectl get rollouts` (Argo Rollouts)
+    -   Monitor success metrics (HTTP 2xx vs 5xx) during transition.
+3.  **Health Verification**: 
+    - Verify healthy startup before increasing traffic.
+    - Automatically propose rollbacks if SLOs are breached.
+4.  **Execution**:
+    - Trigger rollout update or promotion.

package/.opencode/skills/sre-deployment-strategies/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: sre-deployment-strategies
+module: ma-skills

package/.opencode/skills/sre-fix-deployments/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: sre-fix-deployments
+description: Automated troubleshooting and fixes for common deployment issues
+type: skill
+triggers:
+  - "fix deployments"
+  - "troubleshoot deployment"
+---
+
+# workflow-fix-deployments.md
+# Deployment Fix Workflow
+
+This workflow provides automated troubleshooting steps to resolve common deployment issues.
+
+## Instructions
+1.  **Detect Issue**: Based on `check-deployment-status` output, identify the root cause.
+2.  **Image issues**: If `ImagePullBackOff`, verify image name and registry secrets.
+3.  **CrashLoopBackOff**:
+    -   `kubectl logs {deployment_name} -n {namespace} --previous`
+    -   Check for missing env vars or config maps.
+4.  **Pending State**:
+    -   Check node resources: `kubectl describe node`
+    -   Verify PersistentVolumeClaims (PVCs).
+5.  **Scaling**: If resource-related, suggest scaling or adjusting `resources.requests/limits`.
+6.  **Action**: Offer to apply a fix (e.g., `kubectl apply -f ...` or `kubectl set image ...`).

package/.opencode/skills/sre-fix-deployments/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: sre-fix-deployments
+module: ma-skills

package/.opencode/skills/sre-gitops-status/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: sre-gitops-status
+description: Monitor GitOps synchronization state and detect drift using ArgoCD or Flux
+type: skill
+triggers:
+  - "gitops status"
+  - "drift detection"
+---
+
+# workflow-gitops-status.md
+# GitOps Status & Drift Detection Workflow
+
+This workflow monitors and reports the synchronization state between your git repository and the cluster using ArgoCD or Flux.
+
+## Instructions
+1.  **Identify Tool**: Detect if ArgoCD or Flux is in use.
+2.  **Sync Status**:
+    -   **ArgoCD**: `argocd app list`, `argocd app get {app_name}`
+    -   **Flux**: `flux get kustomizations`, `flux get helmreleases`
+3.  **Drift Detection**:
+    -   Identify "OutOfSync" resources.
+    -   Compare live state with desired state in git.
+4.  **Action**:
+    -   Offer to trigger a sync: `argocd app sync {app_name}` or `flux reconcile kustomization {name}`.
+    -   Analyze reasons for permanent drift (e.g., manual cluster changes).

package/.opencode/skills/sre-gitops-status/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: sre-gitops-status
+module: ma-skills