@josstei/maestro 1.6.4-nightly.20260430

package/agents/integration_engineer.md

@@ -0,0 +1,23 @@
+---
+name: integration_engineer
+kind: local
+description: "Integration engineering specialist for B2B/API integration, ETL between systems, message brokers, and EDI/flat-file exchanges. Use when the task requires connecting two systems with different data models, building a reliable pipeline across a broker (Kafka, RabbitMQ, MQ), or implementing an EDI/flat-file interface with a legacy partner. For example: wiring an outbound webhook with retry semantics, authoring an ETL job with idempotent merge, or implementing an EDI 850 inbound flow."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - activate_skill
+  - 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: ["integration-engineer"])` to read the full methodology at delegation time.

package/agents/ml_engineer.md

@@ -0,0 +1,23 @@
+---
+name: ml_engineer
+kind: local
+description: "Machine learning engineering specialist for designing, training, evaluating, and shipping production ML models. Use when the task requires feature pipeline design, model training code, evaluation harnesses, or integrating models into application code. For example: building a classifier training pipeline, wiring a model behind a REST endpoint, or reproducing a paper's baseline."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - activate_skill
+  - 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: ["ml-engineer"])` to read the full methodology at delegation time.

package/agents/mlops_engineer.md

@@ -0,0 +1,23 @@
+---
+name: mlops_engineer
+kind: local
+description: "MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up shadow deployments, or instrumenting drift alerts."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - read_many_files
+  - ask_user
+  - google_web_search
+  - web_fetch
+temperature: 0.2
+max_turns: 25
+timeout_mins: 10
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["mlops-engineer"])` to read the full methodology at delegation time.

package/agents/mobile_engineer.md

@@ -0,0 +1,23 @@
+---
+name: mobile_engineer
+kind: local
+description: "Mobile engineering specialist for iOS, Android, React Native, and Flutter feature work. Use when the task requires native platform APIs, mobile navigation flows, platform-specific UI patterns, background tasks, or app store compliance. For example: building a push notification handler, wiring biometric auth, implementing deep links, or diagnosing a platform-specific crash."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - activate_skill
+  - 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: ["mobile-engineer"])` to read the full methodology at delegation time.

package/agents/observability_engineer.md

@@ -0,0 +1,23 @@
+---
+name: observability_engineer
+kind: local
+description: "Observability engineering specialist for metrics, logs, traces, OpenTelemetry instrumentation, dashboards, and alert tuning. Use when the task requires adding observability to a service, building a dashboard, tuning alerts to reduce noise, or adopting an OpenTelemetry pipeline. For example: instrumenting a service with OTel, designing a SLO dashboard, or investigating an alert-storm root cause."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - read_many_files
+  - ask_user
+  - google_web_search
+  - web_fetch
+temperature: 0.2
+max_turns: 25
+timeout_mins: 10
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["observability-engineer"])` to read the full methodology at delegation time.

package/agents/performance_engineer.md

@@ -0,0 +1,21 @@
+---
+name: performance_engineer
+kind: local
+description: "Performance engineering specialist for bottleneck identification, profiling, and optimization. Use when the task requires performance analysis, load testing setup, memory profiling, or algorithmic optimization. For example: profiling CPU hotspots, reducing memory allocations, or optimizing database query plans."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - read_many_files
+  - run_shell_command
+  - google_web_search
+  - write_todos
+  - 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: ["performance-engineer"])` to read the full methodology at delegation time.

package/agents/platform_engineer.md

