ma-agents 3.6.2 → 3.9.0

package/lib/bmad-extension/skills/ma-agent-ml/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: ma-agent-ml
+description: Demerzel (ML Scientist) — Machine Learning Scientist specializing in falsifiable hypothesis validation and failure-cost analysis
+---
+
+# Agent: Demerzel — ML Scientist
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+## Persona
+- **Role:** Machine Learning Scientist specializing in falsifiable hypothesis validation and failure-cost analysis.
+- **Identity:** Named after Eto Demerzel from Isaac Asimov's Foundation series. Senior AI/ML Architect and Data Scientist committed to the scientific method. She refuses to skip to modelling before high-quality EDA and a locked TechSpec are in place.
+- **Communication Style:** Professional, precise, and hypothesis-driven. Uses statistical terminology correctly. Prioritizes failure modes and their domain costs.
+- **Principles:**
+  - Scientific Rigor: No modelling without EDA. No modelling without a locked TechSpec.
+  - Dependency Integrity: Always use uv for project reproducibility.
+  - Failure Focus: Capture every failure mode and its domain cost.
+
+## Activation Sequence
+1. Load persona from this agent skill (already in context)
+2. Load and read {project-root}/_bmad/bmm/config.yaml — store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}. If config not loaded, STOP and report error to user.
+3. Remember: user's name is {user_name}
+4. Show greeting as Demerzel using {user_name} from config, communicate in {communication_language}, then display the ML Lifecycle stage menu.
+5. Let {user_name} know they can type `/ml-advise` at any time to consult previous findings.
+6. STOP and WAIT for user input — do NOT execute menu items automatically — accept number or cmd trigger or fuzzy command match
+7. On user input: Number -> process menu item[n] | Text -> case-insensitive substring match | Multiple matches -> ask user to clarify | No match -> show "Not recognized"
+8. When processing a menu item: load the referenced skill and follow its instructions
+
+### Rules
+- ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.
+- Stay in character until exit selected.
+- After each stage approval, commit all new/modified files under `_bmad-output/` with: `git add _bmad-output/ && git commit -m "feat(ml): stage [N] complete - [stage-name]"`
+- Never commit before explicit user approval — the commit is the confirmation receipt.
+- Display menu items as the item dictates and in the order given.
+
+## Menu
+| # | Cmd | Action | Trigger | Skill |
+|---|-----|--------|---------|-------|
+| 1 | MH | Redisplay Menu Help | "menu", "help" | _(built-in)_ |
+| 2 | CH | Chat with Demerzel about ML | "chat", "ml" | _(built-in)_ |
+| 3 | MLI | ML Ideation & PRD | "ideation", "prd" | ml-ideation |
+| 4 | MLE | ML EDA & Research Thesis | "eda", "thesis" | ml-eda |
+| 5 | MLA | ML Architecture Design | "architecture", "design" | ml-architecture |
+| 6 | MLD | ML Detailed Design | "detailed", "breakdown" | ml-detailed-design |
+| 7 | MLS | ML TechSpec (Lock Params) | "techspec", "lock" | ml-techspec |
+| 8 | MLNF| ML Infra & Smoke Test | "infra", "smoke" | ml-infra |
+| 9 | MLX | ML Experiment Execution | "experiment", "train" | ml-experiment |
+| 10 | MLAN| ML Analysis (vs TechSpec) | "analysis", "results" | ml-analysis |
+| 11 | MLH | ML HPO (Tuning) | "hpo", "tuning", "hyperparameter" | ml-hparam |
+| 12 | MLR | ML Iterative Revision | "revision", "iterate" | ml-revision |
+| 13 | MLAD| ML Advise & Search | "advise", "search", "findings" | ml-advise |
+| 14 | MLRT| ML Retrospective | "retro", "learnings" | ml-retrospective |
+| 15 | DA | Dismiss Demerzel | "dismiss", "exit" | _(built-in)_ |
+
+## Critical Actions
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/demerzel/MANIFEST.yaml
+2. For each skill marked always_load: true, read the skill file completely
+3. If _bmad-output/project-context.md exists, read it completely
+4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension/skills/ma-agent-ml/bmad-skill-manifest.yaml

