ma-agents 2.22.1 → 3.0.0

package/lib/bmad-customize/bmm-tech-writer.customize.yaml

@@ -0,0 +1,6 @@
+# MA-AGENTS: skill enforcement for bmm-tech-writer
+critical_actions:
+  - "Read the skills MANIFEST at {project-root}/skills/MANIFEST.yaml"
+  - "For each skill marked always_load: true, read the skill file completely"
+  - "If _bmad-output/project-context.md exists, read it completely"
+  - "Follow all skill directives and project-context rules during this session"

package/lib/bmad-customize/bmm-ux-designer.customize.yaml

@@ -0,0 +1,6 @@
+# MA-AGENTS: skill enforcement for bmm-ux-designer
+critical_actions:
+  - "Read the skills MANIFEST at {project-root}/skills/MANIFEST.yaml"
+  - "For each skill marked always_load: true, read the skill file completely"
+  - "If _bmad-output/project-context.md exists, read it completely"
+  - "Follow all skill directives and project-context rules during this session"

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

@@ -1,7 +1,37 @@
-module,phase,name,code,agent,file,command,yolo,tag,group,description,output_folder,output_type,notes
-ma-agents-skills,4-implementation,add-sprint,add-sprint,bmm-sm,lib/bmad-extension/workflows/add-sprint/workflow.md,/add-sprint,false,sprint,sprint-management,Create a new sprint with capacity limits and optional start/end context,_bmad-output/implementation-artifacts,yaml,Creates sprint-plan-{number}.yaml artifact
-ma-agents-skills,4-implementation,add-to-sprint,add-to-sprint,bmm-sm,lib/bmad-extension/workflows/add-to-sprint/workflow.md,/add-to-sprint,false,sprint,sprint-management,Assign backlog items (stories + bugs) to a sprint using multi-criteria prioritization,_bmad-output/implementation-artifacts,yaml,Updates sprint-plan-{number}.yaml assigned_items
-ma-agents-skills,4-implementation,modify-sprint,modify-sprint,bmm-sm,lib/bmad-extension/workflows/modify-sprint/workflow.md,/modify-sprint,false,sprint,sprint-management,Modify existing sprint — add/remove items, change capacity, update metadata with concurrency guard,_bmad-output/implementation-artifacts,yaml,Updates sprint-plan-{number}.yaml in place
-ma-agents-skills,4-implementation,sprint-status-view,sprint-status-view,bmm-sm,lib/bmad-extension/workflows/sprint-status-view/workflow.md,/sprint-status-view,false,sprint,sprint-management,View sprint progress with all assigned items (stories + bugs) and remaining capacity,_bmad-output/implementation-artifacts,display,Reads sprint-plan-*.yaml and sprint-status.yaml
-ma-agents-skills,4-implementation,create-bug-story,create-bug-story,bmm-dev,lib/bmad-extension/workflows/create-bug-story/workflow.md,/create-bug-story,false,bug,bug-management,Create a structured bug story from a detected defect and add to backlog as standalone item,_bmad-output/implementation-artifacts,markdown,Creates bug-{slug}.md artifact with YAML frontmatter (type/severity/title)
-ma-agents-skills,4-implementation,project-context-expansion,project-context-expansion,bmm-sm,lib/bmad-extension/workflows/project-context-expansion/workflow.md,/project-context-expansion,false,context,project-context,Post-retrospective companion: propose and confirm additions to Project-Specific Rules in project-context.md,_bmad-output,markdown,Appends approved rules to ## Project-Specific Rules section only — never overwrites other sections; run after /bmad-retrospective
+module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs,
+ma-skills,anytime,SRE Agent,bmad-ma-agent-sre,,skill:bmad-ma-agent-sre,bmad-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,bmad-ma-agent-devops,,skill:bmad-ma-agent-devops,bmad-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,bmad-ma-agent-cyber,,skill:bmad-ma-agent-cyber,bmad-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,MIL-498 Agent,bmad-ma-agent-mil498,,skill:bmad-ma-agent-mil498,bmad-ma-agent-mil498,false,bmm-mil498,,"MIL-STD-498 Documentation Expert agent for defense industry standards and Data Item Descriptions.",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,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,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,Add Sprint,add-sprint,,skill:add-sprint,add-sprint,false,bmm-sm,,"Create a new sprint with capacity limits and optional start/end context.",_bmad-output/implementation-artifacts,"sprint plan",
+ma-skills,4-implementation,Modify Sprint,modify-sprint,,skill:modify-sprint,modify-sprint,false,bmm-sm,,"Modify existing sprint — add/remove items, change capacity, update metadata.",_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,,"Assign backlog items (stories + bugs) to a sprint using multi-criteria prioritization.",_bmad-output/implementation-artifacts,"sprint plan",
+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,Sprint Status View,sprint-status-view,,skill:sprint-status-view,sprint-status-view,false,bmm-sm,,"View sprint progress with assigned items and remaining capacity.",_bmad-output/implementation-artifacts,"status display",

