ma-agents 2.13.3 → 2.14.0

package/lib/bmad-workflows/mil498/bmad-mil-generate-ocd.md

@@ -14,4 +14,4 @@ This workflow generates a MIL-STD-498 OCD document to describe the system from a
     - **Section 4 (Nature of proposed changes)**: Overview of the solution.
     - **Section 5 (Operational concept)**: Describe user roles, operational scenarios, and key workflows (from UX/Stories).
 4.  **Clarity**: Ensure the document is written in a way that is easily understood by system users and stakeholders.
-5.  **Output**: Save the generated document to the `{output_folder}` as `OCD.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `OCD.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-sdd.md

@@ -15,4 +15,4 @@ This workflow generates a MIL-STD-498 SDD document (using the SSDD template) bas
     - **Section 4 (CSCI architectural design)**: Define components, their interfaces, and data flow.
     - **Section 5 (CSCI detailed design)**: Map Stories to detailed logic and internal data structures.
 4.  **Consistency**: Ensure the design matches the requirements specified in the SRS.
-5.  **Output**: Save the generated document to the `{output_folder}` as `SDD.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SDD.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-sdp.md

@@ -14,4 +14,4 @@ This workflow generates a MIL-STD-498 SDP document to outline the development ap
     - **Section 4 (Software development process)**: Describe the BMAD-METHOD lifecycle used.
     - **Section 5 (Software development activities)**: Detail the tasks, schedules, and milestones.
 4.  **Consistency**: Ensure the plan reflects the actual development methodology being followed.
-5.  **Output**: Save the generated document to the `{output_folder}` as `SDP.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SDP.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-srs.md

@@ -16,4 +16,4 @@ This workflow generates a MIL-STD-498 SRS document by extracting requirements fr
     - **Section 3.3 (External Interface Requirements)**: Map Architecture interface definitions here.
     - **Section 3.10 (Computer Resource Requirements)**: Extract hardware/software constraints from the Architecture document.
 4.  **Traceability**: Ensure each requirement has a unique CID and is traced to the original PRD entry.
