ma-agents 3.4.7 → 3.4.9

package/.opencode/skills/bmad-validate-prd/steps-v/step-v-13-report-complete.md

@@ -0,0 +1,229 @@
+---
+# File references (ONLY variables used in this step)
+validationReportPath: '{validation_report_path}'
+prdFile: '{prd_file_path}'
+---
+
+# Step 13: Validation Report Complete
+
+## STEP GOAL:
+
+Finalize validation report, summarize all findings from steps 1-12, present summary to user conversationally, and offer actionable next steps.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a Validation Architect and Quality Assurance Specialist
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring synthesis and summary expertise
+- ✅ This is the FINAL step - requires user interaction
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on summarizing findings and presenting options
+- 🚫 FORBIDDEN to perform additional validation
+- 💬 Approach: Conversational summary with clear next steps
+- 🚪 This is the final step - no next step after this
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load complete validation report
+- 🎯 Summarize all findings from steps 1-12
+- 🎯 Update report frontmatter with final status
+- 💬 Present summary to user conversationally
+- 💬 Offer menu options for next actions
+- 🚫 FORBIDDEN to proceed without user selection
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Complete validation report with findings from all validation steps
+- Focus: Summary and presentation only (no new validation)
+- Limits: Don't add new findings, just synthesize existing
+- Dependencies: Steps 1-12 completed - all validation checks done
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
+
+### 1. Load Complete Validation Report
+
+Read the entire validation report from {validationReportPath}
+
+Extract all findings from:
+- Format Detection (Step 2)
+- Parity Analysis (Step 2B, if applicable)
+- Information Density (Step 3)
+- Product Brief Coverage (Step 4)
+- Measurability (Step 5)
+- Traceability (Step 6)
+- Implementation Leakage (Step 7)
+- Domain Compliance (Step 8)
+- Project-Type Compliance (Step 9)
+- SMART Requirements (Step 10)
+- Holistic Quality (Step 11)
+- Completeness (Step 12)
+
+### 2. Update Report Frontmatter with Final Status
+
+Update validation report frontmatter:
+
+```yaml
+---
+validationTarget: '{prd_path}'
+validationDate: '{current_date}'
+inputDocuments: [list of documents]
+validationStepsCompleted: ['step-v-01-discovery', 'step-v-02-format-detection', 'step-v-03-density-validation', 'step-v-04-brief-coverage-validation', 'step-v-05-measurability-validation', 'step-v-06-traceability-validation', 'step-v-07-implementation-leakage-validation', 'step-v-08-domain-compliance-validation', 'step-v-09-project-type-validation', 'step-v-10-smart-validation', 'step-v-11-holistic-quality-validation', 'step-v-12-completeness-validation']
+validationStatus: COMPLETE
+holisticQualityRating: '{rating from step 11}'
+overallStatus: '{Pass/Warning/Critical based on all findings}'
+---
+```
+
+### 3. Create Summary of Findings
+
+**Overall Status:**
+- Determine from all validation findings
+- **Pass:** All critical checks pass, minor warnings acceptable
+- **Warning:** Some issues found but PRD is usable
+- **Critical:** Major issues that prevent PRD from being fit for purpose
+
+**Quick Results Table:**
+- Format: [classification]
+- Information Density: [severity]
+- Measurability: [severity]
+- Traceability: [severity]
+- Implementation Leakage: [severity]
+- Domain Compliance: [status]
+- Project-Type Compliance: [compliance score]
+- SMART Quality: [percentage]
+- Holistic Quality: [rating/5]
+- Completeness: [percentage]
+
+**Critical Issues:** List from all validation steps
+**Warnings:** List from all validation steps
+**Strengths:** List positives from all validation steps
+
+**Holistic Quality Rating:** From step 11
+**Top 3 Improvements:** From step 11
+
+**Recommendation:** Based on overall status
+
+### 4. Present Summary to User Conversationally
+
+Display:
+
+"**✓ PRD Validation Complete**
+
+**Overall Status:** {Pass/Warning/Critical}
+
+**Quick Results:**
+{Present quick results table with key findings}
+
+**Critical Issues:** {count or "None"}
+{If any, list briefly}
+
+**Warnings:** {count or "None"}
+{If any, list briefly}
+
+**Strengths:**
+{List key strengths}
+
+**Holistic Quality:** {rating}/5 - {label}
+
+**Top 3 Improvements:**
+1. {Improvement 1}
+2. {Improvement 2}
+3. {Improvement 3}
+
+**Recommendation:**
+{Based on overall status:
+- Pass: "PRD is in good shape. Address minor improvements to make it great."
+- Warning: "PRD is usable but has issues that should be addressed. Review warnings and improve where needed."
+- Critical: "PRD has significant issues that should be fixed before use. Focus on critical issues above."}
+
+**What would you like to do next?**"
+
+### 5. Present MENU OPTIONS
+
+Display:
+
+**[R] Review Detailed Findings** - Walk through validation report section by section
+**[E] Use Edit Workflow** - Use validation report with Edit workflow for systematic improvements
+**[F] Fix Simpler Items** - Immediate fixes for simple issues (anti-patterns, leakage, missing headers)
+**[X] Exit** - Exit and Suggest Next Steps.
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- Only proceed based on user selection
+
+#### Menu Handling Logic:
+
+- **IF R (Review Detailed Findings):**
+  - Walk through validation report section by section
+  - Present findings from each validation step
+  - Allow user to ask questions
+  - After review, return to menu
+
+- **IF E (Use Edit Workflow):**
+  - Explain: "The Edit workflow can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
+  - Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
+  - If yes: Invoke the `bmad-edit-prd` skill, passing the validation report path as context
+  - If no: Return to menu
+
+- **IF F (Fix Simpler Items):**
+  - Offer immediate fixes for:
+    - Template variables (fill in with appropriate content)
+    - Conversational filler (remove wordy phrases)
+    - Implementation leakage (remove technology names from FRs/NFRs)
+    - Missing section headers (add ## headers)
+  - Ask: "Which simple fixes would you like me to make?"
+  - If user specifies fixes, make them and update validation report
+  - Return to menu
+
+- **IF X (Exit):**
+  - Display: "**Validation Report Saved:** {validationReportPath}"
+  - Display: "**Summary:** {overall status} - {recommendation}"
+  - PRD Validation complete. Invoke the `bmad-help` skill.
+
+- **IF Any other:** Help user, then redisplay menu
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Complete validation report loaded successfully
+- All findings from steps 1-12 summarized
+- Report frontmatter updated with final status
+- Overall status determined correctly (Pass/Warning/Critical)
+- Quick results table presented
+- Critical issues, warnings, and strengths listed
+- Holistic quality rating included
+- Top 3 improvements presented
+- Clear recommendation provided
+- Menu options presented with clear explanations
+- User can review findings, get help, or exit
+
+### ❌ SYSTEM FAILURE:
+
+- Not loading complete validation report
+- Missing summary of findings
+- Not updating report frontmatter
+- Not determining overall status
+- Missing menu options
+- Unclear next steps
+
+**Master Rule:** User needs clear summary and actionable next steps. Edit workflow is best for complex issues; immediate fixes available for simpler ones.

package/.opencode/skills/bmad-validate-prd/workflow.md

@@ -0,0 +1,62 @@
+---
+main_config: '{project-root}/_bmad/bmm/config.yaml'
+validateWorkflow: './steps-v/step-v-01-discovery.md'
+---
+
+# PRD Validate Workflow
+
+**Goal:** Validate existing PRDs against BMAD standards through comprehensive review.
+
+**Your Role:** Validation Architect and Quality Assurance Specialist.
+
+You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {main_config} and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+
+✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
+
+### 2. Route to Validate Workflow
+
+"**Validate Mode: Validating an existing PRD against BMAD standards.**"
+
+Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)