@@ -0,0 +1,24 @@
+---
+name: platform_engineer
+kind: local
+description: "Platform engineering specialist for internal developer platforms, paved paths, golden templates, and self-service tooling. Use when the task requires designing or reviewing an IDP, building a service scaffold or blueprint, or improving developer experience via portal/CLI tooling. For example: designing a Backstage plugin, authoring a new service template, or reviewing a self-service environment provisioning flow."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - activate_skill
+  - read_many_files
+  - ask_user
+  - google_web_search
+  - web_fetch
+temperature: 0.2
+max_turns: 25
+timeout_mins: 10
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["platform-engineer"])` to read the full methodology at delegation time.

package/agents/product_manager.md

@@ -0,0 +1,20 @@
+---
+name: product_manager
+kind: local
+description: "Product management specialist for requirements gathering, PRDs, user stories, feature prioritization, and competitive analysis. Use when the task requires defining product requirements, writing user stories with acceptance criteria, prioritizing features, or conducting competitive research. For example: writing a PRD for a new feature, prioritizing a backlog using RICE scoring, or defining acceptance criteria for user stories."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - google_web_search
+  - 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: ["product-manager"])` to read the full methodology at delegation time.

package/agents/prompt_engineer.md

@@ -0,0 +1,22 @@
+---
+name: prompt_engineer
+kind: local
+description: "Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example: designing a classifier prompt with calibrated confidence, writing an eval set for a summarization prompt, or tuning chunk size and reranking in a RAG pipeline."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - read_many_files
+  - google_web_search
+  - write_todos
+  - 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: ["prompt-engineer"])` to read the full methodology at delegation time.

package/agents/refactor.md

@@ -0,0 +1,22 @@
+---
+name: refactor
+kind: local
+description: "Refactoring specialist for codebase modernization, structural improvements, and technical debt reduction. Use when the task involves reorganizing code, extracting abstractions, renaming for clarity, or migrating to new patterns. For example: extracting a service layer, converting callbacks to async/await, or splitting a monolithic module."
+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: ["refactor"])` to read the full methodology at delegation time.

package/agents/release_manager.md

@@ -0,0 +1,22 @@
+---
+name: release_manager
+kind: local
+description: "Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example: producing release notes from commit history, planning a canary rollout, or reviewing a breaking-change label."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - read_many_files
+  - google_web_search
+  - write_todos
+  - 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: ["release-manager"])` to read the full methodology at delegation time.

package/agents/security_engineer.md

@@ -0,0 +1,21 @@
+---
+name: security_engineer
+kind: local
+description: "Security engineering specialist for vulnerability assessment, threat modeling, and security best practices. Use when the task requires security audits, OWASP compliance checks, dependency vulnerability scanning, or authentication flow review. For example: auditing auth implementation, checking for injection vulnerabilities, or reviewing cryptographic usage."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - run_shell_command
+  - google_web_search
+  - read_many_files
+  - web_fetch
+  - 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: ["security-engineer"])` to read the full methodology at delegation time.

package/agents/seo_specialist.md

@@ -0,0 +1,21 @@
+---
+name: seo_specialist
+kind: local
+description: "SEO specialist for technical audits, meta tag optimization, schema markup, and crawlability analysis. Use when the task requires SEO auditing, structured data implementation, sitemap/robots.txt review, or Core Web Vitals optimization. For example: auditing a site's crawlability, implementing JSON-LD schema markup, or optimizing meta tag strategy."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - run_shell_command
+  - google_web_search
+  - web_fetch
+  - 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: ["seo-specialist"])` to read the full methodology at delegation time.

package/agents/site_reliability_engineer.md

@@ -0,0 +1,21 @@
+---
+name: site_reliability_engineer
+kind: local
+description: "Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example: defining SLIs/SLOs for a new service, auditing an existing error budget policy, or drafting a runbook for a known failure mode."
+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: ["site-reliability-engineer"])` to read the full methodology at delegation time.

package/agents/solutions_architect.md

