ma-agents 3.6.2 → 3.9.0

package/lib/bmad-extension-plugin/skills/sqa-requirements-quality/SKILL.md

@@ -0,0 +1,244 @@
+---
+name: sqa-requirements-quality
+description: Requirements Quality Audit workflow — evaluates requirements in selected project documents against 14 quality criteria, producing a per-requirement audit table, missing-elements section, and overall quality score
+type: skill
+triggers:
+  - "requirements quality"
+  - "audit requirements"
+  - "req quality"
+  - "requirements audit"
+---
+
+# Requirements Quality Audit Workflow
+
+## Purpose
+
+Evaluate requirements in selected project documents against **14 established quality criteria** (Clarity, Single Verb, Sentence Structure, Glossary Presence, Necessity, Implementation-Independence, Unambiguity, Completeness, Feasibility, Testability, Stakeholder Alignment, Convention Conformance, Understandability, Precision). Produce a structured per-requirement audit report and offer corrective-action support for failing requirements.
+
+---
+
+## Quality Criteria Reference
+
+| # | Criterion | Definition |
+|---|-----------|------------|
+| 1 | **Clarity & Directness** | No source-form verbs (e.g., "to save", "to keep"). States the required behavior, not a capability. |
+| 2 | **Single Primary Verb** | Each requirement contains exactly one main action verb; any conditions are separated by commas or placed on a new line. |
+| 3 | **Sentence Structure** | Follows the pattern: `Condition + Subject + Predicate + Object [+ Constraint]`. |
+| 4 | **Glossary Presence** | All domain-specific terms used in the requirement are defined in a dedicated glossary. |
+| 5 | **Necessity** | The requirement appears only once in the document and does not duplicate another. If conceptually identical to another, identify which requirement it duplicates. |
+| 6 | **Implementation-Independent** | Describes the need, not a specific solution or technology. |
+| 7 | **Unambiguous** | Has only one possible interpretation for all relevant stakeholders. |
+| 8 | **Completeness** | Self-contained; does not rely on other requirements for its meaning. |
+| 9 | **Feasibility** | Realistic and achievable within reasonable cost, schedule, and technology limits. |
+| 10 | **Testability** | Can be verified by a concrete test or inspection. |
+| 11 | **Stakeholder Alignment** | Accurately reflects the expressed needs of the identified stakeholders. |
+| 12 | **Conformance to Conventions** | Uses the project's standard format (e.g., Epic → User Stories → Acceptance Criteria) and consistent look-and-feel. |
+| 13 | **Understandability** | Written in plain language that the supplier can readily comprehend. |
+| 14 | **Precision** | Uses definite nouns, explicit units, and avoids vague qualifiers (e.g., "approximately", "usually", "high"). |
+
+---
+
+## Step 1 — Scope Selection
+
+Ask the user:
+
+> "Welcome to the Requirements Quality Audit. Which documents should I audit?
+>
+> **Available sources:**
+> 1. **PRD — Functional Requirements (FR)**: All FR-prefixed requirements in `prd.md`
+> 2. **PRD — Non-Functional Requirements (NFR)**: All NFR-prefixed requirements in `prd.md`
+> 3. **Epics & User Stories**: Epic goals and story acceptance criteria in `epics.md`
+> 4. **All of the above**
+>
+> Type **'all'** or list the numbers you want (e.g., '1,2')."
+
+Wait for user selection. Store as {rq_scope}.
+
+---
+
+## Step 2 — Data Collection
+
+Load the selected documents. Note presence or absence — missing documents result in that scope item being SKIPPED.
+
+| Source | Path |
+|--------|------|
+| PRD | `{output_folder}/planning-artifacts/prd.md` |
+| Epics & Stories | `{output_folder}/planning-artifacts/epics.md` |
+
+Inform the user which documents were found and which were missing before proceeding.
+
+---
+
+## Step 3 — Extract Requirements
+
+**Scope guard:** Only extract from documents selected in {rq_scope}.
+
+For each selected source, identify and list all requirements to be evaluated:
+
+- **PRD FRs**: All items prefixed `FR` in the Functional Requirements section
+- **PRD NFRs**: All items prefixed `NFR` in the Non-Functional Requirements section
+- **Epics**: Epic goal statements (the "Goal:" or intent sentence of each epic)
+- **User Stories**: The "As a / I want / so that" statement plus all Acceptance Criteria items
+
+If the total requirement count exceeds 30, ask the user:
+> "I found {N} requirements. Would you like me to audit all of them, or focus on a specific section? (Type 'all' or describe which section to prioritize)"
+
+---
+
+## Step 4 — Evaluate Requirements
+
+For each requirement, evaluate all 14 criteria. Produce a table per requirement:
+
+| Requirement ID | Requirement Summary | Type | Criterion | Pass/Fail | Comments / Suggested Revision |
+|----------------|-------------------|------|-----------|-----------|-------------------------------|
+| [ID] | [one-line summary] | [type] | 1 — Clarity & Directness | ✅ / ❌ | [comment or suggested revision if failed] |
+| | | | 2 — Single Primary Verb | ✅ / ❌ | |
+| | | | 3 — Sentence Structure | ✅ / ❌ | |
+| | | | 4 — Glossary Presence | ✅ / ❌ | |
+| | | | 5 — Necessity | ✅ / ❌ | |
+| | | | 6 — Implementation-Independent | ✅ / ❌ | |
+| | | | 7 — Unambiguous | ✅ / ❌ | |
+| | | | 8 — Completeness | ✅ / ❌ | |
+| | | | 9 — Feasibility | ✅ / ❌ | |
+| | | | 10 — Testability | ✅ / ❌ | |
+| | | | 11 — Stakeholder Alignment | ✅ / ❌ | |
+| | | | 12 — Convention Conformance | ✅ / ❌ | |
+| | | | 13 — Understandability | ✅ / ❌ | |
+| | | | 14 — Precision | ✅ / ❌ | |
+
+**Requirement Type codes:** `FR` `NFR` `US` (User Story) `AC` (Acceptance Criterion) `EPIC`
+
+**Rules:**
+- For every ❌, provide a specific, actionable suggested revision in the Comments column
+- For Criterion 5 (Necessity), if a duplicate is found, name the duplicating requirement by ID
+- A requirement FAILS overall if it fails 3 or more criteria (mark the ID row with ⚠️)
+- A requirement CRITICALLY FAILS if it fails criteria 7 (Unambiguous), 10 (Testability), or 14 (Precision) (mark the ID row with ❌)
+
+---
+
+## Step 5 — Missing Elements
+
+After all requirement tables, produce a **Missing Elements** section:
+
+```
+### Missing Elements
+
+- Glossary: [domain-specific terms used across requirements that lack a definition]
+- Acceptance Criteria: [User Stories with no AC]
+- Traceability: [requirements not linked to a parent epic, stakeholder need, or PRD section]
+- Testability gaps: [requirements where no concrete verification method is apparent]
+- Other: [any absent artifacts or structural issues]
+```
+
+If nothing is missing, state: *No missing elements identified.*
+
+---
+
+## Step 6 — Overall Quality Score
+
+```
+### Overall Quality Score
+
+{X} / {Y} criteria passed across {Z} requirements ({P}%)
+
+**By severity:**
+- Critical failures (failing criterion 7, 10, or 14): {N} requirements
+- Overall failures (≥3 criteria failing): {N} requirements
+- Minor issues (1-2 criteria failing): {N} requirements
+- Fully passing: {N} requirements
+```
+
+---
+
+## Step 7 — Compile and Save Report
+
+Compile the full report in this structure:
+
+```
+# Requirements Quality Audit Report
+**Date:** {today's date}
+**Auditor:** Gad (SQA Agent)
+**Scope:** {selected document sources}
+**Requirements Audited:** {total count}
+**Overall Quality Score:** {X}/{Y} ({P}%)
+
+---
+
+## Executive Summary
+{3-4 sentences: overall quality posture, most common failure patterns, primary recommendations}
+
+---
+
+## Per-Requirement Audit
+
+{requirement tables from Step 4}
+
+---
+
+## Missing Elements
+
+{section from Step 5}
+
+---
+
+## Overall Quality Score
+
+{section from Step 6}
+
+---
+
+## Top Recommendations
+
+{Ordered list of the most impactful improvements — focus on patterns, not individual requirements}
+
+| Priority | Pattern | Affected Requirements | Recommended Fix |
+|----------|---------|-----------------------|-----------------|
+| P1       | ...     | FR12, FR18, FR24      | ...             |
+```
+
+Save the report to:
+`{output_folder}/sqa-requirements-quality-report-{YYYY-MM-DD}.md`
+
+Inform the user of the saved path.
+
+---
+
+## Step 8 — Corrective Action Offers
+
+Ask:
+> "Would you like me to generate a remediation plan with suggested revisions for all failing requirements?"
+
+If yes, save a remediation plan to:
+`{output_folder}/sqa-remediation-plan-requirements-{YYYY-MM-DD}.md`
+
+### Remediation Plan Format
+
+```
+# Requirements Quality Remediation Plan
+**Date:** {today's date}
+**Auditor:** Gad (SQA Agent)
+**Source Report:** sqa-requirements-quality-report-{YYYY-MM-DD}.md
+
+---
+
+## Summary
+{count of critical failures, overall failures, minor issues}
+
+---
+
+## Corrective Actions
+
+| Priority | Req ID | Type | Failed Criteria | Issue | Suggested Revision | Effort |
+|----------|--------|------|----------------|-------|-------------------|--------|
+| P1       | FR12   | FR   | 7, 10          | ...   | ...               | Low    |
+
+---
+
+## Pattern-Level Fixes
+{If multiple requirements share the same failure pattern, describe a single structural fix that would resolve the pattern across all affected requirements}
+```
+
+Then, for each critically failing requirement (criterion 7, 10, or 14 failing), offer one at a time:
+> "Would you like me to create a backlog story to rewrite requirement [ID]? (yes/skip)"
+
+If yes, invoke `create-bug-story` for that item.

package/lib/bmad-extension-plugin/skills/sqa-requirements-quality/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: sqa-requirements-quality
+module: ma-skills

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

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

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

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