ma-agents 3.4.8 → 3.5.0

package/.opencode/skills/remove-from-sprint/SKILL.md

@@ -1,163 +0,0 @@
----
-name: remove-from-sprint
-description: Remove items from a sprint and return them to the unassigned backlog
-type: skill
-triggers:
-  - "remove from sprint"
-  - "unassign from sprint"
----
-
-# Remove-from-Sprint Workflow
-
-Remove items from a sprint and return them to the unassigned backlog.
-
-<workflow>
-
-<step n="1" goal="List sprints that have items and select one">
-  <action>Glob `_bmad-output/implementation-artifacts/sprints/sprint-*.yaml` to discover all sprint files</action>
-  <check if="no sprint files found">
-    <output>No sprints found. Run `/add-sprint` first to create a sprint.</output>
-    <action>Exit workflow</action>
-  </check>
-  <action>For each sprint file, read and extract: id, name, status, capacity, items (array), last_modified</action>
-  <action>Filter to sprints that have at least 1 item in their items array</action>
-  <check if="no sprints have items">
-    <output>No sprints contain any items. Nothing to remove.</output>
-    <action>Exit workflow</action>
-  </check>
-  <output>
-## Sprints with Items
-
-| # | Sprint | Status | Items | Capacity | Last Modified |
-|---|---|---|---|---|---|
-{{#each filtered_sprints}}
-| {{@index+1}} | {{name}} ({{id}}) | {{status}} | {{items_count}} | {{capacity}} | {{last_modified}} |
-{{/each}}
-  </output>
-  <ask>Select sprint (enter number):</ask>
-  <action>Store selected sprint as {{target_sprint}}</action>
-  <action>Store {{session_last_modified}} = {{target_sprint.last_modified}} for concurrency guard</action>
-</step>
-
-<step n="2" goal="Display sprint items with backlog metadata">
-  <action>Read `_bmad-output/implementation-artifacts/backlog.yaml`</action>
-  <action>For each item ID in {{target_sprint.items}}, look up metadata from backlog.yaml to get: title, type, status, priority</action>
-  <action>If an item is not found in backlog.yaml, infer title from ID (kebab-case to title case) and mark type/status/priority as "unknown"</action>
-  <output>
-## Items in {{target_sprint.name}}
-
-| # | ID | Title | Type | Status | Priority |
-|---|---|---|---|---|---|
-{{#each sprint_items}}
-| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{status}} | {{priority}} |
-{{/each}}
-  </output>
-</step>
-
-<step n="3" goal="Prompt for items to remove">
-  <ask>Which items to remove? Enter item numbers (comma-separated), 'all' to remove all, or 'q' to cancel:</ask>
-  <check if="user enters 'q'">
-    <output>Cancelled. No changes made.</output>
-    <action>Exit workflow</action>
-  </check>
-  <check if="user enters 'all'">
-    <action>Set {{items_to_remove}} = all items in {{target_sprint.items}}</action>
-  </check>
-  <check if="user enters item numbers">
-    <action>Resolve entered numbers against the table from step 2</action>
-    <action>Set {{items_to_remove}} = selected items</action>
-  </check>
-</step>
-
-<step n="4" goal="Confirm removal">
-  <output>
-## Confirm Removal
-
-The following items will be removed from **{{target_sprint.name}}** and returned to the unassigned backlog:
-
-{{#each items_to_remove}}
-- {{id}} — {{title}}
-{{/each}}
-
-**Note:** Item status will NOT be changed. Items retain their current status.
-  </output>
-  <ask>Proceed? [y] Yes / [n] Cancel / [e] Edit selection:</ask>
-  <check if="user selects 'n'">
-    <output>Cancelled. No changes made.</output>
-    <action>Exit workflow</action>
-  </check>
-  <check if="user selects 'e'">
-    <goto step="3" />
-  </check>
-  <check if="user input is not 'y', 'n', or 'e'">
-    <output>Unrecognized option: "{{user_input}}". Please enter [y], [n], or [e].</output>
-    <goto step="4" />
-  </check>
-</step>
-
-<step n="5" goal="Concurrency guard — re-read sprint before writing">
-  <action>Re-read the sprint file: `_bmad-output/implementation-artifacts/sprints/{{target_sprint.id}}.yaml`</action>
-  <action>Extract the current `last_modified` timestamp from the file</action>
-  <check if="current file last_modified != {{session_last_modified}}">
-    <output>
-**Conflict Detected:** The sprint file was modified since this session started.
-
-**Session started with:** `last_modified: {{session_last_modified}}`
-**Current file has:** `last_modified: {{current_file_last_modified}}`
-    </output>
-    <ask>How to proceed?
-- [o] Overwrite with your changes (your modifications replace current file)
-- [r] Reload — restart from current file state
-- [x] Cancel — discard all changes
-
-Choice:</ask>
-    <check if="choice == 'x'">
-      <output>Cancelled. Sprint file not modified.</output>
-      <action>Exit workflow</action>
-    </check>
-    <check if="choice == 'r'">
-      <action>Reload {{target_sprint}} from current file content</action>
-      <action>Update {{session_last_modified}} to current file's last_modified</action>
-      <output>Reloaded sprint from current state. Restarting item selection.</output>
-      <goto step="2" />
-    </check>
-    <!-- if 'o', proceed to write with session changes -->
-  </check>
-</step>
-
-<step n="6" goal="Remove items from sprint and update backlog">
-  <action>For each item in {{items_to_remove}}:
-    1. Remove the item ID from the sprint's `items` array
-    2. In `backlog.yaml`, find the matching backlog entry and set its `sprint` field to null (or remove it)
-    3. Do NOT change the item's `status` field — status is preserved as-is
-  </action>
-  <action>**Dual-write — both files must be updated for consistency:**</action>
-  <action>Update `last_modified` in the sprint file to current ISO timestamp</action>
-  <action>Write the updated sprint file: `_bmad-output/implementation-artifacts/sprints/{{target_sprint.id}}.yaml`</action>
-  <check if="sprint file write fails">
-    <output>**Error:** Failed to write sprint file. No changes persisted. Backlog NOT modified.</output>
-    <action>Exit workflow</action>
-  </check>
-  <action>Write the updated `_bmad-output/implementation-artifacts/backlog.yaml`</action>
-  <check if="backlog.yaml write fails">
-    <output>**Warning: Inconsistent state!** Sprint file was updated but backlog.yaml write failed. Items have been removed from the sprint's `items` array but their `sprint` field in backlog.yaml still references {{target_sprint.id}}. Re-run `/remove-from-sprint` or manually fix backlog.yaml.</output>
-  </check>
-  <output>
-## Removal Complete
-
-**Sprint:** {{target_sprint.name}} ({{target_sprint.id}})
-
-**Removed items:**
-{{#each items_to_remove}}
-- {{id}} — {{title}} (status unchanged: {{status}})
-{{/each}}
-
-**Updated sprint capacity:** {{new_items_count}}/{{target_sprint.capacity}} items ({{new_remaining}} remaining)
-
-**Next Steps:**
-- Use `/add-to-sprint` to reassign items to a different sprint
-- Use `/sprint-status-view` to view sprint progress
-  </output>
-</step>
-
-</workflow>

package/.opencode/skills/remove-from-sprint/bmad-skill-manifest.yaml

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

package/.opencode/skills/self-signed-cert/SKILL.md

@@ -1,42 +0,0 @@
----
-name: Self-Signed Certificate Generator
-description: Generates secure self-signed certificates and Root CAs using OpenSSL.
----
-# Self-Signed Certificate Generator
-
-## Purpose
-Automate the creation of Root CAs and self-signed certificates for internal services, local development, and testing environments.
-
-## Instructions
-1.  **Environment Check**: Ensure `openssl` is installed and available in the PATH.
-2.  **Workflow Selection**:
-    - **Standalone Self-Signed**: Quickest for single service testing.
-    - **Root CA + Signed Cert**: Recommended for internal architectures where multiple services need to trust a single authority.
-3.  **Security Standards**:
-    - Key Size: Minimum 2048-bit (4096-bit preferred).
-    - Hashing: SHA-256 or higher.
-    - Permissions: Private keys must be set to `600`.
-
-## Rules
-- NEVER store private keys in version control.
-- ALWAYS include Subject Alternative Names (SANs) for modern browser compatibility.
-- Ensure the certificate Common Name (CN) matches the intended hostname.
-
-## Usage
-The skill provide both Bash (Linux/macOS) and PowerShell (Windows) scripts.
-
-### Linux / macOS
-Run `scripts/generate-cert.sh` with:
-- `TYPE`: `root` or `cert`
-- `NAME`: Base name for the files
-- `DNS`: Primary domain/IP
-
-Example: `bash scripts/generate-cert.sh cert my-service localhost`
-
-### Windows (PowerShell)
-Run `scripts/generate-cert.ps1` with:
-- `-Type`: `root` or `cert`
-- `-Name`: Base name
-- `-Dns`: Primary domain/IP
-
-Example: `.\scripts\generate-cert.ps1 -Type cert -Name my-service -Dns localhost`

package/.opencode/skills/self-signed-cert/scripts/generate-cert.ps1

@@ -1,45 +0,0 @@
-param (
-    [Parameter(Mandatory=$true)]
-    [ValidateSet("root", "cert")]
-    [string]$Type,
-    
-    [string]$Name = "server",
-    
-    [string]$Dns = "localhost",
-    
-    [string]$CaKey,
-    
-    [string]$CaCert
-)
-
-$ErrorActionPreference = "Stop"
-
-if ($Type -eq "root") {
-    Write-Host "Generating Root CA..." -ForegroundColor Cyan
-    openssl genrsa -out "${Name}_rootCA.key" 4096
-    openssl req -x509 -new -nodes -key "${Name}_rootCA.key" -sha256 -days 3650 -out "${Name}_rootCA.crt" `
-        -subj "/CN=${Name}-Root-CA/O=MA-Agents/C=US"
-    Write-Host "Root CA created: ${Name}_rootCA.crt" -ForegroundColor Green
-
-} elseif ($Type -eq "cert") {
-    if (-not $CaKey -or -not $CaCert) {
-        Write-Host "Generating standalone self-signed certificate..." -ForegroundColor Cyan
-        openssl req -x509 -newnodes -days 365 -newkey rsa:2048 `
-            -keyout "${Name}.key" -out "${Name}.crt" `
-            -subj "/CN=${Dns}/O=MA-Agents" `
-            -addext "subjectAltName = DNS:${Dns}"
-    } else {
-        Write-Host "Generating certificate signed by CA..." -ForegroundColor Cyan
-        openssl genrsa -out "${Name}.key" 2048
-        openssl req -new -key "${Name}.key" -out "${Name}.csr" -subj "/CN=${Dns}/O=MA-Agents"
-        
-        # Extension file for SAN
-        "subjectAltName = DNS:${Dns}" | Out-File -FilePath "${Name}.ext" -Encoding ascii
-        
-        openssl x509 -req -in "${Name}.csr" -CA "$CaCert" -CAkey "$CaKey" -CAcreateserial `
-            -out "${Name}.crt" -days 365 -sha256 -extfile "${Name}.ext"
-        
-        Remove-Item "${Name}.csr", "${Name}.ext" -ErrorAction SilentlyContinue
-    }
-    Write-Host "Certificate created: ${Name}.crt" -ForegroundColor Green
-}

package/.opencode/skills/self-signed-cert/scripts/generate-cert.sh

@@ -1,43 +0,0 @@
-#!/bin/bash
-# generate-cert.sh - Part of ma-agents self-signed-cert skill
-
-TYPE=$1
-NAME=${2:-"server"}
-DNS=${3:-"localhost"}
-
-if [ "$TYPE" == "root" ]; then
-    echo "Generating Root CA..."
-    openssl genrsa -out "${NAME}_rootCA.key" 4096
-    openssl req -x509 -new -nodes -key "${NAME}_rootCA.key" -sha256 -days 3650 -out "${NAME}_rootCA.crt" \
-        -subj "/CN=${NAME}-Root-CA/O=MA-Agents/C=US"
-    chmod 600 "${NAME}_rootCA.key"
-    echo "Root CA created: ${NAME}_rootCA.crt"
-
-elif [ "$TYPE" == "cert" ]; then
-    CA_KEY=$4
-    CA_CRT=$5
-
-    if [ -z "$CA_KEY" ] || [ -z "$CA_CRT" ]; then
-        echo "Generating standalone self-signed certificate..."
-        openssl req -x509 -newnodes -days 365 -newkey rsa:2048 \
-            -keyout "${NAME}.key" -out "${NAME}.crt" \
-            -subj "/CN=${DNS}/O=MA-Agents" \
-            -addext "subjectAltName = DNS:${DNS}"
-    else
-        echo "Generating certificate signed by CA..."
-        openssl genrsa -out "${NAME}.key" 2048
-        openssl req -new -key "${NAME}.key" -out "${NAME}.csr" -subj "/CN=${DNS}/O=MA-Agents"
-        
-        # Extension file for SAN
-        echo "subjectAltName = DNS:${DNS}" > "${NAME}.ext"
-        
-        openssl x509 -req -in "${NAME}.csr" -CA "$CA_CRT" -CAkey "$CA_KEY" -CAcreateserial \
-            -out "${NAME}.crt" -days 365 -sha256 -extfile "${NAME}.ext"
-        rm "${NAME}.csr" "${NAME}.ext"
-    fi
-    chmod 600 "${NAME}.key"
-    echo "Certificate created: ${NAME}.crt"
-else
-    echo "Usage: $0 [root|cert] [name] [dns] [ca_key] [ca_crt]"
-    exit 1
-fi

package/.opencode/skills/skill-creator/SKILL.md

@@ -1,196 +0,0 @@
----
-name: Skill Creator
-description: Guide for creating effective skills that extend Claude's capabilities with specialized knowledge, workflows, and tool integrations
----
-# Skill Creator
-
-This skill provides guidance for creating effective skills.
-
-## About Skills
-
-Skills are modular, self-contained packages that extend Claude's capabilities by providing
-specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
-domains or tasks—they transform Claude from a general-purpose agent into a specialized agent
-equipped with procedural knowledge that no model can fully possess.
-
-### What Skills Provide
-
-1. Specialized workflows - Multi-step procedures for specific domains
-2. Tool integrations - Instructions for working with specific file formats or APIs
-3. Domain expertise - Company-specific knowledge, schemas, business logic
-4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
-
-## Core Principles
-
-### Concise is Key
-
-The context window is a public good. Skills share the context window with everything else Claude needs: system prompt, conversation history, other Skills' metadata, and the actual user request.
-
-**Default assumption: Claude is already very smart.** Only add context Claude doesn't already have. Challenge each piece of information: "Does Claude really need this explanation?" and "Does this paragraph justify its token cost?"
-
-Prefer concise examples over verbose explanations.
-
-### Set Appropriate Degrees of Freedom
-
-Match the level of specificity to the task's fragility and variability:
-
-**High freedom (text-based instructions)**: Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach.
-
-**Medium freedom (pseudocode or scripts with parameters)**: Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior.
-
-**Low freedom (specific scripts, few parameters)**: Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed.
-
-### Anatomy of a Skill
-
-Every skill consists of a required SKILL.md file and optional bundled resources:
-
-```
-skill-name/
-├── SKILL.md (required)
-│   ├── YAML frontmatter metadata (required)
-│   │   ├── name: (required)
-│   │   ├── description: (required)
-│   │   └── compatibility: (optional, rarely needed)
-│   └── Markdown instructions (required)
-└── Bundled Resources (optional)
-    ├── scripts/          - Executable code (Python/Bash/etc.)
-    ├── references/       - Documentation intended to be loaded into context as needed
-    └── assets/           - Files used in output (templates, icons, fonts, etc.)
-```
-
-#### SKILL.md (required)
-
-- **Frontmatter** (YAML): Contains `name` and `description` fields (required), plus optional fields like `license`, `metadata`, and `compatibility`. Only `name` and `description` are read by Claude to determine when the skill triggers.
-- **Body** (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers.
-
-#### Bundled Resources (optional)
-
-##### Scripts (`scripts/`)
-
-Executable code for tasks that require deterministic reliability or are repeatedly rewritten.
-
-- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed
-- **Benefits**: Token efficient, deterministic, may be executed without loading into context
-
-##### References (`references/`)
-
-Documentation intended to be loaded as needed into context.
-
-- **When to include**: For documentation that Claude should reference while working
-- **Use cases**: Database schemas, API documentation, domain knowledge, company policies
-- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md
-- **Avoid duplication**: Information lives in either SKILL.md or references files, not both
-
-##### Assets (`assets/`)
-
-Files not intended to be loaded into context, but used within the output Claude produces.
-
-- **When to include**: When the skill needs files for final output
-- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents
-
-#### What NOT to Include
-
-Do NOT create: README.md, INSTALLATION_GUIDE.md, QUICK_REFERENCE.md, CHANGELOG.md, or other auxiliary documentation. The skill should only contain information needed for an AI agent to execute tasks.
-
-### Progressive Disclosure Design Principle
-
-Three-level loading system:
-
-1. **Metadata (name + description)** - Always in context (~100 words)
-2. **SKILL.md body** - When skill triggers (<5k words)
-3. **Bundled resources** - As needed by Claude (Unlimited)
-
-Keep SKILL.md body under 500 lines. Split content into separate files when approaching this limit.
-
-**Pattern 1: High-level guide with references**
-
-```markdown
-# PDF Processing
-## Quick start
-Extract text with pdfplumber: [code example]
-## Advanced features
-- **Form filling**: See [FORMS.md](FORMS.md) for complete guide
-- **API reference**: See [REFERENCE.md](REFERENCE.md) for all methods
-```
-
-**Pattern 2: Domain-specific organization**
-
-```
-bigquery-skill/
-├── SKILL.md (overview and navigation)
-└── references/
-    ├── finance.md (revenue, billing metrics)
-    ├── sales.md (opportunities, pipeline)
-    └── product.md (API usage, features)
-```
-
-**Pattern 3: Conditional details**
-
-```markdown
-# DOCX Processing
-## Creating documents
-Use docx-js for new documents. See [DOCX-JS.md](DOCX-JS.md).
-## Editing documents
-For simple edits, modify the XML directly.
-**For tracked changes**: See [REDLINING.md](REDLINING.md)
-```
-
-## Skill Creation Process
-
-1. Understand the skill with concrete examples
-2. Plan reusable skill contents (scripts, references, assets)
-3. Initialize the skill (run scripts/init_skill.py)
-4. Edit the skill (implement resources and write SKILL.md)
-5. Package the skill (run scripts/package_skill.py)
-6. Iterate based on real usage
-
-### Step 1: Understanding the Skill with Concrete Examples
-
-Gather concrete examples of how the skill will be used. Ask users clarifying questions about functionality and triggers. Conclude when there's clear understanding of supported functionality.
-
-### Step 2: Planning the Reusable Skill Contents
-
-Analyze each concrete example:
-1. Consider how to execute the example from scratch
-2. Identify what scripts, references, and assets would be helpful for repeated execution
-
-### Step 3: Initializing the Skill
-
-```bash
-scripts/init_skill.py <skill-name> --path <output-directory>
-```
-
-Creates skill directory with SKILL.md template, example resource directories, and placeholder files.
-
-### Step 4: Edit the Skill
-
-**Writing guideline:** Always use imperative/infinitive form.
-
-**Update Frontmatter:**
-- `name`: The skill name
-- `description`: Include both what the skill does AND specific triggers/contexts for when to use it
-
-**Update Body:**
-- Write instructions for using the skill and bundled resources
-- For multi-step processes: See references/workflows.md
-- For specific output formats: See references/output-patterns.md
-
-**Start with Reusable Skill Contents:**
-- Implement scripts, references, and assets first
-- Test scripts by running them
-- Delete example files not needed for the skill
-
-### Step 5: Packaging a Skill
-
-```bash
-scripts/package_skill.py <path/to/skill-folder> [output-directory]
-```
-
-Validates and packages the skill into a distributable .skill file (zip format).
-
-### Step 6: Iterate
-
-1. Use the skill on real tasks
-2. Notice struggles or inefficiencies
-3. Identify how SKILL.md or bundled resources should be updated
-4. Implement changes and test again

package/.opencode/skills/skill-creator/references/output-patterns.md

@@ -1,82 +0,0 @@
-# Output Patterns
-
-Use these patterns when skills need to produce consistent, high-quality output.
-
-## Template Pattern
-
-Provide templates for output format. Match the level of strictness to your needs.
-
-**For strict requirements (like API responses or data formats):**
-
-```markdown
-## Report structure
-
-ALWAYS use this exact template structure:
-
-# [Analysis Title]
-
-## Executive summary
-[One-paragraph overview of key findings]
-
-## Key findings
-- Finding 1 with supporting data
-- Finding 2 with supporting data
-- Finding 3 with supporting data
-
-## Recommendations
-1. Specific actionable recommendation
-2. Specific actionable recommendation
-```
-
-**For flexible guidance (when adaptation is useful):**
-
-```markdown
-## Report structure
-
-Here is a sensible default format, but use your best judgment:
-
-# [Analysis Title]
-
-## Executive summary
-[Overview]
-
-## Key findings
-[Adapt sections based on what you discover]
-
-## Recommendations
-[Tailor to the specific context]
-
-Adjust sections as needed for the specific analysis type.
-```
-
-## Examples Pattern
-
-For skills where output quality depends on seeing examples, provide input/output pairs:
-
-````markdown
-## Commit message format
-
-Generate commit messages following these examples:
-
-**Example 1:**
-Input: Added user authentication with JWT tokens
-Output:
-```
-feat(auth): implement JWT-based authentication
-
-Add login endpoint and token validation middleware
-```
-
-**Example 2:**
-Input: Fixed bug where dates displayed incorrectly in reports
-Output:
-```
-fix(reports): correct date formatting in timezone conversion
-
-Use UTC timestamps consistently across report generation
-```
-
-Follow this style: type(scope): brief description, then detailed explanation.
-````
-
-Examples help Claude understand the desired style and level of detail more clearly than descriptions alone.

package/.opencode/skills/skill-creator/references/workflows.md

@@ -1,28 +0,0 @@
-# Workflow Patterns
-
-## Sequential Workflows
-
-For complex tasks, break operations into clear, sequential steps. It is often helpful to give Claude an overview of the process towards the beginning of SKILL.md:
-
-```markdown
-Filling a PDF form involves these steps:
-
-1. Analyze the form (run analyze_form.py)
-2. Create field mapping (edit fields.json)
-3. Validate mapping (run validate_fields.py)
-4. Fill the form (run fill_form.py)
-5. Verify output (run verify_output.py)
-```
-
-## Conditional Workflows
-
-For tasks with branching logic, guide Claude through decision points:
-
-```markdown
-1. Determine the modification type:
-   **Creating new content?** → Follow "Creation workflow" below
-   **Editing existing content?** → Follow "Editing workflow" below
-
-2. Creation workflow: [steps]
-3. Editing workflow: [steps]
-```