-5.  **Output**: Save the generated document to the `{output_folder}` as `SRS.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SRS.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-sss.md

@@ -13,4 +13,4 @@ This workflow generates a MIL-STD-498 SSS document for high-level system require
     - **Section 3.3 (System external interface requirements)**: Map top-level interfaces.
     - **Section 3.4 (System internal interface requirements)**: Map interfaces between major subsystems.
 4.  **High-Level Focus**: Keep requirements at the system/subsystem level, avoiding low-level software details.
-5.  **Output**: Save the generated document to the `{output_folder}` as `SSS.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SSS.md`.

package/lib/bmad-workflows/mil498/bmad-mil-generate-std.md

@@ -14,4 +14,4 @@ This workflow generates a MIL-STD-498 STD document to define the test cases and
     - **Section 4 (Test descriptions)**: Map Story acceptance criteria to specific test cases and procedures.
     - **Section 5 (Requirements traceability)**: Link each test case to one or more SRS requirements.
 4.  **Verification**: Ensure all requirements in the SRS have at least one test case.
-5.  **Output**: Save the generated document to the `{output_folder}` as `STD.md`.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `STD.md`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ma-agents",
-  "version": "2.13.3",
+  "version": "2.14.0",
   "description": "NPX tool to install skills for AI coding agents (Claude Code, Gemini, Copilot, Kilocode, Cline, Cursor)",
   "main": "index.js",
   "bin": {

package/skills/bmad-cyber-generate-certs/SKILL.md

@@ -0,0 +1,17 @@
+# BMAD Cyber: Secure Certificate Generation
+
+Automated workflow for generating self-signed certificates using the `self-signed-cert` skill.
+
+## Instructions
+1.  **Load Skill**: Activate the `self-signed-cert` skill instructions.
+2.  **Requirement Analysis**: Determine common name (CN) and Subject Alternative Names (SANs).
+3.  **Execution**:
+    - **Linux/macOS**:
+        - `bash scripts/generate-cert.sh root my-internal-ca`
+        - `bash scripts/generate-cert.sh cert my-service localhost`
+    - **Windows**:
+        - `.\scripts\generate-cert.ps1 -Type root -Name my-internal-ca`
+        - `.\scripts\generate-cert.ps1 -Type cert -Name my-service -Dns localhost`
+4.  **Packaging**: Provide instructions for importing the cert into trust stores (OS, Browsers) or mounting in Kubernetes secrets.
+5.  **Security**: Ensure private keys are stored with restricted permissions (600).
+6.  **Rotation**: Offer a schedule for certificate renewal.

package/skills/bmad-cyber-generate-certs/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD Cyber: Generate Certs",
+    "description": "Automated workflow for generating self-signed certificates using the self-signed-cert skill",
+    "version": "1.0.0",
+    "author": "Cyber Analyst",
+    "tags": [
+        "bmad",
+        "cyber",
+        "security",
+        "certificates"
+    ]
+}

package/skills/bmad-cyber-immunity-estimation/SKILL.md

@@ -0,0 +1,19 @@
+# BMAD Cyber: Immunity Estimation
+
+Assesses the overall security posture and 'immunity' of the system against common attack vectors.
+
+## Instructions
+1.  **Attack Surface Analysis**: Identify all entry points (APIs, UI, SSH, 3rd party integrations).
+2.  **Control Verification**:
+    - Authentication/Authorization presence.
+    - Encryption in transit and at rest.
+    - Secret management maturity (Hardcoded vs Vault).
+3.  **Posture Scoring**: Rate 1-10 on:
+    - Code quality/Sanitization.
+    - Dependency health.
+    - Infrastructure hardening.
+    - Visibility/Logging.
+4.  **Immunity Report**:
+    - Summarize major gaps.
+    - Provide a roadmap for reach 'Immunity Level 5' (Robust).
+5.  **Verification**: Recommend automated regression tests for security controls.

package/skills/bmad-cyber-immunity-estimation/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD Cyber: Immunity Estimation",
+    "description": "Assess overall security posture and immunity against common attack vectors",
+    "version": "1.0.0",
+    "author": "Cyber Analyst",
+    "tags": [
+        "bmad",
+        "cyber",
+        "security",
+        "assessment"
+    ]
+}

package/skills/bmad-cyber-security-audit/SKILL.md

@@ -0,0 +1,17 @@
+# BMAD Cyber: Comprehensive Security Audit
+
+Deep-dive audit of infrastructure and application configuration.
+
+## Instructions
+1.  **Infrastructure Audit**:
+    - **K8s**: Check for privileged containers, missing network policies, root users.
+    - **Docker**: Check for exposed ports, unnecessary packages in images.
+2.  **Code Audit**:
+    - Static Analysis (SAST) for common patterns (SQLi, XSS).
+    - Check for insecure defaults in frameworks.
+3.  **Identity Audit**:
+    - Review ServiceAccount permissions (RBAC).
+    - Check for hard-coded credentials.
+4.  **Final Recommendation**: 
+    - Provide a prioritized list of hardening tasks.
+    - Propose CIDCD guardrails.

package/skills/bmad-cyber-security-audit/skill.json

@@ -0,0 +1,13 @@
+{
+    "name": "BMAD Cyber: Security Audit",
+    "description": "Deep-dive audit of infrastructure and application configuration",
+    "version": "1.0.0",
+    "author": "Cyber Analyst",
+    "tags": [
+        "bmad",
+        "cyber",
+        "audit",
+        "infrastructure",
+        "code"
+    ]
+}

package/skills/bmad-cyber-vault-secrets/SKILL.md

@@ -0,0 +1,18 @@
+# BMAD Cyber: Vault Secret Management
+
+This skill guides the agent through managing secrets, policies, and authentication in HashiCorp Vault.
+
+## Instructions
+1.  **Check Connection**: Verify `vault status` and authentication.
+2.  **Secret Creation/Update**:
+    - `vault kv put secret/{path} {key}={value}`
+    - Ensure secrets are never logged or echoed in plain text.
+3.  **Policy Management**:
+    - Define HCL policies for restricted access.
+    - `vault policy write {name} {policy_file}`
+4.  **Integration**:
+    - Manage Kubernetes auth method: `vault auth enable kubernetes`
+    - Setup Vault Agent injector configurations.
+5.  **Audit**:
+    - Check for expired tokens or orphaned secrets.
+    - Review access logs if available.

package/skills/bmad-cyber-vault-secrets/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD Cyber: Vault Secrets",
+    "description": "Manage secrets, policies, and authentication in HashiCorp Vault",
+    "version": "1.0.0",
+    "author": "Cyber Analyst",
+    "tags": [
+        "bmad",
+        "cyber",
+        "vault",
+        "secrets"
+    ]
+}

package/skills/bmad-cyber-verify-docker-users/SKILL.md

@@ -0,0 +1,13 @@
+# BMAD Cyber: Docker User & Hardening Verification
+
+This skill guides the Cyber agent through auditing Docker images for proper user management and least privilege.
+
+## Instructions
+1.  **Inspect Metadata**:
+    - Use the `docker-hardening-verification` skill.
+    - Run: `bash skills/docker-hardening-verification/scripts/verify-hardening.sh {image_name}`.
+2.  **Audit Result Analysis**:
+    - **UID Check**: Confirm the defined user is non-zero.
+    - **Permissive Files**: Scan for world-writable files in common paths (/tmp, /etc, /var).
+3.  **Governance Check**: Ensure the image follows OpenShift/hardened cluster requirements (no root, arbitrary UID support).
+4.  **Reporting**: provide a high-level summary of hardening quality and mandatory fixes.

package/skills/bmad-cyber-verify-docker-users/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD Cyber: Verify Docker Users",
+    "description": "Audit Docker images for proper user management and least privilege",
+    "version": "1.0.0",
+    "author": "Cyber Analyst",
+    "tags": [
+        "bmad",
+        "cyber",
+        "docker",
+        "hardening"
+    ]
+}

package/skills/bmad-cyber-verify-image-signature/SKILL.md

@@ -0,0 +1,12 @@
+# BMAD Cyber: Docker Image Signature Verification
+
+This skill guides the Cyber agent through verifying that a Docker image has been properly signed.
+
+## Instructions
+1.  **Identify Image**: Get the image name and digest.
+2.  **Locate Public Key**: Obtain the public key or certificate used for signing.
+3.  **Execute Verification**:
+    - Use `cosign verify --key {public_key} {image_digest}`.
+    - Check the output for valid signatures.
+4.  **Policy Compliance**: Verify if the signing entity (certificate CN) matches the expected trusted authorities.
+5.  **Report**: Alert the user if the image is unsigned or the signature is invalid.

package/skills/bmad-cyber-verify-image-signature/skill.json

@@ -0,0 +1,13 @@
+{
+    "name": "BMAD Cyber: Verify Image Signature",
+    "description": "Verify that a Docker image has been properly signed",
+    "version": "1.0.0",
+    "author": "Cyber Analyst",
+    "tags": [
+        "bmad",
+        "cyber",
+        "security",
+        "docker",
+        "cosign"
+    ]
+}

package/skills/bmad-cyber-vulnerability-scan/SKILL.md

@@ -0,0 +1,18 @@
+# BMAD Cyber: Vulnerability Scan Orchestration
+
+Orchestrates multiple security-focused skills from the `ma-agents` package to provide a comprehensive security scan.
+
+## Instructions
+1.  **Select Scanners**: Based on project tech stack, trigger:
+    - **JS/TS**: `js-ts-security-skill`
+    - **Python**: `python-security-skill`
+    - **Docker**: `verify-hardened-docker-skill`
+2.  **Run Tools**:
+    - Execute `npm audit` or `yarn audit`.
+    - Run `pip-audit` for Python environments.
+    - Run `trivy image {image}` for containers.
+3.  **Aggregate Results**: Collect all findings into a unified report.
+4.  **Prioritization**: Rank vulnerabilities by CVSS score and exploitability.
+5.  **Remediation**:
+    - Propose version upgrades.
+    - Propose configuration hardening steps.

package/skills/bmad-cyber-vulnerability-scan/skill.json

@@ -0,0 +1,13 @@
+{
+    "name": "BMAD Cyber: Vulnerability Scan",
+    "description": "Orchestrate security-focused skills for a comprehensive security scan",
+    "version": "1.0.0",
+    "author": "Cyber Analyst",
+    "tags": [
+        "bmad",
+        "cyber",
+        "security",
+        "scan",
+        "vulnerability"
+    ]
+}

package/skills/bmad-devops-configure-infrastructure/SKILL.md

@@ -0,0 +1,17 @@
+# BMAD DevOps: Configure Infrastructure
+
+This skill focuses on defining and configuring core infrastructure components in a Kubernetes environment.
+
+## Instructions
+1.  **Storage Definition**:
+    - Define `PersistentVolume` (PV) with appropriate access modes and storage classes.
+    - Define `PersistentVolumeClaim` (PVC) for application workloads.
+2.  **Networking**:
+    - Configure `Service` type `LoadBalancer` or `Ingress` controllers.
+    - Define `NetworkPolicies` for secure communication.
+3.  **Disconnected Environments**:
+    - Provide templates for local storage provisioners (e.g., hostPath, Local Persistent Volumes).
+    - Configure static IP assignments for on-prem load balancers.
+4.  **Validation**:
+    - Verify binding status: `kubectl get pv,pvc`
+    - Verify endpoint availability: `kubectl get endpoints`

package/skills/bmad-devops-configure-infrastructure/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD DevOps: Configure Infrastructure",
+    "description": "Define and configure core infrastructure components in a Kubernetes environment",
+    "version": "1.0.0",
+    "author": "DevOps Agent",
+    "tags": [
+        "bmad",
+        "devops",
+        "kubernetes",
+        "infrastructure"
+    ]
+}

package/skills/bmad-devops-disconnected-deployment/SKILL.md

@@ -0,0 +1,17 @@
+# BMAD DevOps: Disconnected Environment Deployment
+
+Strategies and actions for deploying applications in air-gapped or restricted on-prem environments.
+
+## Instructions
+1.  **Dependency Gathering**:
+    - Identify all required container images.
+    - Export images: `docker save {image_list} | gzip > images.tar.gz`
+    - Package Helm charts: `helm package {chart_path}`
+2.  **Target Readiness**:
+    - Verify local registry availability.
+    - Import images: `docker load < images.tar.gz`
+3.  **Deployment**:
+    - Use `--set image.repository={local_registry}/{repo}` for Helm.
+    - Verify offline connectivity between components.
+4.  **Troubleshooting**:
+    - Check for 'ImagePullBackOff' due to incorrect registry paths.

package/skills/bmad-devops-disconnected-deployment/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD DevOps: Disconnected Deployment",
+    "description": "Strategies for deploying applications in air-gapped or restricted on-prem environments",
+    "version": "1.0.0",
+    "author": "DevOps Agent",
+    "tags": [
+        "bmad",
+        "devops",
+        "air-gap",
+        "disconnected"
+    ]
+}

package/skills/bmad-devops-docker-compose-setup/SKILL.md

@@ -0,0 +1,16 @@
+# BMAD DevOps: Docker Compose Management
+
+This skill handles multi-container orchestration using Docker Compose, optimized for development and on-prem deployments.
+
+## Instructions
+1.  **Define Services**: Map application components to Docker services.
+2.  **Environment Sync**: Setup `.env` file management for different environments (on-prem, dev).
+3.  **Disconnected Operations**:
+    - Build images with `--pull=false` if registry is unavailable.
+    - Use local image tags.
+4.  **Orchestration**:
+    - Setup dependencies with `depends_on` and health checks.
+    - Configure volumes for persistence.
+5.  **Execution**:
+    - `docker-compose up -d`
+    - `docker-compose ps`

package/skills/bmad-devops-docker-compose-setup/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD DevOps: Docker Compose Setup",
+    "description": "Multi-container orchestration using Docker Compose optimized for dev and on-prem",
+    "version": "1.0.0",
+    "author": "DevOps Agent",
+    "tags": [
+        "bmad",
+        "devops",
+        "docker",
+        "docker-compose"
+    ]
+}

package/skills/bmad-devops-manage-helm/SKILL.md

@@ -0,0 +1,18 @@
+# BMAD DevOps: Manage Helm
+
+This skill handles the creation and management of Helm charts and Helm umbrellas for complex systems.
+
+## Instructions
+1.  **Analyze System**: Determine if a single chart or an umbrella chart (multiple sub-charts) is needed.
+2.  **Chart Creation**: 
+    - `helm create {chart_name}`
+    - Structure for disconnected environments: Ensure all chart dependencies are bundled (vendorized).
+3.  **Helm Umbrella Setup**:
+    - Configure `Chart.yaml` with sub-chart dependencies.
+    - Setup `values.yaml` to override sub-chart values.
+4.  **On-prem Optimization**:
+    - Prepare `chart-save` and `chart-load` routines for air-gapped systems.
+    - Configure local registry mirrors.
+5.  **Validation**:
+    - `helm lint {chart_path}`
+    - `helm template {chart_path}`

package/skills/bmad-devops-manage-helm/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD DevOps: Manage Helm",
+    "description": "Create and manage Helm charts and umbrellas for complex systems",
+    "version": "1.0.0",
+    "author": "DevOps Agent",
+    "tags": [
+        "bmad",
+        "devops",
+        "helm",
+        "kubernetes"
+    ]
+}

package/skills/bmad-devops-sign-docker-image/SKILL.md

@@ -0,0 +1,14 @@
+# BMAD DevOps: Docker Image Signing
+
+This skill guides the DevOps agent through the process of cryptographically signing a Docker image.
+
+## Instructions
+1.  **Select Image**: Identify the image to sign.
+2.  **Get Digest**: Retrieve the immutable digest: `docker inspect --format='{{index .RepoDigests 0}}' {image_name}`.
+3.  **Prepare Certificate**: Locate the certificate file provided by the user.
+4.  **Execute Signing**:
+    - Use the `docker-image-signing` skill.
+    - Path: `skills/docker-image-signing/scripts/sign-image.sh`
+    - Run: `bash skills/docker-image-signing/scripts/sign-image.sh {image_digest} {cert_file} {key_file}`
+5.  **Verify**: Confirm the signature using `cosign verify`.
+6.  **Report**: provide the signed image reference to the user.

package/skills/bmad-devops-sign-docker-image/skill.json

@@ -0,0 +1,13 @@
+{
+    "name": "BMAD DevOps: Sign Docker Image",
+    "description": "Cryptographically sign Docker images for secure supply chain",
+    "version": "1.0.0",
+    "author": "DevOps Agent",
+    "tags": [
+        "bmad",
+        "devops",
+        "security",
+        "docker",
+        "signing"
+    ]
+}

package/skills/bmad-mil-generate-ocd/SKILL.md

@@ -0,0 +1,16 @@
+# Generate Mil-498 OCD
+
+This skill generates an Operational Concept Description (OCD) based on the MIL-STD-498 template and BMAD-METHOD records (PRD, Architecture, and UX).
+
+## Instructions
+1.  **Template**: Load the MIL-STD-498 OCD template from `{project-root}/_bmad/bmm/templates/mil498/OCD.md`.
+2.  **Input Data**:
+    -   Extract the operational need and mission overview from the **PRD**.
+    -   Use the **Architecture** to describe the system's operational environment.
+    -   Extract user scenarios and workflows from the **UX Design** and **Stories**.
+3.  **Mapping**:
+    -   **Section 3 (Current system or situation)**: Describe the "as-is" state.
+    -   **Section 4 (Nature of proposed changes)**: Overview of the solution.
+    -   **Section 5 (Operational concept)**: Describe user roles, operational scenarios, and key workflows (from UX/Stories).
+4.  **Clarity**: Ensure the document is written in a way that is easily understood by system users and stakeholders.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `OCD.md`.

package/skills/bmad-mil-generate-ocd/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "Generate Mil-498 OCD",
+    "description": "Generates an Operational Concept Description (OCD) compliant with MIL-STD-498",
+    "version": "1.0.0",
+    "author": "Joseph",
+    "tags": [
+        "bmad",
+        "mil498",
+        "ocd",
+        "operation"
+    ]
+}

package/skills/bmad-mil-generate-sdd/SKILL.md

@@ -0,0 +1,16 @@
+# Generate Mil-498 SDD
+
+This skill generates a Software Design Description (SDD) based on the MIL-STD-498 template and BMAD-METHOD records (PRD, Architecture, UX, Epics, and Stories).
+
+## Instructions
+1.  **Template**: Load the MIL-STD-498 SSDD template from `{project-root}/_bmad/bmm/templates/mil498/SSDD.md`.
+2.  **Input Data**:
+    -   Use the **Architecture** document for high-level structure.
+    -   Extract detailed component logic from **Epics** and **Stories**.
+    -   Use **UX Design** for interface layouts and interaction flows.
+3.  **Mapping**:
+    -   **Section 3 (CSCI-wide design decisions)**: Map architectural decisions and design constraints.
+    -   **Section 4 (CSCI architectural design)**: Define components, their interfaces, and data flow.
+    -   **Section 5 (CSCI detailed design)**: Map Stories to detailed logic and internal data structures.
+4.  **Consistency**: Ensure the design matches the requirements specified in the SRS.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SDD.md`.

