ma-agents 2.22.1 → 3.0.0

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

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

package/lib/bmad-extension/skills/sprint-status-view/SKILL.md

@@ -0,0 +1,202 @@
+---
+name: sprint-status-view
+description: Display sprint progress with assigned items, type distinction, and remaining capacity
+type: skill
+triggers:
+  - "sprint status view"
+  - "view sprint status"
+---
+
+# Sprint Status View Workflow
+
+Extension workflow that displays sprint progress with assigned items (stories + bugs), type distinction, and remaining capacity.
+
+> **Architecture mandate:** This workflow is a NEW extension at `lib/bmad-extension/workflows/sprint-status-view/`. It does NOT modify any files under `_bmad/bmm/workflows/`.
+
+<workflow>
+
+<step n="1" goal="Discover all sprint artifact files">
+  <action>Glob `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` to discover all sprint artifact files</action>
+  <check if="no sprint files found">
+    <output>
+ℹ️ **No Sprints Found**
+
+No sprint plan files exist yet (`sprint-plan-*.yaml`).
+
+**To get started:**
+- Run `/add-sprint` to create your first sprint
+- Run `/add-to-sprint` to assign backlog items to it
+    </output>
+    <action>Exit workflow</action>
+  </check>
+  <action>For each sprint file found, read the full YAML content and store as {{sprint_plans}} list</action>
+  <action>Sort {{sprint_plans}} by sprint_number ascending</action>
+</step>
+
+<step n="2" goal="Load sprint-status.yaml for user story execution statuses">
+  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
+  <check if="file not found">
+    <output>⚠️ `sprint-status.yaml` not found. User story execution statuses will not be available. Run `/sprint-planning` to initialize.</output>
+    <action>Set {{story_status_map}} = {} (empty — will show data integrity warnings per missing item)</action>
+  </check>
+  <check if="file found">
+    <action>Parse development_status section into {{story_status_map}} — key: story key, value: status</action>
+    <action>Exclude epic-* keys and *-retrospective keys from the map</action>
+  </check>
+</step>
+
+<step n="3" goal="Discover bug stories for type/severity data">
+  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` to discover all bug story files</action>
+  <check if="no bug files found">
+    <action>Set {{bug_metadata_map}} = {} (empty)</action>
+  </check>
+  <check if="bug files found">
+    <action>For each bug file, parse YAML frontmatter to extract: type, severity, title</action>
+    <action>Build {{bug_metadata_map}} — key: file basename (e.g., `bug-login-crash`), value: {severity, title}</action>
+  </check>
+</step>
+
+<step n="4" goal="Display sprint status for each sprint">
+  <action>For each sprint in {{sprint_plans}} (in order):</action>
+  <action>Calculate: {{assigned_count}} = length(sprint.assigned_items)</action>
+  <action>Calculate: {{remaining_capacity}} = sprint.capacity - {{assigned_count}}</action>
+
+  <action>For each item identifier in sprint.assigned_items, resolve item details:
+
+    **If item is a story (key matches regex `^\d+-\d+-.+`):**
+    - Look up status in {{story_status_map}}[item_key]
+    - If NOT found in {{story_status_map}}:
+      → Record as DATA INTEGRITY WARNING: "Item {item_key} has no status entry in sprint-status.yaml — run /sprint-planning to initialize status tracking for this item."
+      → Display item with marker: ⚠️ [status unknown]
+    - If found: display with current status label
+
+    **If item is a bug (key matches regex `^bug-.+`):**
+    - Look up in {{bug_metadata_map}}[item_key]
+    - If NOT found: display with title as item_key, severity as "unknown"
+    - If found: display with title and severity from frontmatter
+    - Bug execution status: use `status` from bug file frontmatter if present; otherwise "not-started"
+
+    **If item matches neither pattern:** display as type "Unknown" with raw identifier as title
+  </action>
+
+  <output>
+---
+
+## 🏃 {{sprint.sprint_name}} (Sprint {{sprint.sprint_number}})
+
+**Status:** {{sprint.status}} | **Capacity:** {{sprint.capacity}} items | **Assigned:** {{assigned_count}} | **Remaining:** {{remaining_capacity}}
+{{#if sprint.start_context}}**Start:** {{sprint.start_context}}{{/if}} {{#if sprint.end_context}}| **End:** {{sprint.end_context}}{{/if}}
+
+{{#if over_capacity}}
+⚠️ **Over capacity by {{overage}} item(s)**
+{{/if}}
+
+### Assigned Items
+
+| Item | Title | Type | Status / Severity |
+|---|---|---|---|
+{{#each resolved_items}}
+{{#if is_story}}
+| {{item_key}} | {{title}} | 📋 Story | {{status}} |
+{{/if}}
+{{#if is_bug}}
+| {{item_key}} | {{title}} | 🐛 Bug | Severity: {{severity}} / {{bug_status}} |
+{{/if}}
+{{/each}}
+
+{{#if data_integrity_warnings}}
+**⚠️ Data Integrity Warnings:**
+{{#each data_integrity_warnings}}
+- {{this}}
+{{/each}}
+{{/if}}
+
+{{#if assigned_items_empty}}
+*(No items assigned to this sprint)*
+{{/if}}
+  </output>
+</step>
+
+<step n="5" goal="Display unassigned backlog summary">
+  <action>Collect all item keys from {{story_status_map}} that are NOT in any sprint's assigned_items list — these are unassigned user stories</action>
+  <action>Collect all bug basenames from {{bug_metadata_map}} that are NOT in any sprint's assigned_items list — these are unassigned bugs</action>
+  <action>Count unassigned stories by status: {{unassigned_by_status}}</action>
+  <output>
+---
+
+## 📦 Unassigned Backlog
+
+### 📋 Unassigned Stories
+
+| Status | Count |
+|---|---|
+| backlog | {{count_backlog}} |
+| ready-for-dev | {{count_ready}} |
+| in-progress | {{count_in_progress}} |
+| review | {{count_review}} |
+| done | {{count_done}} |
+
+*Total unassigned stories: {{total_unassigned}}*
+
+### 🐛 Unassigned Bugs
+
+{{#if unassigned_bugs}}
+| ID / File | Title | Severity |
+|---|---|---|
+{{#each unassigned_bugs}}
+| {{id}} | {{title}} | {{severity}} |
+{{/each}}
+{{else}}
+*(No unassigned bugs)*
+{{/if}}
+
+**Tip:** Use `/add-to-sprint` to assign unassigned items to a sprint.
+  </output>
+</step>
+
+<step n="6" goal="Offer next actions">
+  <ask>Options:
+1. Show full unassigned backlog item list (IDs + titles + statuses)
+2. Add items to a sprint — run `/add-to-sprint`
+3. Modify a sprint — run `/modify-sprint`
+4. Create a new sprint — run `/add-sprint`
+5. Exit
+
+Choice:</ask>
+  <check if="choice == 1">
+    <action>For each unassigned story key in {{story_status_map}} not assigned to any sprint, display: key, inferred title, status</action>
+    <action>For each unassigned bug in {{bug_metadata_map}} not assigned to any sprint, display: id, title, severity</action>
+    <output>
+### Full Unassigned Backlog
+
+**Stories:**
+| Key | Title | Status |
+|---|---|---|
+{{#each unassigned_story_items}}
+| {{key}} | {{title}} | {{status}} |
+{{/each}}
+
+**Bugs:**
+| ID | Title | Severity |
+|---|---|---|
+{{#each unassigned_bugs}}
+| {{id}} | {{title}} | {{severity}} |
+{{/each}}
+    </output>
+    <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 `/modify-sprint` to add/remove items or change sprint settings.</output>
+  </check>
+  <check if="choice == 4">
+    <output>▶️ Run `/add-sprint` to create a new sprint.</output>
+  </check>
+  <check if="choice == 5">
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+</workflow>

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

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

package/lib/bmad-extension/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/lib/bmad-extension/skills/sre-check-deployment-status/bmad-skill-manifest.yaml

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

package/lib/bmad-extension/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/lib/bmad-extension/skills/sre-check-secrets/bmad-skill-manifest.yaml

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

package/lib/bmad-extension/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/lib/bmad-extension/skills/sre-check-system-status/bmad-skill-manifest.yaml

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

package/lib/bmad-extension/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/lib/bmad-extension/skills/sre-day-2-ops/bmad-skill-manifest.yaml

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

package/lib/bmad-extension/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/lib/bmad-extension/skills/sre-deployment-strategies/bmad-skill-manifest.yaml

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

package/lib/bmad-extension/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/lib/bmad-extension/skills/sre-fix-deployments/bmad-skill-manifest.yaml

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