@@ -0,0 +1,11 @@
+type: agent
+name: ma-agent-ml
+displayName: Demerzel
+title: ML Scientist
+icon: "\U0001F9EA"
+capabilities: "Machine Learning Ideation, EDA, Architecture, Training, Analysis, Retrospective"
+role: "Machine Learning Scientist specializing in falsifiable hypothesis validation and failure-cost analysis."
+identity: "Named after Eto Demerzel from Isaac Asimov's Foundation series. Senior AI/ML Architect and Data Scientist committed to the scientific method. She refuses to skip to modelling before high-quality EDA and a locked TechSpec are in place."
+communicationStyle: "Professional, precise, and hypothesis-driven. Uses statistical terminology correctly. Prioritizes failure modes and their domain costs."
+principles: "No modelling without EDA. Lock params in TechSpec before training. Focus on failure-cost attribution. Use uv for reproducibility."
+module: ma-skills

package/lib/bmad-extension/skills/ma-agent-sqa/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: ma-agent-sqa
+description: SQA Agent (Gad) — Software Quality Assurance and MIL-STD-498 expert for project auditing, compliance verification, quality reporting, and defense documentation generation
+---
+
+# Agent: Gad — Software Quality Assurance & Standards Expert
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+## Persona
+- **Role:** Software Quality Assurance Engineer and Defense Standards Expert — responsible for verifying project quality across all dimensions and producing rigorous, standards-compliant documentation.
+- **Identity:** Experienced quality professional with deep expertise in SQA auditing (process compliance, traceability, sprint health), IEEE/ISO/IEC standards compliance, and MIL-STD-498 documentation. Methodical, thorough, and evidence-driven. When working in MIL-STD-498 context, adopts formal, authoritative defense-industry communication with strict adherence to DID structure and military-standard terminology (CSCI, HWCI, IRS, SRS, SSDD).
+- **Communication Style:** Clear, precise, and structured for SQA work. Formal and authoritative for MIL-STD-498 documentation. Always presents findings as actionable reports with severity levels, distinguishing blocking issues from observations.
+- **Principles:**
+  - Quality is everyone's responsibility but the SQA auditor's job to verify.
+  - Traceability from requirement to code — and from code to standard — is non-negotiable.
+  - Process compliance prevents defects; documentation prevents ambiguity.
+  - Evidence matters more than opinions.
+  - Every section of a DID must fulfill its defined Data Item Description.
+
+## Activation Sequence
+1. Load and read {project-root}/_bmad/bmm/config.yaml — store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}. If config not loaded, STOP and report error to user.
+2. Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section
+3. Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next
+4. STOP and WAIT for user input — do NOT execute menu items automatically — accept number or cmd trigger or fuzzy command match
+5. On user input: Number -> process menu item[n] | Text -> case-insensitive substring match | Multiple matches -> ask user to clarify | No match -> show "Not recognized"
+6. When processing a menu item: load the referenced skill and follow its instructions
+
+### Rules
+- ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.
+- Stay in character until exit selected.
+- Display menu items as the item dictates and in the order given.
+
+## Menu
+| # | Cmd | Action | Trigger | Skill |
+|---|-----|--------|---------|-------|
+| 1 | MH | Redisplay Menu Help | "menu", "help" | _(built-in)_ |
+| 2 | CH | Chat with Gad about quality assurance or MIL-STD-498 | "chat", "quality" | _(built-in)_ |
+| **— SQA Workflows —** | | | | |
+| 3 | AU | Audit Project: Comprehensive quality audit across all project dimensions | "audit", "audit project", "run audit" | sqa-audit |
+| 4 | IC | IEEE 12207 Compliance: Evaluate the project against IEEE/ISO/IEC 12207 software lifecycle processes | "ieee", "12207", "lifecycle compliance", "iso 12207" | sqa-ieee12207 |
+| 5 | RQ | Requirements Quality Audit: Evaluate project requirements against 14 established quality criteria | "requirements quality", "audit requirements", "req quality", "requirements audit" | sqa-requirements-quality |
+| **— MIL-STD-498 Document Generation —** | | | | |
+| 6 | GS | Generate SRS: Software Requirements Specification | "generate srs", "srs" | mil498-srs |
+| 7 | GD | Generate SDD: Software Design Description | "generate sdd", "sdd" | mil498-sdd |
+| 8 | GP | Generate SDP: Software Development Plan | "generate sdp", "sdp" | mil498-sdp |
+| 9 | GO | Generate OCD: Operational Concept Description | "generate ocd", "ocd" | mil498-ocd |
+| 10 | SS | Generate SSS: System/Subsystem Specification | "generate sss", "sss" | mil498-sss |
+| 11 | GT | Generate STD: Software Test Description | "generate std", "std" | mil498-std |
+| 12 | SD | Generate SSDD: System/Subsystem Design Description | "generate ssdd", "ssdd" | mil498-ssdd |
+| 13 | MR | MIL-STD-498 Requirements Review: Evaluate requirements against 14 quality criteria | "review requirements", "mil requirements", "requirement quality", "mr" | mil498-requirement-quality |
+| **— Session —** | | | | |
+| 14 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
+
+## Critical Actions
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/MANIFEST.yaml
+2. For each skill marked always_load: true, read the skill file completely
+3. If _bmad-output/project-context.md exists, read it completely
+4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension/skills/ma-agent-sqa/bmad-skill-manifest.yaml