package/.opencode/skills/create-bug-story/SKILL.md

@@ -0,0 +1,263 @@
+---
+name: create-bug-story
+description: Guided workflow to create a structured bug story from a detected defect
+type: skill
+triggers:
+  - "create bug story"
+  - "report bug"
+---
+
+# Create Bug Story Workflow
+
+Guided workflow to create a structured bug story from a detected defect and add it to the backlog as a standalone item.
+
+<workflow>
+
+<step n="1" goal="Gather bug title and severity">
+  <action>Explain: This workflow creates a structured bug story file that enters the backlog alongside user stories.</action>
+  <ask>What is the bug title? (short, descriptive — e.g., "Login fails with empty password field")</ask>
+  <action>Store as {{bug_title}}</action>
+  <action>Validate {{bug_title}} is not empty</action>
+  <check if="{{bug_title}} is empty">
+    <output>❌ Bug title cannot be empty.</output>
+    <goto step="1" />
+  </check>
+
+  <output>
+**Severity levels:**
+- `critical` — Data loss, security breach, or system crash in normal usage
+- `high` — Core feature broken or serious security risk; blocks users
+- `medium` — Feature partially broken or degraded; workaround exists
+- `low` — Minor issue, cosmetic defect, or edge case with minimal user impact
+  </output>
+  <ask>What is the severity? [critical / high / medium / low]</ask>
+  <action>Store as {{severity}}</action>
+  <action>Normalize to lowercase</action>
+  <check if="{{severity}} is not one of: critical, high, medium, low">
+    <output>❌ Severity must be one of: critical, high, medium, low.</output>
+    <goto step="1" />
+  </check>
+</step>
+
+<step n="2" goal="Gather affected component and reproduction steps">
+  <ask>What is the affected component? (e.g., "auth module", "login page", "installer pipeline")</ask>
+  <action>Store as {{affected_component}}</action>
+
+  <ask>What are the reproduction steps? (numbered steps to reproduce the bug — describe them one at a time or as a list)</ask>
+  <action>Store as {{reproduction_steps}}</action>
+</step>
+
+<step n="3" goal="Gather expected vs actual behavior">
+  <ask>What is the expected behavior? (what should happen when working correctly)</ask>
+  <action>Store as {{expected_behavior}}</action>
+
+  <ask>What is the actual behavior? (what actually happens — the defect)</ask>
+  <action>Store as {{actual_behavior}}</action>
+</step>
+
+<step n="4" goal="Gather version and bug type">
+  <ask>What version was this bug found in? (optional — press Enter to skip; e.g., "2.3.1", "v1.0.0-rc2")</ask>
+  <action>Store as {{version_found}} (empty string if skipped)</action>
+
+  <output>
+**Bug type classifications:**
+- `regression` — Previously working feature now broken
+- `functional` — Feature does not work as specified
+- `performance` — Unacceptable latency, throughput, or resource usage
+- `security` — Vulnerability or authentication/authorization flaw
+- `ui` — Visual or interaction defect
+- `data` — Data corruption, loss, or incorrect transformation
+- `integration` — Failure at system/service boundaries
+- `other` — Does not fit the above categories
+  </output>
+  <ask>What is the bug type? [regression / functional / performance / security / ui / data / integration / other] (default: functional)</ask>
+  <action>Store as {{bug_type}}</action>
+  <action>If empty or blank, default to "functional"</action>
+  <action>Normalize to lowercase</action>
+  <check if="{{bug_type}} is not one of: regression, functional, performance, security, ui, data, integration, other">
+    <output>❌ Bug type must be one of: regression, functional, performance, security, ui, data, integration, other.</output>
+    <goto step="4" />
+  </check>
+</step>
+
+<step n="5" goal="Gather root cause hypothesis and affected files">
+  <ask>What is your root cause hypothesis? (optional — press Enter to skip; e.g., "Null check missing in validateUser()")</ask>
+  <action>Store as {{root_cause}} (empty string if skipped)</action>
+
+  <ask>What files are affected? (optional — comma-separated paths relative to repo root, press Enter to skip)</ask>
+  <action>Store as {{affected_files}} (empty string if skipped)</action>
+  <action>If provided, split by comma and trim whitespace to form a list of file paths</action>
+
+  <ask>Is there a suggested fix? (optional — brief description or press Enter to skip)</ask>
+  <action>Store as {{suggested_fix}} (empty string if skipped)</action>
+</step>
+
+<step n="6" goal="Confirm all bug details before writing">
+  <action>Derive {{title_slug}} by converting {{bug_title}} to lowercase kebab-case:
+    - Convert to lowercase
+    - Replace spaces and underscores with hyphens
+    - Remove characters that are not alphanumeric or hyphens
+    - Collapse consecutive hyphens into one
+    - Trim leading/trailing hyphens
+  </action>
+  <action>Set {{output_file}} = `_bmad-output/implementation-artifacts/bug-{{title_slug}}.md`</action>
+
+  <output>
+## Bug Story Summary — Please Confirm
+
+- **Title:** {{bug_title}}
+- **Severity:** {{severity}}
+- **Bug Type:** {{bug_type}}
+- **Version Found:** {{version_found}} *(empty if skipped)*
+- **Affected Component:** {{affected_component}}
+- **Reproduction Steps:** {{reproduction_steps}}
+- **Expected Behavior:** {{expected_behavior}}
+- **Actual Behavior:** {{actual_behavior}}
+- **Root Cause Hypothesis:** {{root_cause}} *(empty if skipped)*
+- **Affected Files:** {{affected_files}} *(empty if skipped)*
+- **Suggested Fix:** {{suggested_fix}} *(empty if skipped)*
+- **Output File:** `{{output_file}}`
+  </output>
+  <ask>Confirm creation? [y] Yes / [n] Cancel / [e] Edit a field:</ask>
+  <check if="user selects 'e'">
+    <ask>Which field to edit? (title / severity / component / steps / expected / actual / version / bug-type / root-cause / files / fix)</ask>
+    <check if="field == 'title' OR field == 'severity'"><goto step="1" /></check>
+    <check if="field == 'component' OR field == 'steps'"><goto step="2" /></check>
+    <check if="field == 'expected' OR field == 'actual'"><goto step="3" /></check>
+    <check if="field == 'version' OR field == 'bug-type'"><goto step="4" /></check>
+    <check if="field == 'root-cause' OR field == 'files' OR field == 'fix'"><goto step="5" /></check>
+    <check if="none of the above matched">
+      <output>❌ Unrecognized field. Valid options: title / severity / component / steps / expected / actual / version / bug-type / root-cause / files / fix</output>
+      <goto step="6" />
+    </check>
+  </check>
+  <check if="user selects 'n'">
+    <output>❌ Bug story creation cancelled.</output>
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<step n="7" goal="Write bug story file">
+  <action>Check if {{output_file}} already exists</action>
+  <check if="file already exists">
+    <output>⚠️ A bug story already exists at `{{output_file}}`.</output>
+    <ask>Overwrite? [y] Yes — overwrite existing / [n] Cancel / [s] Save with unique suffix (e.g. bug-{{title_slug}}-2.md):</ask>
+    <check if="user selects 's'">
+      <action>Find the next available suffix: try bug-{{title_slug}}-2.md, -3.md, etc. until a filename that does not exist is found. Set {{output_file}} to that path.</action>
+    </check>
+    <check if="user selects 'n'">
+      <output>❌ Bug story creation cancelled to preserve existing file.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <action>Write bug story to {{output_file}} using the template below.
+    CRITICAL: The YAML frontmatter block MUST be the very first content in the file — no blank lines, no title, nothing before the opening `---`.
+    Format optional fields (root_cause, affected_files, suggested_fix) as follows:
+      - If {{root_cause}} is empty, write: `_Not identified_`
+      - If {{affected_files}} is empty, write: `_Unknown_`; otherwise list each file as a `- path/to/file` bullet
+      - If {{suggested_fix}} is empty, omit the Suggested Fix section entirely
+  </action>
+
+  <action>Write file with this exact structure:
+
+```
+---
+type: bug
+status: backlog
+severity: {{severity}}
+bug_type: {{bug_type}}
+version_found: {{version_found}}
+title: {{bug_title}}
+---
+
+# Bug: {{bug_title}}
+
+**Severity:** {{severity}}
+**Affected Component:** {{affected_component}}
+
+## Reproduction Steps
+
+{{reproduction_steps}}
+
+## Expected Behavior
+
+{{expected_behavior}}
+
+## Actual Behavior
+
+{{actual_behavior}}
+
+## Root Cause Hypothesis
+
+{{root_cause or "_Not identified_"}}
+
+## Affected Files
+
+{{affected_files list or "_Unknown_"}}
+
+## Suggested Fix
+
+{{suggested_fix — omit section if empty}}
+
+## Notes
+
+- Created via `create-bug-story` workflow
+- Discoverable by sprint workflows via glob: `_bmad-output/implementation-artifacts/bug-*.md`
+- To add to a sprint, run `/add-to-sprint`
+```
+  </action>
+
+  <output>
+✅ **Bug story created successfully!**
+
+- **File:** `{{output_file}}`
+- **Title:** {{bug_title}}
+- **Severity:** {{severity}}
+- **Bug Type:** {{bug_type}}
+- **Component:** {{affected_component}}
+  </output>
+</step>
+
+<step n="8" goal="Add bug entry to backlog.yaml">
+  <action>Check if `_bmad-output/implementation-artifacts/backlog.yaml` exists</action>
+
+  <check if="backlog.yaml exists">
+    <action>Read `_bmad-output/implementation-artifacts/backlog.yaml`</action>
+    <action>Determine the next priority number by finding the highest existing priority value and adding 1</action>
+    <action>Append a new entry at the end of the backlog items list with the following format:
+```yaml
+- id: "BUG-{{title_slug}}"
+  type: bug
+  epic: null
+  title: "{{bug_title}}"
+  priority: N
+  status: backlog
+  sprint: null
+  severity: {{severity}}
+```
+    Where N is the next priority number.
+    </action>
+    <action>Re-number all priorities sequentially (1, 2, 3, ...) from top to bottom to ensure no gaps</action>
+    <action>Write the updated backlog.yaml back to disk</action>
+    <output>
+📋 **Backlog updated!** Added `BUG-{{title_slug}}` to `_bmad-output/implementation-artifacts/backlog.yaml` with priority {{N}}.
+    </output>
+  </check>
+
+  <check if="backlog.yaml does not exist">
+    <output>
+ℹ️ No `backlog.yaml` found at `_bmad-output/implementation-artifacts/backlog.yaml`.
+Run `/generate-backlog` to create a backlog that will include this bug story.
+    </output>
+  </check>
+
+  <output>
+**Next Steps:**
+- Use `/add-to-sprint` to assign this bug to the current sprint
+- Use `/sprint-status-view` to see all sprint items including this bug
+- To detect more bugs, ensure the `auto-bug-detection` skill is loaded in your session
+  </output>
+</step>
+
+</workflow>