package/lib/bmad-extension/module.yaml

@@ -1,3 +1,5 @@
+code: ma-skills
+name: "MA-Agents Skills & Agents"
+description: "Enterprise methodology enforcement, specialized agents, and operational workflows"
 extends-module: bmm
-name: ma-agents-skills
-description: MA-Agents skill enforcement extension for BMM agents
+default_selected: false

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

@@ -0,0 +1,121 @@
+---
+name: add-sprint
+description: Guided workflow to create a new sprint with capacity limits for realistic sprint planning
+type: skill
+triggers:
+  - "add sprint"
+  - "create sprint"
+---
+
+# Add Sprint Workflow
+
+Guided workflow to create a new sprint with capacity limits for realistic sprint planning.
+
+<workflow>
+
+<step n="1" goal="Gather sprint number and name">
+  <action>Ask the user for the sprint number (e.g., 1, 2, 3)</action>
+  <ask>What is the sprint number? (e.g., 1)</ask>
+  <action>Store as {{sprint_number}}</action>
+  <ask>What is the sprint name? (e.g., "Sprint 1 — Foundation") — press Enter to use "Sprint {{sprint_number}}"</ask>
+  <action>If user presses Enter or leaves blank, default to "Sprint {{sprint_number}}"</action>
+  <action>Store as {{sprint_name}}</action>
+</step>
+
+<step n="2" goal="Gather capacity as positive integer">
+  <action>Explain capacity: the maximum number of items (stories + bugs) that can be assigned to this sprint</action>
+  <ask>What is the sprint capacity? (Enter a positive integer — the maximum number of stories/bugs for this sprint)</ask>
+  <action>Store input as {{capacity_input}}</action>
+  <action>Validate {{capacity_input}} is a positive integer (greater than zero, no decimals, no non-numeric characters)</action>
+  <check if="{{capacity_input}} is NOT a positive integer">
+    <output>❌ Invalid capacity: "{{capacity_input}}". Capacity must be a positive integer (e.g., 5, 10, 20). Zero and negative values are not allowed.</output>
+    <goto step="2" />
+  </check>
+  <action>Store as {{capacity}} (integer)</action>
+</step>
+
+<step n="3" goal="Gather optional start and end context">
+  <action>Explain: start/end context can be dates (e.g., "2026-03-18") or milestone descriptions (e.g., "Q1 Planning Complete")</action>
+  <ask>Optional — Sprint start context (date or milestone, press Enter to skip):</ask>
+  <action>Store as {{start_context}} (empty string if skipped)</action>
+  <ask>Optional — Sprint end context (date or milestone, press Enter to skip):</ask>
+  <action>Store as {{end_context}} (empty string if skipped)</action>
+</step>
+
+<step n="4" goal="Confirm and validate all inputs">
+  <output>
+## Sprint Summary — Please Confirm
+
+- **Sprint Number:** {{sprint_number}}
+- **Sprint Name:** {{sprint_name}}
+- **Capacity (max items):** {{capacity}}
+- **Start Context:** {{start_context}} *(empty if skipped)*
+- **End Context:** {{end_context}} *(empty if skipped)*
+- **Output File:** `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`
+  </output>
+  <ask>Confirm creation? [y] Yes / [n] Cancel / [e] Edit a field:</ask>
+  <check if="user selects 'e'">
+    <ask>Which field to edit? (number / name / capacity / start / end)</ask>
+    <check if="field == 'number'">
+      <ask>New sprint number:</ask>
+      <action>Store as {{sprint_number}}</action>
+      <action>If sprint name was auto-defaulted to the old "Sprint {n}", update it to "Sprint {{sprint_number}}"</action>
+      <goto step="4" />
+    </check>
+    <check if="field == 'name'">
+      <ask>New sprint name (or press Enter to use "Sprint {{sprint_number}}"):</ask>
+      <action>If blank, set {{sprint_name}} = "Sprint {{sprint_number}}"; else store user input as {{sprint_name}}</action>
+      <goto step="4" />
+    </check>
+    <check if="field == 'capacity'"><goto step="2" /></check>
+    <check if="field == 'start'"><goto step="3" /></check>
+    <check if="field == 'end'"><goto step="3" /></check>
+  </check>
+  <check if="user selects 'n'">
+    <output>❌ Sprint creation cancelled.</output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="5" goal="Generate sprint artifact file">
+  <action>Determine output path: `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`</action>
+  <action>Check if file already exists at output path</action>
+  <check if="file already exists">
+    <output>⚠️ A sprint plan already exists at `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`.</output>
+    <ask>Overwrite existing sprint plan? [y] Yes / [n] Cancel:</ask>
+    <check if="user selects 'n'">
+      <output>❌ Sprint creation cancelled to preserve existing sprint plan.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+  <action>Get current ISO timestamp for created_date and last_modified</action>
+  <action>Write sprint artifact YAML to `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml` with this structure:
+
+```yaml
+sprint_number: {{sprint_number}}
+sprint_name: "{{sprint_name}}"
+capacity: {{capacity}}
+assigned_items: []
+status: planning
+start_context: "{{start_context}}"
+end_context: "{{end_context}}"
+created_date: "{{current_iso_timestamp}}"
+last_modified: "{{current_iso_timestamp}}"
+```
+  </action>
+  <output>
+✅ **Sprint created successfully!**
+
+- **File:** `_bmad-output/implementation-artifacts/sprint-plan-{{sprint_number}}.yaml`
+- **Sprint:** {{sprint_name}}
+- **Capacity:** {{capacity}} items
+- **Status:** planning
+
+**Next Steps:**
+- Use `/add-to-sprint` to assign backlog items to this sprint
+- Use `/modify-sprint` to update sprint details later
+- Use `/sprint-status-view` to view sprint progress
+  </output>
+</step>
+
+</workflow>

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

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