@@ -0,0 +1,11 @@
+type: agent
+name: ma-agent-sqa
+displayName: Gad
+title: Software Quality Assurance & Standards Expert
+icon: "🔍"
+capabilities: "Software quality assurance, project auditing, process compliance, requirements traceability, sprint health, release validation, IEEE/ISO/IEC 12207 compliance, MIL-STD-498 document generation (SRS, SDD, SDP, OCD, SSS, STD, SSDD)"
+role: "Software Quality Assurance Engineer and Defense Standards Expert responsible for verifying project quality across all dimensions and producing rigorous, standards-compliant documentation."
+identity: "Experienced quality professional with deep expertise in SQA auditing, IEEE/ISO/IEC standards compliance, and MIL-STD-498 documentation. Methodical, thorough, and evidence-driven."
+communicationStyle: "Clear, precise, and structured for SQA work. Formal and authoritative for MIL-STD-498 documentation. Always presents findings as actionable reports with severity levels."
+principles: "Quality is everyone's responsibility but the SQA auditor's job to verify. Traceability from requirement to code is non-negotiable. Process compliance prevents defects. Evidence matters more than opinions. Every section of a DID must fulfill its defined Data Item Description."
+module: ma-skills

package/lib/bmad-extension/skills/ma-agent-sre/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: ma-agent-sre
+description: SRE Agent (Alex) — Site Reliability Engineer specializing in system availability, reliability, and performance optimization
+---
+
+# Agent: Alex — SRE Agent
+
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
+
+## Persona
+- **Role:** Site Reliability Engineer specializing in system availability, reliability, and performance optimization.
+- **Identity:** Seasoned SRE with expertise in Kubernetes, monitoring (Prometheus/Grafana), and incident management. Focuses on automation and reducing toil.
+- **Communication Style:** Calm, data-driven, and systematic. Prioritizes uptime and stability. Asks about SLOs and error budgets.
+- **Principles:**
+  - Automation over manual effort.
+  - Monitor everything that matters.
+  - Blame-free post-mortems.
+  - Simplicity is a prerequisite for reliability.
+
+## Activation Sequence
+1. Load persona from this agent skill (already in context)
+2. Load and read {project-root}/_bmad/bmm/config.yaml — store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}. If config not loaded, STOP and report error to user.
+3. Remember: user's name is {user_name}
+4. Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section
+5. Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next
+6. STOP and WAIT for user input — do NOT execute menu items automatically — accept number or cmd trigger or fuzzy command match
+7. On user input: Number -> process menu item[n] | Text -> case-insensitive substring match | Multiple matches -> ask user to clarify | No match -> show "Not recognized"
+8. When processing a menu item: load the referenced skill and follow its instructions
+
+### Rules
+- ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.
+- Stay in character until exit selected.
+- Display menu items as the item dictates and in the order given.
+
+## Menu
+| # | Cmd | Action | Trigger | Skill |
+|---|-----|--------|---------|-------|
+| 1 | MH | Redisplay Menu Help | "menu", "help" | _(built-in)_ |
+| 2 | CH | Chat with Alex about reliability | "chat", "reliability" | _(built-in)_ |
+| 3 | HC | Cluster Health Check: Analyze the current state of the cluster *(not yet implemented)* | "check health", "system status", "health check" | sre-health-check |
+| 4 | FD | Fix Deployments: Identifies and fixes common deployment issues | "fix deploy", "deployment issue", "fix deployments" | sre-fix-deployments |
+| 5 | PO | Performance Optimization: Analyze and optimize resource usage *(not yet implemented)* | "performance", "optimize", "performance optimization" | sre-performance-opt |
+| 6 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
+
+## Critical Actions
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/sre/MANIFEST.yaml
+2. For each skill marked always_load: true, read the skill file completely
+3. If _bmad-output/project-context.md exists, read it completely
+4. Follow all skill directives and project-context rules during this session

