ma-agents 3.4.9 → 3.5.1

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

@@ -1,229 +0,0 @@
----
-# 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

@@ -1,62 +0,0 @@
----
-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/cleanup-done/SKILL.md

@@ -1,159 +0,0 @@
----
-name: cleanup-done
-description: Archive done stories and bugs — move files to done/ subfolder and remove from sprint/backlog
-type: skill
-triggers:
-  - "cleanup done"
-  - "archive done items"
----
-
-# Cleanup-Done Workflow
-
-Archive done stories and bugs — move files to the `done/` subfolder and remove from sprint/backlog tracking.
-
-<workflow>
-
-<step n="1" goal="Identify all done items across data sources">
-  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml` — collect all story keys where status is `done`</action>
-  <action>Read `_bmad-output/implementation-artifacts/backlog.yaml` — collect all items where status is `done`</action>
-  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` — for each bug file, parse YAML frontmatter and collect those with `status: done`</action>
-  <action>Deduplicate across all three sources — build {{done_items}} as a unified list with: id, title, type (story/bug), source_file</action>
-  <check if="no done items found">
-    <output>No items with status `done` found across sprint-status.yaml, backlog.yaml, or bug files. Nothing to archive.</output>
-    <action>Exit workflow</action>
-  </check>
-</step>
-
-<step n="2" goal="Display done items and confirm archival scope">
-  <output>
-## Done Items Ready for Archival
-
-| # | ID | Title | Type | Source |
-|---|---|---|---|---|
-{{#each done_items}}
-| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{source}} |
-{{/each}}
-
-*Total: {{done_items.length}} items*
-  </output>
-  <ask>Options:
-- [a] Archive all
-- [s] Select specific items (enter item numbers)
-- [q] Cancel
-
-Choice:</ask>
-  <check if="user selects 'q'">
-    <output>Cancelled. No changes made.</output>
-    <action>Exit workflow</action>
-  </check>
-  <check if="user selects 'a'">
-    <action>Set {{items_to_archive}} = all {{done_items}}</action>
-  </check>
-  <check if="user selects 's'">
-    <ask>Enter item numbers to archive (comma-separated):</ask>
-    <action>Resolve entered numbers against the table above</action>
-    <action>Set {{items_to_archive}} = selected items</action>
-  </check>
-</step>
-
-<step n="3" goal="Ensure done/ directory exists">
-  <action>Check if `_bmad-output/implementation-artifacts/done/` directory exists</action>
-  <action>If not, create it</action>
-</step>
-
-<step n="4" goal="Move files to done/ directory">
-  <action>For each item in {{items_to_archive}}:
-
-    **Stories** (type == story):
-    - Source: `_bmad-output/implementation-artifacts/{id}.md`
-    - Destination: `_bmad-output/implementation-artifacts/done/{id}.md`
-    - Use rename/move operation
-    - Skip if source file does not exist (log warning)
-    - Skip if destination file already exists (log warning — do not overwrite)
-
-    **Bugs** (type == bug):
-    - Source: `_bmad-output/implementation-artifacts/bug-{slug}.md`
-    - Destination: `_bmad-output/implementation-artifacts/done/bug-{slug}.md`
-    - Use rename/move operation
-    - Skip if source file does not exist (log warning)
-    - Skip if destination file already exists (log warning — do not overwrite)
-  </action>
-  <action>Track results: {{moved}}, {{skipped_missing}}, {{skipped_exists}}</action>
-</step>
-
-<step n="5" goal="Remove done IDs from sprint files">
-  <action>Glob `_bmad-output/implementation-artifacts/sprints/sprint-*.yaml` to find all sprint files</action>
-  <action>For each sprint file:
-    - Read the sprint's `items` array
-    - Check if any item IDs in the array match {{items_to_archive}}
-    - If NO matches found: skip this sprint file entirely (no modification needed)
-    - If matches found:
-      - Remove the matching item IDs from the array
-      - If items array becomes empty AND sprint status is `active`: auto-close the sprint by setting status to `closed`
-      - Update `last_modified` to current ISO timestamp
-      - Write the updated sprint file
-  </action>
-</step>
-
-<step n="6" goal="Remove done items from backlog.yaml">
-  <action>Read `_bmad-output/implementation-artifacts/backlog.yaml`</action>
-  <action>Remove all entries whose ID is in {{items_to_archive}}</action>
-  <action>Re-number remaining item priorities sequentially: 1, 2, 3, ..., N</action>
-  <action>Write updated `_bmad-output/implementation-artifacts/backlog.yaml`</action>
-</step>
-
-<step n="7" goal="Remove done entries from sprint-status.yaml">
-  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
-  <action>In the `development_status` section:
-    - Remove done story keys that are in {{items_to_archive}}
-    - Remove done bug keys that are in {{items_to_archive}}
-    - Do NOT remove epic keys (keys matching `epic-*`)
-    - Do NOT remove retrospective keys (keys ending with `-retrospective`)
-    - If all stories belonging to an epic have been removed: set that epic's status to `done`
-    - Preserve YAML comments where possible
-  </action>
-  <action>Write updated `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
-</step>
-
-<step n="8" goal="Report summary">
-  <output>
-## Archival Complete
-
-**Files moved to `done/`:** {{moved_count}}
-{{#each moved_items}}
-- {{id}} ({{type}}) -> done/
-{{/each}}
-
-{{#if skipped_missing.length}}
-**Skipped (source missing):** {{skipped_missing.length}}
-{{#each skipped_missing}}
-- {{id}} — source file not found
-{{/each}}
-{{/if}}
-
-{{#if skipped_exists.length}}
-**Skipped (already in done/):** {{skipped_exists.length}}
-{{#each skipped_exists}}
-- {{id}} — destination already exists
-{{/each}}
-{{/if}}
-
-**Sprint updates:**
-{{#each updated_sprints}}
-- {{sprint_id}}: removed {{removed_count}} item(s){{#if auto_closed}} — auto-closed (no remaining items){{/if}}
-{{/each}}
-
-**Backlog:** {{backlog_removed_count}} items removed, priorities renumbered 1..{{backlog_remaining_count}}
-
-**Sprint-status.yaml:** {{status_removed_count}} entries removed
-{{#if epics_marked_done.length}}
-- Epics marked done: {{#each epics_marked_done}}{{this}}{{#unless @last}}, {{/unless}}{{/each}}
-{{/if}}
-
-**Next Steps:**
-- Use `/sprint-status-view` to verify updated sprint state
-- Use `/prioritize-backlog` to reorder remaining backlog items
-  </output>
-</step>
-
-</workflow>

package/.opencode/skills/cmake-best-practices/SKILL.md

@@ -1,64 +0,0 @@
----
-name: Modern CMake Best Practices
-description: Enforce target-based, property-oriented CMake patterns (CMake 3.0+).
----
-# Modern CMake Best Practices (Target-Based Approach)
-
-This skill ensures that CMake definitions follow the "Modern CMake" philosophy (3.0+), focusing on targets and properties rather than global variables.
-
-## Policies
-
-### 1. Target-Centric Philosophy
-*   **Rule**: Treat targets as objects. Use `target_*` commands instead of global commands.
-*   **Action**: 
-    - **Forbidden**: `include_directories()`, `link_libraries()`, `add_definitions()`.
-    - **Mandatory**: `target_include_directories()`, `target_link_libraries()`, `target_compile_definitions()`.
-*   **Rationale**: Encapsulates requirements and prevents property leakage to unrelated targets.
-
-### 2. Visibility Hygiene (`PUBLIC`, `PRIVATE`, `INTERFACE`)
-*   **Rule**: Always specify the scope of target properties.
-*   **Action**:
-    - `PRIVATE`: Requirement only for building the target.
-    - `INTERFACE`: Requirement only for consumers of the target.
-    - `PUBLIC`: Requirement for both.
-*   **Rationale**: Ensures that internal dependencies (like a private logging library) don't bleed into the usage requirements of your high-level API.
-
-### 3. Feature-Based C++ Standards
-*   **Rule**: Do not manually set `CMAKE_CXX_STANDARD` or `-std=c++XX` flags.
-*   **Action**: Use `target_compile_features(my_target PUBLIC cxx_std_17)`.
-*   **Rationale**: Allows CMake to handle compiler-specific flags and ensures the compiler actually supports the requested features.
-
-### 4. No Global Variable Manipulation
-*   **Rule**: Ban direct modification of `CMAKE_CXX_FLAGS` or `CMAKE_EXE_LINKER_FLAGS`.
-*   **Action**: Use `target_compile_options()` for specific compiler warnings or flags.
-*   **Rationale**: Global flags make it impossible to have different settings for different targets in the same project.
-
-### 5. Namespaced Alias Targets
-*   **Rule**: Always provide an alias for library targets using a namespace.
-*   **Action**: `add_library(MyLib::MyLib ALIAS my_lib_target)`.
-*   **Rationale**: Makes exported targets look consistent with external dependencies (like those found via `find_package`).
-
-## Examples
-
-### Before (Legacy Procedural CMake)
-```cmake
-include_directories(${PROJECT_SOURCE_DIR}/include)
-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++17 -Wall")
-add_library(mylib mylib.cpp)
-```
-
-### After (Modern Target-Based CMake)
-```cmake
-add_library(mylib mylib.cpp)
-
-target_compile_features(mylib PUBLIC cxx_std_17)
-target_compile_options(mylib PRIVATE -Wall)
-
-target_include_directories(mylib 
-    PUBLIC 
-        $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include>
-        $<INSTALL_INTERFACE:include>
-)
-
-add_library(MyProject::MyLib ALIAS mylib)
-```

package/.opencode/skills/cmake-best-practices/examples/cmake.md

@@ -1,59 +0,0 @@
-# Modern CMake Examples
-
-### 1. Project Structure and App
-```cmake
-cmake_minimum_required(VERSION 3.14)
-project(MyAwesomeApp VERSION 1.0 LANGUAGES CXX)
-
-# Use target_compile_features for the whole project standard if needed
-# but target-specific is better.
-add_executable(app main.cpp)
-
-target_compile_features(app PRIVATE cxx_std_17)
-target_link_libraries(app PRIVATE MyProject::Core)
-```
-
-### 2. Library with Internal/External Dependencies
-```cmake
-add_library(core src/core.cpp)
-
-# Internal include dir
-target_include_directories(core 
-    PUBLIC  include
-    PRIVATE src
-)
-
-# Link against a 3rd party library found via find_package
-find_package(fmt REQUIRED)
-target_link_libraries(core 
-    PUBLIC  fmt::fmt
-    PRIVATE Threads::Threads
-)
-
-add_library(MyProject::Core ALIAS core)
-```
-
-### 3. Proper Header-Only Library
-```cmake
-add_library(utils INTERFACE)
-
-target_include_directories(utils 
-    INTERFACE 
-        $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include>
-        $<INSTALL_INTERFACE:include>
-)
-
-# Requirement: anyone using utils MUST have C++14
-target_compile_features(utils INTERFACE cxx_std_14)
-
-add_library(MyProject::Utils ALIAS utils)
-```
-
-### 4. Compiler-Specific Options Safely
-```cmake
-if(MSVC)
-    target_compile_options(core PRIVATE /W4 /WX)
-else()
-    target_compile_options(core PRIVATE -Wall -Wextra -Werror)
-endif()
-```

package/.opencode/skills/code-documentation/SKILL.md

@@ -1,57 +0,0 @@
----
-name: Code Documentation Best Practices
-description: Standardize file headers and method documentation across C++, C#, JS, TS, and Python.
----
-# Code Documentation Best Practices
-
-This skill enforces high-quality, standardized documentation for source code files and methods. It ensures consistent metadata and clear explanations of intent across different programming languages.
-
-## Policies
-
-### 1. Mandatory File Headers
-*   **Rule**: Every source file must begin with a standardized header block.
-*   **Contents**:
-    - **Purpose**: A brief description of what the file contains/solves.
-    - **Author/Project**: Project name or author information.
-    - **Metadata**: Date created/modified and version if applicable.
-
-### 2. Mandatory Method Documentation
-*   **Rule**: Every public or non-trivial internal function/method must have a documentation block immediately preceding it.
-*   **Standards**:
-    - **C++**: Use Doxygen style (`/** ... */`).
-    - **C#**: Use XML Documentation style (`/// <summary> ...`).
-    - **JS/TS**: Use JSDoc style (`/** ... */`).
-    - **Python**: Use PEP 257 Docstrings (`""" ... """`).
-*   **Required Fields**:
-    - **Summary**: Concise description of what the method does.
-    - **Parameters**: Name and purpose of each argument.
-    - **Return Value**: Description of the output.
-    - **Exceptions/Errors**: Document significant error states or exceptions thrown.
-
-### 3. Focus on "Why" and "What"
-*   **Rule**: Do not document trivial code (e.g., `i++ // increment i`).
-*   **Action**: Document the **intent** and **usage constraints**. If the code is complex, explain the high-level logic rather than line-by-line mechanics.
-
-### 4. Semantic Linking
-*   **Rule**: Use language-specific linking features (e.g., `@see`, `{@link}`, `<see cref=.../>`) to refer to related types or methods.
-
-## Language Specifics
-
-| Language | Format | Key Tags |
-| :--- | :--- | :--- |
-| **C++** | Doxygen | `\brief`, `\param`, `\return`, `\throw` |
-| **C#** | XML Doc | `<summary>`, `<param>`, `<returns>`, `<exception>` |
-| **JS/TS** | JSDoc | `@description`, `@param`, `@returns`, `@throws` |
-| **Python** | Docstrings | `Args:`, `Returns:`, `Raises:` (Google/NumPy style) |
-
----
-
-## Example (Generic Pattern)
-
-```text
-[File Header]
-[Imports]
-
-[Component Documentation]
-[Implementation]
-```

package/.opencode/skills/code-documentation/examples/cpp.md

@@ -1,29 +0,0 @@
-# C++ Documentation (Doxygen Style)
-
-### File Header
-```cpp
-/**
- * @file DataProcessor.hpp
- * @brief Handles high-performance transformation of raw sensor data.
- * @author Antigravity / ma-agents
- * @date 2026-02-22
- * @version 1.0.0
- */
-```
-
-### Method Documentation
-```cpp
-/**
- * @brief Calculates the moving average of a dataset.
- * 
- * This method uses a sliding window algorithm to smooth out volatility 
- * in sensor inputs.
- * 
- * @param data A span of float values to process.
- * @param windowSize The size of the averaging window (must be > 0).
- * @return The calculated moving average as a float.
- * @throw std::invalid_argument If data is empty or windowSize is invalid.
- * @see SignalFilter
- */
-float calculateMovingAverage(gsl::span<const float> data, size_t windowSize);
-```

package/.opencode/skills/code-documentation/examples/csharp.md

@@ -1,28 +0,0 @@
-# C# Documentation (XML Style)
-
-### File Header
-```csharp
-/*
- * File: AuthenticationService.cs
- * Purpose: Manages user login, token validation, and multi-factor authentication.
- * Author: Antigravity / ma-agents
- * Date: 2026-02-22
- */
-```
-
-### Method Documentation
-```csharp
-/// <summary>
-/// Validates a user's credentials against the secure identity store.
-/// </summary>
-/// <param name="username">The unique identifier for the user.</param>
-/// <param name="password">The plain-text password (will be hashed internally).</param>
-/// <returns>
-/// An <see cref="AuthResult"/> indicating success or failure with a details message.
-/// </returns>
-/// <exception cref="SecurityException">Thrown if the account is locked.</exception>
-public async Task<AuthResult> LoginAsync(string username, string password)
-{
-    // ...
-}
-```