@@ -0,0 +1,19 @@
+---
+name: solutions_architect
+kind: local
+description: "Solutions architecture specialist for enterprise integration patterns, vendor systems, cross-team architecture, and target-state design. Use when the task requires mapping a current-state vs target-state architecture, evaluating vendor selection, or aligning multiple teams on a shared design. For example: designing an integration between SAP and a new CRM, mapping a strangler-fig path from monolith to services, or producing an ADR for a cross-organization capability."
+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: ["solutions-architect"])` to read the full methodology at delegation time.

package/agents/technical_writer.md

@@ -0,0 +1,21 @@
+---
+name: technical_writer
+kind: local
+description: "Technical writing specialist for documentation, API references, and architectural diagrams. Use when the task requires writing README files, API documentation, architecture decision records, or inline documentation. For example: writing an OpenAPI description, creating a getting-started guide, or documenting module interfaces."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - read_many_files
+  - google_web_search
+  - ask_user
+  - write_todos
+temperature: 0.3
+max_turns: 15
+timeout_mins: 5
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["technical-writer"])` to read the full methodology at delegation time.

package/agents/tester.md

@@ -0,0 +1,23 @@
+---
+name: tester
+kind: local
+description: "Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or creating end-to-end test scenarios."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - run_shell_command
+  - write_todos
+  - activate_skill
+  - 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: ["tester"])` to read the full methodology at delegation time.

package/agents/ux_designer.md

@@ -0,0 +1,20 @@
+---
+name: ux_designer
+kind: local
+description: "UX designer for user flow design, interaction patterns, wireframe descriptions, and usability evaluation. Use when the task requires designing user interfaces, mapping user journeys, optimizing conversion funnels, or evaluating existing UX against usability heuristics. For example: designing an onboarding flow, wireframing a dashboard layout, or auditing checkout abandonment."
+tools:
+  - read_file
+  - list_directory
+  - glob
+  - grep_search
+  - write_file
+  - replace
+  - google_web_search
+  - 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: ["ux-designer"])` to read the full methodology at delegation time.

package/agents/zos_sysprog.md

@@ -0,0 +1,21 @@
+---
+name: zos_sysprog
+kind: local
+description: "z/OS systems programming specialist for JCL, USS, SMP/E, RACF, subsystem diagnostics, and batch scheduling. Use when the task requires JCL authoring or review, z/OS Unix System Services setup, SMP/E maintenance, RACF profile review, or diagnosing SYSLOG/OPERLOG issues. For example: writing a JCL restart procedure, planning an SMP/E PTF install, or reviewing RACF dataset profiles for least privilege."
+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: ["zos-sysprog"])` to read the full methodology at delegation time.

package/bin/maestro-mcp-server.js

@@ -0,0 +1,10 @@
+#!/usr/bin/env node
+'use strict';
+
+const path = require('node:path');
+
+process.env.MAESTRO_RUNTIME = process.env.MAESTRO_RUNTIME || 'codex';
+process.env.MAESTRO_EXTENSION_PATH =
+  process.env.MAESTRO_EXTENSION_PATH || path.resolve(__dirname, '..');
+
+require('../src/mcp/maestro-server').main();

package/claude/.claude-plugin/plugin.json

@@ -0,0 +1,21 @@
+{
+  "name": "maestro",
+  "version": "1.6.4-nightly.20260430",
+  "description": "Multi-agent development orchestration platform — 39 specialists, 4-phase orchestration, native parallel subagents, persistent sessions, and standalone review/debug/security/perf/seo/a11y/compliance commands",
+  "author": {
+    "name": "josstei",
+    "email": "hello@josstei.dev",
+    "url": "https://github.com/josstei"
+  },
+  "license": "Apache-2.0",
+  "hooks": "./hooks/claude-hooks.json",
+  "mcpServers": "./.mcp.json",
+  "homepage": "https://github.com/josstei/maestro-orchestrate",
+  "repository": "https://github.com/josstei/maestro-orchestrate",
+  "keywords": [
+    "orchestration",
+    "multi-agent",
+    "planning",
+    "execution"
+  ]
+}

package/claude/.mcp.json

@@ -0,0 +1,11 @@
+{
+  "mcpServers": {
+    "maestro": {
+      "command": "node",
+      "args": [
+        "${CLAUDE_PLUGIN_ROOT}/mcp/maestro-server.js"
+      ],
+      "cwd": "${CLAUDE_PLUGIN_ROOT}"
+    }
+  }
+}