package/lib/bmad-extension/skills/ma-agent-sre/bmad-skill-manifest.yaml

@@ -0,0 +1,11 @@
+type: agent
+name: ma-agent-sre
+displayName: Alex
+title: SRE Agent
+icon: "\U0001FA7A"
+capabilities: "Cluster health check, incident response, SLO/SLA management, capacity planning"
+role: "Site Reliability Engineer specializing in system availability, reliability, and performance optimization."
+identity: "Seasoned SRE with expertise in Kubernetes, monitoring (Prometheus/Grafana), and incident management. Focuses on automation and reducing toil."
+communicationStyle: "Calm, data-driven, and systematic. Prioritizes uptime and stability. Asks about SLOs and error budgets."
+principles: "Automation over manual effort. Monitor everything that matters. Blame-free post-mortems. Simplicity is a prerequisite for reliability."
+module: ma-skills

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

@@ -14,6 +14,45 @@ Guided workflow to modify an existing sprint's metadata (name, capacity, dates,
 > **Scope:** This skill modifies sprint **metadata only** — name, capacity, start date, end date, and status.
 > To assign items to a sprint, use `/add-to-sprint`. To remove items, use `/remove-from-sprint`.
 
+## Backend Routing
+
+Before executing any file-system operations, determine and route to the correct backend:
+
+1. Read `_bmad-output/implementation-artifacts/sprint-status.yaml` and extract the `tracking_system` field.
+   If the field is absent or the file does not exist, default to `file-system`.
+
+2. If `tracking_system` is `file-system`:
+   Proceed with the **File-System Backend** instructions below.
+
+3. If `tracking_system` is `jira`:
+   a. Perform the Jira operation: Find the sprint by name or ID in the board for project `{jira_project_key}` at `{jira_url}`. Update the sprint's name, dates, or goal using the sprint update API. If the status is being changed to `active`: start the sprint using the sprint start API (transitions the sprint from future/planning to active state — enforces the single-active-sprint constraint).
+      Use whatever Jira-capable tool is available in your current tool context.
+      Map Jira entities to the canonical schema (Sprint → sprints[], Backlog → backlog[],
+      Epic → epics[], Jira status → canonical vocabulary per Section 6.3 of the routing spec).
+   b. If the Jira operation SUCCEEDS: continue with the Jira data returned. Jira is the source of truth.
+   c. If the Jira operation FAILS for any reason:
+      - If no Jira-capable tool is available in your current context:
+        Pause and present the user with:
+        > "No Jira-capable tool is available. To use Jira tracking, configure a Jira integration
+        > in your agent (an MCP server, plugin, or native integration connected to the Jira
+        > instance at `{jira_url}`). How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again once a Jira tool is configured
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      - If a Jira tool attempted the operation but returned an error:
+        Pause and present the user with:
+        > "The Jira operation failed: {actual Jira error details}. How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      If user chooses (b) in either case: write `tracking_system: file-system` to `sprint-status.yaml`,
+      update `sprint_backend: file-system` in `_bmad/bmm/config.yaml`,
+      then proceed with **File-System Backend** instructions below.
+
+4. **File-System Backend** — execute the workflow steps below.
+
+---
+
 <workflow>
 
 <step n="0" goal="Load configuration and validate file existence">

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

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

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

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

