@josstei/maestro 1.6.4-nightly.20260430

package/README.md

@@ -0,0 +1,220 @@
+# Maestro
+
+[![Version](https://img.shields.io/badge/version-1.6.4-blue)](https://github.com/josstei/maestro-orchestrate/releases)
+[![License](https://img.shields.io/badge/license-Apache--2.0-green)](LICENSE)
+[![Gemini CLI](https://img.shields.io/badge/Gemini_CLI-extension-orange)](https://github.com/google-gemini/gemini-cli)
+[![Claude Code](https://img.shields.io/badge/Claude_Code-plugin-blue)](https://docs.anthropic.com/en/docs/claude-code)
+[![Codex](https://img.shields.io/badge/Codex-plugin-black)](docs/runtime-codex.md)
+[![Qwen Code](https://img.shields.io/badge/Qwen_Code-extension-purple)](https://github.com/QwenLM/qwen-code)
+
+Maestro is a multi-agent development orchestration platform with 39 specialists, an Express path for simple work, a 4-phase standard workflow for medium and complex work, persistent session state, and standalone review/debug/security/perf/seo/accessibility/compliance entrypoints. It runs from one canonical `src/` tree across **Gemini CLI**, **Claude Code**, **Codex**, and **Qwen Code**.
+
+## Runtime Targets
+
+| Runtime | Location | Public Surface | Notes |
+|---------|----------|----------------|-------|
+| Gemini CLI | repo root | `/maestro:*` | Snake-case agents, TOML commands, hooks, TOML shell policies |
+| Claude Code | `claude/` | `/orchestrate`, `/review-code`, ... | Kebab-case agents with `maestro:` subagent names |
+| Codex | `plugins/maestro/` | `$maestro:*` | Plugin skills, `spawn_agent`, no runtime hooks |
+| Qwen Code | `qwen/` | `/maestro:*` | Gemini-CLI-compatible extension, `QWEN.md` context file, `SubagentStart`/`SubagentStop` hooks |
+
+## Getting Started
+
+### Prerequisites
+
+- One supported runtime: Gemini CLI, Claude Code, Codex, or Qwen Code
+- Node.js 20+ for the MCP server and helper scripts
+- Gemini CLI and Qwen Code only: enable experimental subagents in `~/.gemini/settings.json` (Gemini) or `~/.qwen/settings.json` (Qwen)
+
+```json
+{
+  "experimental": {
+    "enableAgents": true
+  }
+}
+```
+
+Maestro does not edit `~/.gemini/settings.json` or `~/.qwen/settings.json` for you.
+
+### Installation
+
+#### Gemini CLI
+
+```bash
+gemini extensions install https://github.com/josstei/maestro-orchestrate
+```
+
+Local development:
+
+```bash
+git clone https://github.com/josstei/maestro-orchestrate
+cd maestro-orchestrate
+gemini extensions link .
+```
+
+Verify with `gemini extensions list`.
+
+#### Claude Code
+
+Marketplace install:
+
+```bash
+claude plugin marketplace add josstei/maestro-orchestrate
+claude plugin install maestro@maestro-orchestrator --scope user
+```
+
+Development / temporary loading:
+
+```bash
+git clone https://github.com/josstei/maestro-orchestrate
+claude --plugin-dir /path/to/maestro-orchestrate/claude
+```
+
+More Claude-specific setup and plugin management lives in [claude/README.md](claude/README.md).
+
+#### Codex
+
+Register the marketplace:
+
+```bash
+codex plugin marketplace add josstei/maestro-orchestrate
+```
+
+Then start Codex, run `/plugins` to browse, select **Maestro**, and choose **Install**.
+
+Local development (path must start with `./`, `../`, `/`, or `~/` — Codex otherwise treats bare `owner/repo` as a GitHub source):
+
+```bash
+git clone https://github.com/josstei/maestro-orchestrate
+codex plugin marketplace add /absolute/path/to/maestro-orchestrate
+# then: start Codex, run `/plugins`, select Maestro → Install
+```
+
+More Codex-specific setup and runtime details live in [plugins/maestro/README.md](plugins/maestro/README.md) and [docs/runtime-codex.md](docs/runtime-codex.md).
+
+#### Qwen Code
+
+```bash
+qwen extensions install https://github.com/josstei/maestro-orchestrate
+```
+
+Local development:
+
+```bash
+git clone https://github.com/josstei/maestro-orchestrate
+cd maestro-orchestrate
+qwen extensions link .
+```
+
+Verify with `qwen extensions list`. Qwen Code uses the same `/maestro:*` command surface as Gemini CLI and reads `QWEN.md` as its context file.
+
+### Quick Start
+
+Start a full orchestration with the runtime-specific entrypoint:
+
+| Runtime | Example |
+|---------|---------|
+| Gemini CLI | `/maestro:orchestrate Build a REST API for a task management system with user authentication` |
+| Claude Code | `/orchestrate Build a REST API for a task management system with user authentication` |
+| Codex | `$maestro:orchestrate Build a REST API for a task management system with user authentication` |
+| Qwen Code | `/maestro:orchestrate Build a REST API for a task management system with user authentication` |
+
+Maestro classifies the task, chooses Express or Standard workflow, asks the required design questions, produces an implementation plan when needed, delegates execution to specialists, runs a quality gate, and archives the session state in `docs/maestro/`.
+
+## Examples
+
+Usage examples: [EXAMPLES.md](EXAMPLES.md). Gemini/Qwen forms shown:
+
+- Full orchestration: `/maestro:orchestrate Build a REST API for a task management system with user authentication`
+- Standalone review: `/maestro:review Review the staged changes for correctness, regressions, security, maintainability risk, and missing tests`
+- Security audit: `/maestro:security-audit Audit authentication, authorization, data exposure, secret handling, and exploitability risks`
+
+## Configuration
+
+Defaults work; these settings tune behavior:
+
+| Setting | Default | Purpose |
+|---------|---------|---------|
+| `MAESTRO_STATE_DIR` | `docs/maestro` | Session, plan, and archive output path |
+| `MAESTRO_EXECUTION_MODE` | `ask` | Choose `parallel`, `sequential`, or prompt |
+| `MAESTRO_AUTO_ARCHIVE` | `true` | Archive successful sessions automatically |
+| `MAESTRO_MAX_RETRIES` | `2` | Retry limit for failed phases |
+| `MAESTRO_MAX_CONCURRENT` | `0` | Parallel-agent cap, where `0` means no Maestro cap |
+| `MAESTRO_DISABLED_AGENTS` | unset | Specialists to exclude from assignment |
+
+## Commands
+
+| Capability | Gemini CLI | Claude Code | Codex | Qwen Code |
+|------------|------------|-------------|-------|-----------|
+| Orchestrate | `/maestro:orchestrate` | `/orchestrate` | `$maestro:orchestrate` | `/maestro:orchestrate` |
+| Execute | `/maestro:execute` | `/execute` | `$maestro:execute` | `/maestro:execute` |
+| Resume | `/maestro:resume` | `/resume-session` | `$maestro:resume-session` | `/maestro:resume` |
+| Status | `/maestro:status` | `/status` | `$maestro:status` | `/maestro:status` |
+| Archive | `/maestro:archive` | `/archive` | `$maestro:archive` | `/maestro:archive` |
+| Review | `/maestro:review` | `/review-code` | `$maestro:review-code` | `/maestro:review` |
+| Debug | `/maestro:debug` | `/debug-workflow` | `$maestro:debug-workflow` | `/maestro:debug` |
+| Security Audit | `/maestro:security-audit` | `/security-audit` | `$maestro:security-audit` | `/maestro:security-audit` |
+| Performance Check | `/maestro:perf-check` | `/perf-check` | `$maestro:perf-check` | `/maestro:perf-check` |
+| SEO Audit | `/maestro:seo-audit` | `/seo-audit` | `$maestro:seo-audit` | `/maestro:seo-audit` |
+| Accessibility Audit | `/maestro:a11y-audit` | `/a11y-audit` | `$maestro:a11y-audit` | `/maestro:a11y-audit` |
+| Compliance Check | `/maestro:compliance-check` | `/compliance-check` | `$maestro:compliance-check` | `/maestro:compliance-check` |
+
+For Claude Code and Codex, Maestro intentionally avoids bare skill names that collide with host commands. Use `/review-code`, `/debug-workflow`, and `/resume-session` in Claude Code, and `$maestro:review-code`, `$maestro:debug-workflow`, and `$maestro:resume-session` in Codex, so built-in `/review`, `/debug`, and `/resume` commands keep working.
+
+Qwen Code uses the same `/maestro:*` command surface as Gemini CLI.
+
+## Workflow
+
+- **Express**: For simple work. Maestro asks 1-2 clarifying questions, proposes a brief, delegates to one specialist, runs code review, and archives without a design doc or implementation plan.
+- **Standard**: For medium and complex work. Maestro runs Design, Plan, Execute, and Complete phases with explicit approval gates, phased execution, and final review blocking on unresolved Critical or Major findings.
+
+## Outputs and Success Criteria
+
+Maestro writes orchestration outputs under `MAESTRO_STATE_DIR`, usually `docs/maestro/`. Standard workflow outputs include active session state, design documents, implementation plans, phase reports, validation output, and archived records.
+
+A successful run must have an approved plan when Standard workflow is used, completed phase reports, validation results for the changed surface, and no unresolved Critical or Major review findings. If a phase cannot complete, Maestro records the blocker and the next required action instead of silently continuing.
+
+## Security and Permissions
+
+Maestro follows the host runtime's tool permissions, sandboxing, and confirmation model. It does not require committed secrets or long-lived credentials, and orchestration session state stays inside `MAESTRO_STATE_DIR` unless configured otherwise. Use `MAESTRO_DISABLED_AGENTS` to restrict specialists in sensitive repositories, and run `$maestro:security-audit` or the equivalent runtime command before adopting changes that touch authentication, authorization, secrets, or data exposure paths.
+
+## Documentation
+
+- [EXAMPLES.md](EXAMPLES.md) for copyable usage scenarios across all runtimes
+- [docs/overview.md](docs/overview.md) for the project model and generated structure
+- [docs/architecture.md](docs/architecture.md) for orchestration internals and architecture layout
+- [docs/usage.md](docs/usage.md) for development workflow, settings, and command surfaces
+- [docs/flow.md](docs/flow.md) for the orchestration workflow steps and hard gates
+- [docs/cicd.md](docs/cicd.md) for CI/CD pipeline workflows, release process, and Mermaid diagrams
+- [docs/runtime-gemini.md](docs/runtime-gemini.md) for Gemini runtime specifics
+- [docs/runtime-claude.md](docs/runtime-claude.md) for Claude runtime specifics
+- [docs/runtime-codex.md](docs/runtime-codex.md) for Codex runtime specifics
+- [docs/runtime-qwen.md](docs/runtime-qwen.md) for Qwen runtime specifics
+
+## Development and Release Validation
+
+Canonical source lives under `src/`. Runtime files in `agents/`, `commands/`, `hooks/`, `mcp/`, `policies/`, `claude/`, `plugins/maestro/`, and `qwen/` are generated; update `src/` first, then regenerate.
+
+```bash
+npm ci
+node scripts/generate.js
+git diff --exit-code --name-only
+node --test tests/unit/*.test.js tests/transforms/*.test.js tests/integration/*.test.js
+npm run pack:verify
+npm run release:artifacts
+npm run release:verify-artifacts
+```
+
+Release validation creates `dist/release/maestro-vX.Y.Z-extension.tar.gz`. The archive is intentionally generic: it unpacks with `gemini-extension.json`, `qwen-extension.json`, `.claude-plugin/marketplace.json`, and `.agents/plugins/marketplace.json` at the root, plus the runtime payload needed by Gemini CLI, Qwen Code, Claude Code, and Codex.
+
+Stable releases publish three aligned outputs:
+
+- Git tag `vX.Y.Z`
+- npm package `@josstei/maestro@X.Y.Z`
+- GitHub Release asset `maestro-vX.Y.Z-extension.tar.gz`
+
+Codex plugin releases launch the MCP server through the matching npm package version. Hook installation is explicit via `npm run install-hooks`; package, pack, and publish flows do not install git hooks.
+
+## License
+
+Apache-2.0

package/agents/accessibility_specialist.md

@@ -0,0 +1,20 @@
+---
+name: accessibility_specialist
+kind: local
+description: "Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for WCAG 2.1 AA compliance, reviewing keyboard navigation in modal dialogs, or validating ARIA usage in custom components."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - run_shell_command
+  - google_web_search
+  - write_todos
+  - read_many_files
+  - ask_user
+temperature: 0.2
+max_turns: 20
+timeout_mins: 8
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["accessibility-specialist"])` to read the full methodology at delegation time.

package/agents/analytics_engineer.md

@@ -0,0 +1,22 @@
+---
+name: analytics_engineer
+kind: local
+description: "Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding event tracking to a checkout flow, designing an A/B test for a pricing page, or defining KPI dashboards."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - google_web_search
+  - write_todos
+  - read_many_files
+  - ask_user
+temperature: 0.2
+max_turns: 25
+timeout_mins: 10
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["analytics-engineer"])` to read the full methodology at delegation time.

package/agents/api_designer.md

@@ -0,0 +1,19 @@
+---
+name: api_designer
+kind: local
+description: "API design specialist for endpoint design, request/response contracts, and API versioning strategies. Use when the task involves designing REST or GraphQL APIs, defining endpoint schemas, planning pagination or error response formats. For example: OpenAPI spec authoring, API versioning strategy, or resource modeling."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - read_many_files
+  - ask_user
+  - google_web_search
+  - web_fetch
+temperature: 0.3
+max_turns: 15
+timeout_mins: 5
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["api-designer"])` to read the full methodology at delegation time.

package/agents/architect.md

@@ -0,0 +1,19 @@
+---
+name: architect
+kind: local
+description: "System design specialist for architecture decisions, technology selection, and high-level component design. Use when the task requires evaluating architectural trade-offs, designing system components, selecting technology stacks, or planning service boundaries. For example: microservice decomposition, database schema design, or API contract planning."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - google_web_search
+  - read_many_files
+  - ask_user
+  - web_fetch
+temperature: 0.3
+max_turns: 15
+timeout_mins: 5
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["architect"])` to read the full methodology at delegation time.

package/agents/cloud_architect.md

@@ -0,0 +1,19 @@
+---
+name: cloud_architect
+kind: local
+description: "Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS, designing a VPC topology, or evaluating a CDN/edge-compute strategy."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - google_web_search
+  - read_many_files
+  - ask_user
+  - web_fetch
+temperature: 0.3
+max_turns: 15
+timeout_mins: 5
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["cloud-architect"])` to read the full methodology at delegation time.

package/agents/cobol_engineer.md

@@ -0,0 +1,22 @@
+---
+name: cobol_engineer
+kind: local
+description: "COBOL engineering specialist for mainframe program development, maintenance, and modernization on z/OS. Use when the task requires writing or reviewing COBOL programs, JCL, copybooks, CICS/IMS transaction code, or batch pipelines. For example: implementing a new batch job, refactoring a monolithic COBOL program, or reviewing a copybook change for binary compatibility."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - read_many_files
+  - ask_user
+  - google_web_search
+temperature: 0.2
+max_turns: 25
+timeout_mins: 10
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["cobol-engineer"])` to read the full methodology at delegation time.

package/agents/code_reviewer.md

@@ -0,0 +1,17 @@
+---
+name: code_reviewer
+kind: local
+description: "Code review specialist for identifying bugs, security vulnerabilities, and code quality issues. Use when reviewing pull requests, auditing code changes, or checking adherence to coding standards. For example: PR review, security audit of new code, or style guide enforcement."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - read_many_files
+  - ask_user
+temperature: 0.2
+max_turns: 15
+timeout_mins: 5
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["code-reviewer"])` to read the full methodology at delegation time.

package/agents/coder.md

@@ -0,0 +1,22 @@
+---
+name: coder
+kind: local
+description: "Implementation specialist for writing clean, well-structured code following established patterns and SOLID principles. Use when the task requires feature implementation, writing new modules, or building out functionality from specifications. For example: building a new API endpoint, implementing a service class, or writing utility functions."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - activate_skill
+  - read_many_files
+  - ask_user
+temperature: 0.2
+max_turns: 25
+timeout_mins: 10
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["coder"])` to read the full methodology at delegation time.

package/agents/compliance_reviewer.md

@@ -0,0 +1,19 @@
+---
+name: compliance_reviewer
+kind: local
+description: "Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture, or license compatibility checks. For example: auditing an app for GDPR compliance, designing cookie consent that satisfies ePrivacy, or checking open-source license compatibility."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - google_web_search
+  - web_fetch
+  - read_many_files
+  - ask_user
+temperature: 0.3
+max_turns: 15
+timeout_mins: 5
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["compliance-reviewer"])` to read the full methodology at delegation time.

package/agents/content_strategist.md

@@ -0,0 +1,19 @@
+---
+name: content_strategist
+kind: local
+description: "Content strategy specialist for content planning, editorial calendars, audience targeting, and content gap analysis. Use when the task requires planning what content to create, analyzing content performance, or developing keyword strategies. For example: building an editorial calendar, conducting content gap analysis, or defining content pillars for a product launch."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - google_web_search
+  - web_fetch
+  - read_many_files
+  - ask_user
+temperature: 0.3
+max_turns: 15
+timeout_mins: 5
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["content-strategist"])` to read the full methodology at delegation time.

package/agents/copywriter.md

@@ -0,0 +1,19 @@
+---
+name: copywriter
+kind: local
+description: "Marketing copywriter for persuasive content, landing pages, CTAs, and brand voice consistency. Use when the task requires writing marketing copy, product descriptions, email campaigns, or user-facing content that drives action. For example: writing landing page hero text, crafting email subject lines, or creating product feature descriptions."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - read_many_files
+  - ask_user
+temperature: 0.3
+max_turns: 20
+timeout_mins: 8
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["copywriter"])` to read the full methodology at delegation time.

package/agents/data_engineer.md

@@ -0,0 +1,22 @@
+---
+name: data_engineer
+kind: local
+description: "Data engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline construction, or schema evolution. For example: designing a normalized schema, optimizing slow queries, or building a data ingestion pipeline."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - read_many_files
+  - ask_user
+  - google_web_search
+temperature: 0.2
+max_turns: 20
+timeout_mins: 8
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["data-engineer"])` to read the full methodology at delegation time.

package/agents/database_administrator.md

@@ -0,0 +1,21 @@
+---
+name: database_administrator
+kind: local
+description: "Database administration specialist for RDBMS schema review, query tuning, index strategy, and migration safety on PostgreSQL, MySQL, SQL Server, and Oracle. Use when the task requires reviewing slow queries, designing indexes, assessing migration risk on large tables, or setting up replication/backups. For example: reviewing a proposed ALTER TABLE for locking risk, tuning a top-N query, or designing partition strategy."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - run_shell_command
+  - google_web_search
+  - read_many_files
+  - write_todos
+  - ask_user
+  - web_fetch
+temperature: 0.2
+max_turns: 20
+timeout_mins: 8
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["database-administrator"])` to read the full methodology at delegation time.

package/agents/db2_dba.md

@@ -0,0 +1,21 @@
+---
+name: db2_dba
+kind: local
+description: "DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production cursor, or planning a REORG during a maintenance window."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - run_shell_command
+  - google_web_search
+  - read_many_files
+  - write_todos
+  - ask_user
+  - web_fetch
+temperature: 0.2
+max_turns: 20
+timeout_mins: 8
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["db2-dba"])` to read the full methodology at delegation time.

package/agents/debugger.md

@@ -0,0 +1,19 @@
+---
+name: debugger
+kind: local
+description: "Debugging specialist for root cause analysis, investigating defects, and tracing execution flow. Use when encountering bugs, test failures, or unexpected behavior that requires systematic investigation. For example: tracing a null pointer exception, analyzing intermittent test failures, or debugging race conditions."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - read_many_files
+  - run_shell_command
+  - write_todos
+  - ask_user
+temperature: 0.2
+max_turns: 20
+timeout_mins: 8
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["debugger"])` to read the full methodology at delegation time.

package/agents/design_system_engineer.md

@@ -0,0 +1,22 @@
+---
+name: design_system_engineer
+kind: local
+description: "Design system engineering specialist for design tokens, component API contracts, theming architecture, CSS architecture, style consistency, and visual regression strategy. Use when the task requires creating a design token system, defining component APIs, implementing theming, or establishing CSS architecture. For example: setting up a token hierarchy with light/dark themes, designing the prop interface for a component library, or implementing a token-to-CSS pipeline."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - activate_skill
+  - read_many_files
+  - ask_user
+temperature: 0.2
+max_turns: 25
+timeout_mins: 10
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["design-system-engineer"])` to read the full methodology at delegation time.

package/agents/devops_engineer.md

@@ -0,0 +1,23 @@
+---
+name: devops_engineer
+kind: local
+description: "DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or configuring Terraform."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - google_web_search
+  - write_todos
+  - read_many_files
+  - web_fetch
+  - ask_user
+temperature: 0.2
+max_turns: 20
+timeout_mins: 8
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["devops-engineer"])` to read the full methodology at delegation time.

package/agents/hlasm_assembler_specialist.md

@@ -0,0 +1,22 @@
+---
+name: hlasm_assembler_specialist
+kind: local
+description: "IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend from the compile listing and PSW."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - read_many_files
+  - ask_user
+  - google_web_search
+temperature: 0.2
+max_turns: 25
+timeout_mins: 10
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["hlasm-assembler-specialist"])` to read the full methodology at delegation time.

package/agents/i18n_specialist.md

@@ -0,0 +1,21 @@
+---
+name: i18n_specialist
+kind: local
+description: "Internationalization specialist for i18n architecture, string extraction, locale management, pluralization rules, RTL support, and date/number/currency formatting. Use when the task requires internationalizing an application, setting up locale file structures, extracting hardcoded strings, or adding right-to-left language support. For example: adding multi-language support to a React app, extracting strings for translator handoff, or implementing RTL layout for Arabic."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - read_many_files
+  - ask_user
+temperature: 0.2
+max_turns: 20
+timeout_mins: 8
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["i18n-specialist"])` to read the full methodology at delegation time.

package/agents/ibm_i_specialist.md

@@ -0,0 +1,22 @@
+---
+name: ibm_i_specialist
+kind: local
+description: "IBM i (AS/400, iSeries) specialist for RPG, CL, DB2 for i, and OS/400 system operations. Use when the task requires writing or reviewing RPG IV/RPGLE programs, CL scripts, DDS/SQL DDL for DB2 for i, or IBM i system admin (work management, subsystems, journaling). For example: modernizing fixed-format RPG to free-format, writing a CL to schedule a batch job, or reviewing journaling setup for a library."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - read_many_files
+  - ask_user
+  - google_web_search
+temperature: 0.2
+max_turns: 25
+timeout_mins: 10
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["ibm-i-specialist"])` to read the full methodology at delegation time.