package/skills/bmad-mil-generate-sdd/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "Generate Mil-498 SDD",
+    "description": "Generates a Software Design Description (SDD) compliant with MIL-STD-498",
+    "version": "1.0.0",
+    "author": "Joseph",
+    "tags": [
+        "bmad",
+        "mil498",
+        "sdd",
+        "design"
+    ]
+}

package/skills/bmad-mil-generate-sdp/SKILL.md

@@ -0,0 +1,15 @@
+# Generate Mil-498 SDP
+
+This skill generates a Software Development Plan (SDP) based on the MIL-STD-498 template and BMAD-METHOD records (Product Brief and PRD).
+
+## Instructions
+1.  **Template**: Load the MIL-STD-498 SDP template from `{project-root}/_bmad/bmm/templates/mil498/SDP.md`.
+2.  **Input Data**:
+    -   Extract project overview and constraints from the **Product Brief**.
+    -   Use the **PRD** for scope and high-level requirements.
+3.  **Mapping**:
+    -   **Section 3 (Project organization and resources)**: Define the team structure and resource requirements.
+    -   **Section 4 (Software development process)**: Describe the BMAD-METHOD lifecycle used.
+    -   **Section 5 (Software development activities)**: Detail the tasks, schedules, and milestones.
+4.  **Consistency**: Ensure the plan reflects the actual development methodology being followed.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SDP.md`.

package/skills/bmad-mil-generate-sdp/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "Generate Mil-498 SDP",
+    "description": "Generates a Software Development Plan (SDP) compliant with MIL-STD-498",
+    "version": "1.0.0",
+    "author": "Joseph",
+    "tags": [
+        "bmad",
+        "mil498",
+        "sdp",
+        "planning"
+    ]
+}

package/skills/bmad-mil-generate-srs/SKILL.md

@@ -0,0 +1,18 @@
+# Generate Mil-498 SRS
+
+This skill generates a Software Requirements Specification (SRS) based on the MIL-STD-498 template and BMAD-METHOD records (PRD, Architecture, UX, and Epics).
+
+## Instructions
+1.  **Template**: Load the MIL-STD-498 SRS template from `{project-root}/_bmad/bmm/templates/mil498/SRS.md`.
+2.  **Input Data**:
+    -   Gather requirements from the **PRD**.
+    -   Extract interface requirements from the **Architecture** document.
+    -   Extract user interface constraints from the **UX Design** document.
+    -   Map functional requirements to the **Epics**.
+3.  **Mapping**:
+    -   **Section 3.1 (Required States and Modes)**: Map system states defined in the PRD/Architecture.
+    -   **Section 3.2 (CSCI Capability Requirements)**: Map functional requirements from PRD and Epics.
+    -   **Section 3.3 (External Interface Requirements)**: Map Architecture interface definitions here.
+    -   **Section 3.10 (Computer Resource Requirements)**: Extract hardware/software constraints from the Architecture document.
+4.  **Traceability**: Ensure each requirement has a unique CID and is traced to the original PRD entry.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SRS.md`.