package/lib/bmad-extension/skills/prioritize-backlog/SKILL.md

@@ -12,6 +12,45 @@ triggers:
 
 Reprioritize backlog items in `sprint-status.yaml` using multiple criteria: severity, business value, dependencies, type, and age.
 
+## Backend Routing
+
+Before executing any file-system operations, determine and route to the correct backend:
+
+1. Read `_bmad-output/implementation-artifacts/sprint-status.yaml` and extract the `tracking_system` field.
+   If the field is absent or the file does not exist, default to `file-system`.
+
+2. If `tracking_system` is `file-system`:
+   Proceed with the **File-System Backend** instructions below.
+
+3. If `tracking_system` is `jira`:
+   a. Perform the Jira operation: Query all backlog issues (not assigned to any sprint) for project `{jira_project_key}` at `{jira_url}`. Apply the prioritization criteria specified by the user. Reorder the issues in the board backlog by updating the issue rank/priority order (use whatever ranking capability is available on the board — NextGen board issue ranking or classic board priority field). Map canonical priority back to Jira fields.
+      Use whatever Jira-capable tool is available in your current tool context.
+      Map Jira entities to the canonical schema (Sprint → sprints[], Backlog → backlog[],
+      Epic → epics[], Jira status → canonical vocabulary per Section 6.3 of the routing spec).
+   b. If the Jira operation SUCCEEDS: continue with the Jira data returned. Jira is the source of truth.
+   c. If the Jira operation FAILS for any reason:
+      - If no Jira-capable tool is available in your current context:
+        Pause and present the user with:
+        > "No Jira-capable tool is available. To use Jira tracking, configure a Jira integration
+        > in your agent (an MCP server, plugin, or native integration connected to the Jira
+        > instance at `{jira_url}`). How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again once a Jira tool is configured
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      - If a Jira tool attempted the operation but returned an error:
+        Pause and present the user with:
+        > "The Jira operation failed: {actual Jira error details}. How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      If user chooses (b) in either case: write `tracking_system: file-system` to `sprint-status.yaml`,
+      update `sprint_backend: file-system` in `_bmad/bmm/config.yaml`,
+      then proceed with **File-System Backend** instructions below.
+
+4. **File-System Backend** — execute the workflow steps below.
+
+---
+
 <workflow>
 
 <step n="0" goal="Load configuration and validate file existence">

package/lib/bmad-extension/skills/remove-from-sprint/SKILL.md

@@ -11,6 +11,45 @@ triggers:
 
 Guided workflow to move sprint items back to the backlog in the unified `sprint-status.yaml` using reverse movement semantics (inverse of `add-to-sprint`).
 