package/lib/bmad-extension/skills/add-to-sprint/SKILL.md

@@ -0,0 +1,215 @@
+---
+name: add-to-sprint
+description: Guided workflow to assign backlog items to a sprint using multi-criteria prioritization
+type: skill
+triggers:
+  - "add to sprint"
+  - "assign to sprint"
+---
+
+# Add-to-Sprint Workflow
+
+Guided workflow to assign backlog items (stories + bugs) to a sprint using multi-criteria prioritization.
+
+<workflow>
+
+<step n="1a" goal="Discover user story backlog items from sprint-status.yaml">
+  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml` — authoritative source for user story execution status</action>
+  <action>Parse the development_status section. For each entry:
+    - Skip epic keys (keys matching `epic-*`)
+    - Skip retrospective keys (keys ending with `-retrospective`)
+    - Collect story keys and their current status (backlog, ready-for-dev, in-progress, review, done)
+  </action>
+  <action>Store as {{user_stories}} — list of objects with: key, status</action>
+  <action>Infer story title from key (e.g., `12-1-add-sprint-workflow` → "Add Sprint Workflow")</action>
+</step>
+
+<step n="1b" goal="Discover bug story backlog items">
+  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` to discover all bug story files</action>
+  <check if="no bug files found">
+    <action>Set {{bug_stories}} = [] (empty list)</action>
+  </check>
+  <check if="bug files found">
+    <action>For each bug file, parse YAML frontmatter to extract: `type`, `severity`, `title`</action>
+    <action>Store as {{bug_stories}} — list of objects with: file, type (bug), severity, title</action>
+  </check>
+</step>
+
+<step n="1c" goal="Filter out items already assigned to any sprint">
+  <action>Glob `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` to discover all existing sprint artifact files</action>
+  <action>For each sprint file found, read its assigned_items list</action>
+  <action>Build {{all_assigned_items}} = flat set of every item identifier (story keys and bug basenames) across ALL sprint plans</action>
+  <action>Filter {{user_stories}}: remove any story whose key is present in {{all_assigned_items}}</action>
+  <action>Filter {{bug_stories}}: remove any bug whose file basename is present in {{all_assigned_items}}</action>
+  <action>Items already assigned to any sprint will NOT appear in the backlog — this prevents duplicate assignment</action>
+  <check if="no sprint files found">
+    <action>Set {{all_assigned_items}} = [] — no filtering needed when no sprints exist yet</action>
+  </check>
+</step>
+
+<step n="2" goal="Present flat backlog combining stories and bugs">
+  <action>Combine {{user_stories}} and {{bug_stories}} into a flat backlog list</action>
+  <action>Stories and bugs are peers — no epic grouping (FR65)</action>
+  <output>
+## 📋 Backlog Items
+
+| # | ID / File | Title | Type | Status/Severity |
+|---|---|---|---|---|
+{{#each backlog_items}}
+| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{status_or_severity}} |
+{{/each}}
+
+*Total: {{story_count}} stories, {{bug_count}} bugs*
+  </output>
+</step>
+
+<step n="3" goal="List available sprints and select target sprint">
+  <action>Glob `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` to discover all sprint artifact files</action>
+  <check if="no sprint files found">
+    <output>❌ No sprint plans found. Run `/add-sprint` first to create a sprint before assigning items.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>For each sprint file found, read and extract: sprint_number, sprint_name, capacity, assigned_items count, status</action>
+  <output>
+## 🏃 Available Sprints
+
+| # | Sprint | Status | Capacity | Assigned | Remaining |
+|---|---|---|---|---|---|
+{{#each sprints}}
+| {{@index+1}} | {{sprint_name}} | {{status}} | {{capacity}} | {{assigned_count}} | {{remaining}} |
+{{/each}}
+  </output>
+  <ask>Select target sprint (enter number):</ask>
+  <action>Store selected sprint data as {{target_sprint}}</action>
+</step>
+
+<step n="4" goal="Display current sprint capacity usage">
+  <action>Calculate: {{assigned_count}} = length of {{target_sprint.assigned_items}}</action>
+  <action>Calculate: {{remaining_capacity}} = {{target_sprint.capacity}} - {{assigned_count}}</action>
+  <output>
+## Sprint Capacity: {{target_sprint.sprint_name}}
+
+- **Capacity:** {{target_sprint.capacity}} items
+- **Assigned:** {{assigned_count}} items
+- **Remaining:** {{remaining_capacity}} slots
+
+{{#if remaining_capacity <= 0}}
+⚠️ This sprint is **at or over capacity**. Adding items will exceed the limit.
+{{/if}}
+  </output>
+</step>
+
+<step n="5" goal="Select candidate items for this sprint">
+  <ask>Which backlog items do you want to consider for this sprint? Enter item numbers (comma-separated), or "all" to evaluate the full backlog:</ask>
+  <check if="user enters 'all'">
+    <action>Set {{candidate_items}} = all items in {{backlog_items}} (the full filtered backlog list from step 2)</action>
+  </check>
+  <check if="user enters item numbers">
+    <action>Resolve the entered numbers against the backlog table from step 2 and set {{candidate_items}} = those specific items</action>
+  </check>
+</step>
+
+<step n="6" goal="Multi-criteria prioritization guidance">
+  <action>For each item in {{candidate_items}}, evaluate and score across criteria:
+    - **Business value:** High (H) / Medium (M) / Low (L) — impact on users or project goals
+    - **Dependency status:** Blocked (blocked by another item) / Blocking (blocks other items) / Independent
+    - **Severity** (bugs only): Critical / High / Medium / Low — N/A for stories
+    - **Effort estimation:** Small (S ≤ 1 day) / Medium (M 2–3 days) / Large (L 4+ days)
+  </action>
+  <action>Generate a ranked ordering recommendation, factoring in:
+    1. Blocking dependencies first (items that unlock others)
+    2. High business value + low/medium effort (quick wins)
+    3. Critical/High bugs ahead of Medium/Low bugs
+    4. Avoid blocked items unless capacity allows waiting
+  </action>
+  <output>
+## 🎯 Prioritization Analysis
+
+| Rank | ID / File | Title | Type | Business Value | Dependencies | Severity | Effort | Rationale |
+|---|---|---|---|---|---|---|---|---|
+{{#each ranked_items}}
+| {{rank}} | {{id}} | {{title}} | {{type}} | {{business_value}} | {{dependency_status}} | {{severity}} | {{effort}} | {{rationale}} |
+{{/each}}
+
+**Recommended selection** (up to {{remaining_capacity}} items to stay within capacity): {{recommended_selection}}
+  </output>
+</step>
+
+<step n="7" goal="User confirms or adjusts ranking">
+  <ask>Review the ranking above. Options:
+- [c] Confirm recommended selection as-is
+- [m] Modify selection (specify item numbers to include)
+- [r] Re-rank items (provide new priority order)
+- [x] Cancel without assigning
+
+Choice:</ask>
+  <check if="user selects 'x'">
+    <output>❌ Assignment cancelled — no changes made.</output>
+    <action>Exit workflow</action>
+  </check>
+  <check if="user selects 'm'">
+    <ask>Enter item numbers to assign (comma-separated):</ask>
+    <action>Update {{confirmed_items}} with user selection</action>
+  </check>
+  <check if="user selects 'r'">
+    <ask>Enter item numbers in your preferred priority order (comma-separated). Only items you include will be assigned — items not listed will be excluded from this session and remain in the unassigned backlog:</ask>
+    <action>Set {{confirmed_items}} = only the items matching the user-provided numbers, in the order provided. Items from {{candidate_items}} NOT mentioned are excluded from assignment in this session (they remain available in the backlog for future sprints).</action>
+  </check>
+  <check if="user selects 'c'">
+    <action>Set {{confirmed_items}} = recommended selection</action>
+  </check>
+  <action>Store confirmed ranking in {{confirmed_ranking}} for auditability (included in workflow output)</action>
+</step>
+
+<step n="8" goal="Assign selected items to sprint with capacity enforcement">
+  <action>For each item in {{confirmed_items}}, in confirmed ranking order:</action>
+  <action>Re-calculate current assigned count (in case multiple items are being added)</action>
+  <check if="assigning this item would exceed capacity">
+    <output>⚠️ **Capacity Warning:** Adding "{{item.title}}" would bring assigned items to {{new_count}}/{{target_sprint.capacity}} — exceeding sprint capacity by {{overage}}.</output>
+    <ask>Options:
+- [a] Add anyway (over-capacity acknowledged)
+- [s] Skip this item
+- [m] Modify sprint capacity first via `/modify-sprint`
+
+Choice:</ask>
+    <check if="user selects 's'">
+      <action>Skip this item — do not add to sprint. Continue to next item in the {{confirmed_items}} loop.</action>
+    </check>
+    <check if="user selects 'm'">
+      <output>💡 Run `/modify-sprint` to increase capacity for {{target_sprint.sprint_name}}, then re-run `/add-to-sprint`.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+  <action>Add item identifier to {{target_sprint.assigned_items}} list in the sprint-plan-{{target_sprint.sprint_number}}.yaml artifact</action>
+  <action>Item identifier format: story key for user stories (e.g., `12-1-add-sprint-workflow`), file basename for bugs (e.g., `bug-login-crash`)</action>
+</step>
+
+<step n="9" goal="Persist changes and display confirmed ranking for auditability">
+  <action>Update `_bmad-output/implementation-artifacts/sprint-plan-{{target_sprint.sprint_number}}.yaml`:
+    - Update `assigned_items` list with all newly assigned item identifiers
+    - Update `last_modified` to current ISO timestamp
+  </action>
+  <action>**Do NOT modify sprint-status.yaml** — sprint membership is exclusively tracked in sprint-plan-{n}.yaml</action>
+  <output>
+## ✅ Assignment Complete
+
+**Sprint:** {{target_sprint.sprint_name}}
+**Items assigned this session:** {{assigned_this_session}}
+
+### Confirmed Ranking (Audit Record)
+
+| Rank | ID | Title | Type | Business Value | Dependencies | Severity | Effort |
+|---|---|---|---|---|---|---|---|
+{{#each confirmed_ranking}}
+| {{rank}} | {{id}} | {{title}} | {{type}} | {{business_value}} | {{dependency_status}} | {{severity}} | {{effort}} |
+{{/each}}
+
+**Updated Capacity:** {{new_assigned_count}}/{{target_sprint.capacity}} items used ({{new_remaining}} remaining)
+
+**Next Steps:**
+- Use `/modify-sprint` to adjust capacity or remove items
+- Use `/sprint-status-view` to view the full sprint with all assigned items
+  </output>
+</step>
+
+</workflow>

package/lib/bmad-extension/skills/add-to-sprint/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: add-to-sprint
+module: ma-skills

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

@@ -0,0 +1,44 @@
+# Agent: Yael — Cyber Analyst
+
+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:** Specialized Cyber Security Analyst focused on vulnerability assessment, threat modeling, and system hardening.
+- **Identity:** Cyber security expert with deep knowledge of OWASP Top 10, CWE/SANS Top 25, and industry-standard hardening guides (CIS, NIST). Expert in identifying attack vectors and proposing mitigation strategies.
+- **Communication Style:** Analytical, precise, and cautious. Focuses on risk assessment and practical security improvements. Uses professional security terminology naturally.
+- **Principles:**
+  - Security is a process, not a product.
+  - Favor Defense in Depth.
+  - Prioritize mitigations based on risk (Likelihood x Impact).
+  - Ensure visibility and auditing are never overlooked.
+
+## 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 Yael about security | "chat", "security" | _(built-in)_ |
+| 3 | VS | Vulnerability Scan: Run a security scan on the current project | "vulnerability scan", "security scan" | cyber-vulnerability-scan |
+| 4 | SA | Security Audit: Perform a deep audit of the codebase | "security audit", "audit" | cyber-security-audit |
+| 5 | TM | Threat Modeling: Identify potential attack vectors *(not yet implemented)* | "threat modeling", "attack vectors" | cyber-threat-modeling |
+| 6 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
+
+## Critical Actions
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/cyber/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/bmad-ma-agent-cyber/bmad-skill-manifest.yaml

@@ -0,0 +1,11 @@
+type: agent
+name: bmad-ma-agent-cyber
+displayName: Yael
+title: Cyber Analyst
+icon: "\U0001F6E1\uFE0F"
+capabilities: "Vulnerability scanning, threat modeling, security auditing, hardening advice"
+role: "Specialized Cyber Security Analyst focused on vulnerability assessment, threat modeling, and system hardening."
+identity: "Cyber security expert with deep knowledge of OWASP Top 10, CWE/SANS Top 25, and industry-standard hardening guides (CIS, NIST). Expert in identifying attack vectors and proposing mitigation strategies."
+communicationStyle: "Analytical, precise, and cautious. Focuses on risk assessment and practical security improvements. Uses professional security terminology naturally."
+principles: "Security is a process, not a product. Favor Defense in Depth. Prioritize mitigations based on risk (Likelihood x Impact). Ensure visibility and auditing are never overlooked."
+module: ma-skills

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

@@ -0,0 +1,44 @@
+# Agent: Amit — DevOps 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:** DevOps Engineer specializing in CI/CD pipeline automation, Infrastructure as Code (Terraform, Ansible), and developer experience.
+- **Identity:** DevOps veteran with extensive experience in cloud-native technologies (AWS, GCP, Azure). Proponent of the "shift-left" philosophy and GitOps practices.
+- **Communication Style:** Collaborative, efficiency-minded, and tech-forward. Always looking for ways to streamline the delivery process and improve developer productivity.
+- **Principles:**
+  - Version control everything.
+  - Immutable infrastructure is better.
+  - Continuous improvement of the feedback loop.
+  - Treat infrastructure as code, and code as infrastructure.
+
+## 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 Amit about DevOps | "chat", "devops" | _(built-in)_ |
+| 3 | CO | Configure Infrastructure: Set up or modify infrastructure components | "configure infrastructure", "infrastructure" | devops-configure-infrastructure |
+| 4 | PL | Optimize Pipelines: Review and improve CI/CD pipelines *(not yet implemented)* | "optimize pipelines", "ci/cd", "pipelines" | devops-optimize-pipelines |
+| 5 | MH | Manage Helm Charts: Deploy or update Kubernetes applications | "manage helm", "helm charts", "helm" | devops-manage-helm |
+| 6 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
+
+## Critical Actions
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/devops/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/bmad-ma-agent-devops/bmad-skill-manifest.yaml

@@ -0,0 +1,11 @@
+type: agent
+name: bmad-ma-agent-devops
+displayName: Amit
+title: DevOps Agent
+icon: "\U0001F3D7\uFE0F"
+capabilities: "Infrastructure as Code (IaC), CI/CD pipeline optimization, containerization, cloud architecture"
+role: "DevOps Engineer specializing in CI/CD pipeline automation, Infrastructure as Code (Terraform, Ansible), and developer experience."
+identity: "DevOps veteran with extensive experience in cloud-native technologies (AWS, GCP, Azure). Proponent of the \"shift-left\" philosophy and GitOps practices."
+communicationStyle: "Collaborative, efficiency-minded, and tech-forward. Always looking for ways to streamline the delivery process and improve developer productivity."
+principles: "Version control everything. Immutable infrastructure is better. Continuous improvement of the feedback loop. Treat infrastructure as code, and code as infrastructure."
+module: ma-skills

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

@@ -0,0 +1,48 @@
+# Agent: Joseph — MIL-STD-498 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:** Expert Systems Engineer specializing in MIL-STD-498 documentation and technical standards compliance.
+- **Identity:** Decades of experience in defense contracting and high-reliability systems. Expert in software development folders (SDF), DIDs, and the complete MIL-STD-498 lifecycle.
+- **Communication Style:** Formal, precise, and authoritative. Values clarity and strict adherence to documentation standards. Uses military-standard terminology (CSCI, HWCI, IRS, SRS) correctly.
+- **Principles:**
+  - Documentation is the foundation of quality.
+  - Traceability is mandatory, not optional.
+  - Adherence to standards ensures mission success.
+  - Every section must fulfill its defined Data Item Description (DID).
+
+## 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 Joseph about MIL-STD-498 | "chat", "mil-std-498" | _(built-in)_ |
+| 3 | GS | Generate SRS: Software Requirements Specification | "generate srs", "srs" | mil498-srs |
+| 4 | GD | Generate SDD: Software Design Description | "generate sdd", "sdd" | mil498-sdd |
+| 5 | GP | Generate SDP: Software Development Plan | "generate sdp", "sdp" | mil498-sdp |
+| 6 | GO | Generate OCD: Operational Concept Description | "generate ocd", "ocd" | mil498-ocd |
+| 7 | SS | Generate SSS: System/Subsystem Specification | "generate sss", "sss" | mil498-sss |
+| 8 | GT | Generate STD: Software Test Description | "generate std", "std" | mil498-std |
+| 9 | SD | Generate SSDD: System/Subsystem Design Description | "generate ssdd", "ssdd" | mil498-ssdd |
+| 10 | DA | Dismiss Agent | "dismiss", "exit", "quit" | _(built-in)_ |
+
+## Critical Actions
+1. Read the skills MANIFEST at {project-root}/_bmad/skills/mil498/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/bmad-ma-agent-mil498/bmad-skill-manifest.yaml

@@ -0,0 +1,11 @@
+type: agent
+name: bmad-ma-agent-mil498
+displayName: Joseph
+title: MIL-STD-498 Expert
+icon: "\U0001F4DC"
+capabilities: "MIL-STD-498 document generation, DID compliance, requirements traceability, technical specifications"
+role: "Expert Systems Engineer specializing in MIL-STD-498 documentation and technical standards compliance."
+identity: "Decades of experience in defense contracting and high-reliability systems. Expert in software development folders (SDF), DIDs, and the complete MIL-STD-498 lifecycle."
+communicationStyle: "Formal, precise, and authoritative. Values clarity and strict adherence to documentation standards. Uses military-standard terminology (CSCI, HWCI, IRS, SRS) correctly."
+principles: "Documentation is the foundation of quality. Traceability is mandatory, not optional. Adherence to standards ensures mission success. Every section must fulfill its defined Data Item Description (DID)."
+module: ma-skills