package/skills/bmad-mil-generate-srs/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "Generate Mil-498 SRS",
+    "description": "Generates a Software Requirements Specification (SRS) compliant with MIL-STD-498",
+    "version": "1.0.0",
+    "author": "Joseph",
+    "tags": [
+        "bmad",
+        "mil498",
+        "srs",
+        "documentation"
+    ]
+}

package/skills/bmad-mil-generate-sss/SKILL.md

@@ -0,0 +1,15 @@
+# Generate Mil-498 SSS
+
+This skill generates a System/Subsystem Specification (SSS) based on the MIL-STD-498 template and BMAD-METHOD records (Product Brief and PRD).
+
+## Instructions
+1.  **Template**: Load the MIL-STD-498 SSS template from `{project-root}/_bmad/bmm/templates/mil498/SSS.md`.
+2.  **Input Data**:
+    -   Use the **Product Brief** for high-level system objectives.
+    -   Extract system-level functional and non-functional requirements from the **PRD**.
+3.  **Mapping**:
+    -   **Section 3.1 (System capability requirements)**: Map top-level functional requirements.
+    -   **Section 3.3 (System external interface requirements)**: Map top-level interfaces.
+    -   **Section 3.4 (System internal interface requirements)**: Map interfaces between major subsystems.
+4.  **High-Level Focus**: Keep requirements at the system/subsystem level, avoiding low-level software details.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `SSS.md`.