package/.opencode/skills/create-bug-story/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: create-bug-story
+module: ma-skills

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

@@ -0,0 +1,27 @@
+---
+name: cyber-generate-certs
+description: Generate self-signed certificates using the self-signed-cert skill
+type: skill
+triggers:
+  - "generate certs"
+  - "generate certificates"
+---
+
+# workflow-generate-certs.md
+# Secure Certificate Generation Workflow
+
+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/.opencode/skills/cyber-generate-certs/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: cyber-generate-certs
+module: ma-skills

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

@@ -0,0 +1,29 @@
+---
+name: cyber-immunity-estimation
+description: Assess overall security posture and immunity against common attack vectors
+type: skill
+triggers:
+  - "immunity estimation"
+  - "security posture"
+---
+
+# workflow-immunity-estimation.md
+# Cyber Immunity Estimation Workflow
+
+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/.opencode/skills/cyber-immunity-estimation/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: cyber-immunity-estimation
+module: ma-skills

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

@@ -0,0 +1,27 @@
+---
+name: cyber-security-audit
+description: Comprehensive security audit of infrastructure and application configuration
+type: skill
+triggers:
+  - "security audit"
+  - "run security audit"
+---
+
+# workflow-security-audit.md
+# Comprehensive Security Audit Workflow
+
+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/.opencode/skills/cyber-security-audit/bmad-skill-manifest.yaml

@@ -0,0 +1,3 @@
+type: skill
+name: cyber-security-audit
+module: ma-skills