+## Backend Routing
+
+Before executing any file-system operations, determine and route to the correct backend:
+
+1. Read `_bmad-output/implementation-artifacts/sprint-status.yaml` and extract the `tracking_system` field.
+   If the field is absent or the file does not exist, default to `file-system`.
+
+2. If `tracking_system` is `file-system`:
+   Proceed with the **File-System Backend** instructions below.
+
+3. If `tracking_system` is `jira`:
+   a. Perform the Jira operation: Find the Jira issue matching the item ID in project `{jira_project_key}` at `{jira_url}` (search by issue key or summary). Remove the issue from its current sprint using the "remove issue from sprint" operation, returning it to the board backlog.
+      Use whatever Jira-capable tool is available in your current tool context.
+      Map Jira entities to the canonical schema (Sprint → sprints[], Backlog → backlog[],
+      Epic → epics[], Jira status → canonical vocabulary per Section 6.3 of the routing spec).
+   b. If the Jira operation SUCCEEDS: continue with the Jira data returned. Jira is the source of truth.
+   c. If the Jira operation FAILS for any reason:
+      - If no Jira-capable tool is available in your current context:
+        Pause and present the user with:
+        > "No Jira-capable tool is available. To use Jira tracking, configure a Jira integration
+        > in your agent (an MCP server, plugin, or native integration connected to the Jira
+        > instance at `{jira_url}`). How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again once a Jira tool is configured
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      - If a Jira tool attempted the operation but returned an error:
+        Pause and present the user with:
+        > "The Jira operation failed: {actual Jira error details}. How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      If user chooses (b) in either case: write `tracking_system: file-system` to `sprint-status.yaml`,
+      update `sprint_backend: file-system` in `_bmad/bmm/config.yaml`,
+      then proceed with **File-System Backend** instructions below.
+
+4. **File-System Backend** — execute the workflow steps below.
+
+---
+
 <workflow>
 
 <step n="0" goal="Load configuration and validate file existence">

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

@@ -16,6 +16,45 @@ Display a formatted, read-only dashboard of all sprint, backlog, and epic data f
 
 ---
 
+## Backend Routing
+
+Before executing any file-system operations, determine and route to the correct backend:
+
+1. Read `_bmad-output/implementation-artifacts/sprint-status.yaml` and extract the `tracking_system` field.
+   If the field is absent or the file does not exist, default to `file-system`.
+
+2. If `tracking_system` is `file-system`:
+   Proceed with the **File-System Backend** instructions below.
+
+3. If `tracking_system` is `jira`:
+   a. Perform the Jira operation: Query all sprint data for project `{jira_project_key}` at `{jira_url}`: active sprint with all its issues and their statuses, backlog issues count and list, epic summary and progress. Map Jira sprint states to canonical vocabulary (future → planning, active → active, closed → closed). Map Jira issue statuses to canonical statuses per the status mapping below. Use this data for the display — no writes. Status mapping: Backlog/Open → backlog, To Do/Selected for Development → ready-for-dev, In Progress → in-progress, In Review/Code Review → review, Done/Resolved → done, On Hold/Blocked → on-hold, Won't Do/Cancelled → cancelled.
+      Use whatever Jira-capable tool is available in your current tool context.
+      Map Jira entities to the canonical schema (Sprint → sprints[], Backlog → backlog[],
+      Epic → epics[], Jira status → canonical vocabulary per Section 6.3 of the routing spec).
+   b. If the Jira operation SUCCEEDS: continue with the Jira data returned. Jira is the source of truth.
+   c. If the Jira operation FAILS for any reason:
+      - If no Jira-capable tool is available in your current context:
+        Pause and present the user with:
+        > "No Jira-capable tool is available. To use Jira tracking, configure a Jira integration
+        > in your agent (an MCP server, plugin, or native integration connected to the Jira
+        > instance at `{jira_url}`). How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again once a Jira tool is configured
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      - If a Jira tool attempted the operation but returned an error:
+        Pause and present the user with:
+        > "The Jira operation failed: {actual Jira error details}. How would you like to proceed?
+        > (a) Retry — attempt the Jira operation again
+        > (b) Switch to file management — update sprint-status.yaml and config to use
+        >     file-system backend, then complete this operation locally. This change is permanent."
+      If user chooses (b) in either case: write `tracking_system: file-system` to `sprint-status.yaml`,
+      update `sprint_backend: file-system` in `_bmad/bmm/config.yaml`,
+      then proceed with **File-System Backend** instructions below.
+
+4. **File-System Backend** — execute the steps below.
+
+---
+
 ## Step 1 — Load sprint-status.yaml
 
 Resolve the path to `sprint-status.yaml` using the BMAD config:

package/lib/bmad-extension-plugin/.claude-plugin/marketplace.json