package/skills/bmad-mil-generate-sss/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "Generate Mil-498 SSS",
+    "description": "Generates a System/Subsystem Specification (SSS) compliant with MIL-STD-498",
+    "version": "1.0.0",
+    "author": "Joseph",
+    "tags": [
+        "bmad",
+        "mil498",
+        "sss",
+        "specification"
+    ]
+}

package/skills/bmad-mil-generate-std/SKILL.md

@@ -0,0 +1,16 @@
+# Generate Mil-498 STD
+
+This skill generates a Software Test Description (STD) based on the MIL-STD-498 template and BMAD-METHOD records (Architecture, Epics, and Stories).
+
+## Instructions
+1.  **Template**: Load the MIL-STD-498 STD template from `{project-root}/_bmad/bmm/templates/mil498/STD.md`.
+2.  **Input Data**:
+    -   Use the **Architecture** to define the test environment.
+    -   Extract test scenarios from **Epics**.
+    -   Extract detailed acceptance criteria from **Stories**.
+3.  **Mapping**:
+    -   **Section 3 (Test preparations)**: Describe hardware/software needed for testing.
+    -   **Section 4 (Test descriptions)**: Map Story acceptance criteria to specific test cases and procedures.
+    -   **Section 5 (Requirements traceability)**: Link each test case to one or more SRS requirements.
+4.  **Verification**: Ensure all requirements in the SRS have at least one test case.
+5.  **Output**: Save the generated document to the `{output_folder}/planning-artifacts/` as `STD.md`.