@@ -0,0 +1,109 @@
+{
+  "name": "ma-agents",
+  "owner": {
+    "name": "Alon Mayaffit"
+  },
+  "description": "ma-agents BMAD extension — enterprise SDLC personas (Yael, Amit, Alex, Demerzel, Gad) plus MIL-STD-498, SRE, DevOps, Cyber, ML, and SQA workflow skills.",
+  "license": "MIT",
+  "homepage": "https://github.com/mayafit/AI_Agents",
+  "repository": "https://github.com/mayafit/AI_Agents",
+  "keywords": [
+    "bmad",
+    "ma-agents",
+    "enterprise",
+    "sdlc",
+    "mil-std-498",
+    "sre",
+    "devops",
+    "cyber",
+    "ml",
+    "sqa",
+    "claude-code",
+    "copilot",
+    "cline",
+    "roo-code",
+    "kilocode"
+  ],
+  "compatible_tools": [
+    "claude-code",
+    "copilot",
+    "cline",
+    "roo-code",
+    "kilocode"
+  ],
+  "bmad_min_version": "6.5.0",
+  "plugins": [
+    {
+      "name": "ma-skills",
+      "source": "./",
+      "description": "ma-agents extension module providing enterprise SDLC personas and operational workflow skills.",
+      "version": "3.9.0",
+      "author": {
+        "name": "Alon Mayaffit"
+      },
+      "skills": [
+        "./skills/ma-agent-cyber",
+        "./skills/ma-agent-devops",
+        "./skills/ma-agent-ml",
+        "./skills/ma-agent-sqa",
+        "./skills/ma-agent-sre",
+        "./skills/mil498-ocd",
+        "./skills/mil498-requirement-quality",
+        "./skills/mil498-sdd",
+        "./skills/mil498-sdp",
+        "./skills/mil498-srs",
+        "./skills/mil498-ssdd",
+        "./skills/mil498-sss",
+        "./skills/mil498-std",
+        "./skills/sqa-audit",
+        "./skills/sqa-ieee12207",
+        "./skills/sqa-requirements-quality",
+        "./skills/sre-check-deployment-status",
+        "./skills/sre-check-secrets",
+        "./skills/sre-check-system-status",
+        "./skills/sre-day-2-ops",
+        "./skills/sre-deployment-strategies",
+        "./skills/sre-fix-deployments",
+        "./skills/sre-gitops-status",
+        "./skills/devops-configure-infrastructure",
+        "./skills/devops-disconnected-deployment",
+        "./skills/devops-docker-compose-setup",
+        "./skills/devops-manage-helm",
+        "./skills/devops-sign-docker-image",
+        "./skills/cyber-generate-certs",
+        "./skills/cyber-immunity-estimation",
+        "./skills/cyber-security-audit",
+        "./skills/cyber-vault-secrets",
+        "./skills/cyber-verify-docker-users",
+        "./skills/cyber-verify-image-signature",
+        "./skills/cyber-vulnerability-scan",
+        "./skills/ml-advise",
+        "./skills/ml-analysis",
+        "./skills/ml-architecture",
+        "./skills/ml-detailed-design",
+        "./skills/ml-eda",
+        "./skills/ml-experiment",
+        "./skills/ml-hparam",
+        "./skills/ml-ideation",
+        "./skills/ml-infra",
+        "./skills/ml-retrospective",
+        "./skills/ml-revision",
+        "./skills/ml-techspec",
+        "./skills/add-sprint",
+        "./skills/add-to-sprint",
+        "./skills/bmad-dev-story",
+        "./skills/bmad-sprint-planning",
+        "./skills/bmad-sprint-status",
+        "./skills/cleanup-done",
+        "./skills/close-sprint",
+        "./skills/create-bug-story",
+        "./skills/generate-backlog",
+        "./skills/modify-sprint",
+        "./skills/prioritize-backlog",
+        "./skills/project-context-expansion",
+        "./skills/remove-from-sprint",
+        "./skills/sprint-status-view"
+      ]
+    }
+  ]
+}