package/skills/bmad-mil-generate-std/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "Generate Mil-498 STD",
+    "description": "Generates a Software Test Description (STD) compliant with MIL-STD-498",
+    "version": "1.0.0",
+    "author": "Joseph",
+    "tags": [
+        "bmad",
+        "mil498",
+        "std",
+        "testing"
+    ]
+}

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

@@ -0,0 +1,22 @@
+# BMAD SRE: Check Deployment Status
+
+This skill 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/skills/bmad-sre-check-deployment-status/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD SRE: Check Deployment Status",
+    "description": "Guides checking the status of a specific deployment in a Kubernetes cluster",
+    "version": "1.0.0",
+    "author": "SRE Agent",
+    "tags": [
+        "bmad",
+        "sre",
+        "kubernetes",
+        "diagnostics"
+    ]
+}

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

@@ -0,0 +1,13 @@
+# BMAD SRE: Check Secrets
+
+This skill 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/skills/bmad-sre-check-secrets/skill.json

@@ -0,0 +1,13 @@
+{
+    "name": "BMAD SRE: Check Secrets",
+    "description": "Identify and resolve problems related to Kubernetes Secrets",
+    "version": "1.0.0",
+    "author": "SRE Agent",
+    "tags": [
+        "bmad",
+        "sre",
+        "kubernetes",
+        "security",
+        "secrets"
+    ]
+}

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

@@ -0,0 +1,17 @@
+# BMAD SRE: Check System Status
+
+This skill 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/skills/bmad-sre-check-system-status/skill.json

@@ -0,0 +1,13 @@
+{
+    "name": "BMAD SRE: Check System Status",
+    "description": "Overview of the health of the container runtime and orchestration environment",
+    "version": "1.0.0",
+    "author": "SRE Agent",
+    "tags": [
+        "bmad",
+        "sre",
+        "kubernetes",
+        "docker",
+        "diagnostics"
+    ]
+}

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

@@ -0,0 +1,15 @@
+# BMAD SRE: Day 2 Operations & Maintenance
+
+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/skills/bmad-sre-day-2-ops/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD SRE: Day 2 Operations",
+    "description": "Long-term stability, cluster-to-config verification, and periodic maintenance",
+    "version": "1.0.0",
+    "author": "SRE Agent",
+    "tags": [
+        "bmad",
+        "sre",
+        "maintenance",
+        "optimization"
+    ]
+}

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

@@ -0,0 +1,17 @@
+# BMAD SRE: Deployment Strategies
+
+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/skills/bmad-sre-deployment-strategies/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD SRE: Deployment Strategies",
+    "description": "Implement and monitor Blue-Green, Canary, and Rolling Updates",
+    "version": "1.0.0",
+    "author": "SRE Agent",
+    "tags": [
+        "bmad",
+        "sre",
+        "deployment",
+        "strategies"
+    ]
+}

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

@@ -0,0 +1,15 @@
+# BMAD SRE: Deployment Fix
+
+This skill 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/skills/bmad-sre-fix-deployments/skill.json

@@ -0,0 +1,12 @@
+{
+    "name": "BMAD SRE: Fix Deployments",
+    "description": "Automated troubleshooting and resolution of common deployment issues",
+    "version": "1.0.0",
+    "author": "SRE Agent",
+    "tags": [
+        "bmad",
+        "sre",
+        "troubleshooting",
+        "fix"
+    ]
+}

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

@@ -0,0 +1,15 @@
+# BMAD SRE: GitOps Status & Drift Detection
+
+This skill 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/skills/bmad-sre-gitops-status/skill.json

@@ -0,0 +1,13 @@
+{
+    "name": "BMAD SRE: GitOps Status",
+    "description": "Monitor and report sync state between git repo and cluster (ArgoCD/Flux)",
+    "version": "1.0.0",
+    "author": "SRE Agent",
+    "tags": [
+        "bmad",
+        "sre",
+        "gitops",
+        "argocd",
+        "flux"
+    ]
+}