@josstei/maestro 1.6.4-nightly.20260430

package/claude/agents/release-manager.md

@@ -0,0 +1,38 @@
+---
+name: release-manager
+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.
+  
+  <example>
+  Context: User needs release notes produced for an upcoming release.
+  user: "Generate the v2.4.0 release notes from the commits since v2.3.0"
+  assistant: "I'll group the commits by change type (feature, fix, deprecation, breaking), write a user-facing summary per group, and flag any breaking changes with migration guidance."
+  <commentary>
+  Release Manager is appropriate for assembling release notes and changelog entries — writes docs, not code.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a phased rollout plan reviewed.
+  user: "Plan the rollout for the new checkout flow with a 1%/10%/50%/100% ramp"
+  assistant: "I'll produce the rollout schedule, readiness checklist, rollback criteria, and communication points at each ramp step."
+  <commentary>
+  Release Manager handles coordination artifacts: rollout plans, readiness checks, comms.
+  </commentary>
+  </example>
+model: inherit
+color: gold
+maxTurns: 15
+tools:
+  - Read
+  - Write
+  - Edit
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["release-manager"])` to read the full methodology at delegation time.

package/claude/agents/security-engineer.md

@@ -0,0 +1,37 @@
+---
+name: security-engineer
+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.
+  
+  <example>
+  Context: User needs a security audit or vulnerability assessment.
+  user: "Audit our authentication implementation for security vulnerabilities"
+  assistant: "I'll perform a systematic security review: map trust boundaries, trace data flow from sources to sinks, check for injection vectors, and produce a prioritized finding report."
+  <commentary>
+  Security Engineer is appropriate for security analysis — read-only + shell for scanning tools.
+  </commentary>
+  </example>
+  <example>
+  Context: User wants to check for specific vulnerability classes.
+  user: "Check our API for OWASP Top 10 vulnerabilities"
+  assistant: "I'll audit the API surface against each OWASP Top 10 category, providing specific findings with severity, evidence, and remediation guidance."
+  <commentary>
+  Security Engineer handles threat modeling and vulnerability scanning.
+  </commentary>
+  </example>
+model: inherit
+color: red
+maxTurns: 20
+tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["security-engineer"])` to read the full methodology at delegation time.

package/claude/agents/seo-specialist.md

@@ -0,0 +1,37 @@
+---
+name: seo-specialist
+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.
+  
+  <example>
+  Context: User needs an SEO audit of their web project.
+  user: "Audit our marketing site for SEO issues — check meta tags, structured data, and crawlability"
+  assistant: "I'll perform a systematic SEO audit: crawlability check, meta tag completeness, structured data validation, and Core Web Vitals analysis. Findings will be prioritized by search impact."
+  <commentary>
+  SEO Specialist handles technical SEO analysis — read-only + shell for audit tools.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs structured data implemented for rich search results.
+  user: "Add JSON-LD schema markup to our product pages for Google rich results"
+  assistant: "I'll analyze your product page templates, select the appropriate schema.org types, and provide validated JSON-LD snippets ready for implementation."
+  <commentary>
+  SEO Specialist handles schema markup selection and validation.
+  </commentary>
+  </example>
+model: inherit
+color: orange
+maxTurns: 20
+tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["seo-specialist"])` to read the full methodology at delegation time.

package/claude/agents/site-reliability-engineer.md

@@ -0,0 +1,37 @@
+---
+name: site-reliability-engineer
+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.
+  
+  <example>
+  Context: User is defining reliability targets for a new or existing service.
+  user: "Define SLIs and SLOs for our checkout API"
+  assistant: "I'll define the user-journey SLIs (availability, latency, freshness), propose SLO targets grounded in current performance, and size the error budget with a burn-rate alert policy."
+  <commentary>
+  SRE is appropriate for SLI/SLO definition and error budget policy, not for code fixes.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a runbook or postmortem review.
+  user: "Review our payments outage postmortem for action-item quality"
+  assistant: "I'll audit the timeline, classify contributing factors, assess whether action items are concrete and owned, and flag any blameful or speculative language."
+  <commentary>
+  SRE handles reliability process artifacts: runbooks, postmortems, error budget reviews.
+  </commentary>
+  </example>
+model: inherit
+color: orange
+maxTurns: 20
+tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["site-reliability-engineer"])` to read the full methodology at delegation time.

package/claude/agents/solutions-architect.md

@@ -0,0 +1,33 @@
+---
+name: solutions-architect
+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.
+  
+  <example>
+  Context: User needs a cross-team integration designed.
+  user: "Design the integration between our new billing system and the existing ERP"
+  assistant: "I'll map the data ownership, integration patterns (sync vs async), canonical data model, idempotency needs, and rollout plan for dual-write vs cutover."
+  <commentary>
+  Solutions Architect is appropriate for cross-system, cross-team integration design — read-only.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a current-to-target-state roadmap.
+  user: "Plan the roadmap from our monolith to services for order management"
+  assistant: "I'll produce a current-state map, target-state diagram, and a phased strangler-fig sequence with clear capability boundaries and migration risks."
+  <commentary>
+  Solutions Architect handles multi-phase modernization roadmaps with measurable phases.
+  </commentary>
+  </example>
+model: inherit
+color: lavender
+maxTurns: 15
+tools:
+  - Read
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["solutions-architect"])` to read the full methodology at delegation time.

package/claude/agents/technical-writer.md

@@ -0,0 +1,37 @@
+---
+name: technical-writer
+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.
+  
+  <example>
+  Context: User needs documentation written or updated for their project.
+  user: "Write the API documentation for our authentication service"
+  assistant: "I'll write documentation tailored to the target audience — I'll need to confirm whether this is for end-users, developers integrating the API, or internal maintainers."
+  <commentary>
+  Technical Writer is appropriate for documentation tasks — writes files but does not modify source code.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs existing docs audited or improved.
+  user: "Our README is outdated and confusing — can you fix it?"
+  assistant: "I'll audit the current README against the actual codebase state, identify gaps and inaccuracies, and rewrite for clarity with the developer audience in mind."
+  <commentary>
+  Technical Writer handles documentation quality and accuracy improvements.
+  </commentary>
+  </example>
+model: inherit
+color: green
+maxTurns: 15
+tools:
+  - Read
+  - Write
+  - Edit
+  - Glob
+  - Grep
+  - WebSearch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["technical-writer"])` to read the full methodology at delegation time.

package/claude/agents/tester.md

@@ -0,0 +1,39 @@
+---
+name: tester
+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.
+  
+  <example>
+  Context: User needs tests written for new or existing code.
+  user: "Write tests for the authentication service we just implemented"
+  assistant: "I'll discover the project's test framework and conventions, write unit and integration tests using injectable dependencies, then run the suite to confirm they pass."
+  <commentary>
+  Tester is appropriate for test authoring — writes test files only, does not modify source code.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs test coverage improved for a module.
+  user: "Our payment module has no tests and we're about to refactor it"
+  assistant: "I'll analyze the payment module's public API surface, identify critical paths and edge cases, and write a comprehensive test suite before any refactoring begins."
+  <commentary>
+  Tester handles coverage gaps and pre-refactor test harness creation.
+  </commentary>
+  </example>
+model: inherit
+color: magenta
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - Skill
+  - WebSearch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["tester"])` to read the full methodology at delegation time.

package/claude/agents/ux-designer.md

@@ -0,0 +1,34 @@
+---
+name: ux-designer
+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.
+  
+  <example>
+  Context: User needs user flow design for a new feature.
+  user: "Design the user onboarding flow for our SaaS product"
+  assistant: "I'll map the user journey from signup to first value moment, define each screen's purpose and interaction patterns, and identify drop-off risks with mitigation strategies."
+  <commentary>
+  UX Designer handles user flow design and interaction pattern selection.
+  </commentary>
+  </example>
+  <example>
+  Context: User wants UX review of an existing interface.
+  user: "Our checkout flow has a 60% abandonment rate — review the UX"
+  assistant: "I'll evaluate the checkout flow against usability heuristics, identify friction points and cognitive overload, and provide specific wireframe-level improvements."
+  <commentary>
+  UX Designer handles usability evaluation and improvement recommendations.
+  </commentary>
+  </example>
+model: inherit
+color: purple
+maxTurns: 20
+tools:
+  - Read
+  - Write
+  - Edit
+  - Glob
+  - Grep
+  - WebSearch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["ux-designer"])` to read the full methodology at delegation time.

package/claude/agents/zos-sysprog.md

@@ -0,0 +1,37 @@
+---
+name: zos-sysprog
+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.
+  
+  <example>
+  Context: User needs JCL or job scheduling reviewed.
+  user: "Review this JCL for our nightly batch; it keeps ABENDing on step 3 with S0C4"
+  assistant: "I'll check the DCB attributes, dataset allocation, REGION size, and step conditional logic, then cross-reference the S0C4 against the compile listing to locate the failing module."
+  <commentary>
+  z/OS Sysprog is appropriate for JCL/ABEND diagnostics and resource allocation issues.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a RACF review for a new application.
+  user: "Review the RACF profiles for our new app's datasets and started task"
+  assistant: "I'll audit dataset profiles for least privilege, check the STC identity's OMVS segment and UID, verify generic profile coverage, and flag any UACC above NONE."
+  <commentary>
+  z/OS Sysprog handles RACF review and security posture for z/OS resources.
+  </commentary>
+  </example>
+model: inherit
+color: slate
+maxTurns: 20
+tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["zos-sysprog"])` to read the full methodology at delegation time.

package/claude/hooks/claude-hooks.json

@@ -0,0 +1,48 @@
+{
+  "hooks": {
+    "SessionEnd": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node ${CLAUDE_PLUGIN_ROOT}/scripts/hook-runner.js claude session-end",
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node ${CLAUDE_PLUGIN_ROOT}/scripts/hook-runner.js claude session-start",
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node ${CLAUDE_PLUGIN_ROOT}/scripts/hook-runner.js claude before-agent",
+            "timeout": 10
+          }
+        ],
+        "matcher": "Agent"
+      },
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node ${CLAUDE_PLUGIN_ROOT}/scripts/policy-enforcer.js",
+            "timeout": 5
+          }
+        ],
+        "matcher": "Bash"
+      }
+    ]
+  }
+}

package/claude/mcp/maestro-server.js

@@ -0,0 +1,9 @@
+'use strict';
+
+const fs = require('node:fs');
+const path = require('node:path');
+
+process.env.MAESTRO_RUNTIME = process.env.MAESTRO_RUNTIME || 'claude';
+const repoEntry = path.resolve(__dirname, '../../src/mcp/maestro-server.js');
+const bundledEntry = path.resolve(__dirname, '../src/mcp/maestro-server.js');
+require(fs.existsSync(repoEntry) ? repoEntry : bundledEntry).main();

package/claude/mcp-config.example.json

@@ -0,0 +1,9 @@
+{
+  "maestro": {
+    "command": "node",
+    "args": [
+      "./mcp/maestro-server.js"
+    ],
+    "cwd": "<path-to-maestro-plugin>"
+  }
+}

package/claude/scripts/adapters/claude-adapter.js

@@ -0,0 +1,7 @@
+'use strict';
+const fs = require('node:fs');
+const path = require('node:path');
+
+const repoEntry = path.resolve(__dirname, '../../../src/platforms/shared/adapters/claude-adapter.js');
+const bundledEntry = path.resolve(__dirname, '../../src/platforms/shared/adapters/claude-adapter.js');
+module.exports = require(fs.existsSync(repoEntry) ? repoEntry : bundledEntry);

package/claude/scripts/hook-runner.js

@@ -0,0 +1,8 @@
+'use strict';
+
+const fs = require('node:fs');
+const path = require('node:path');
+
+const repoEntry = path.resolve(__dirname, '../../src/platforms/shared/hook-runner.js');
+const bundledEntry = path.resolve(__dirname, '../src/platforms/shared/hook-runner.js');
+require(fs.existsSync(repoEntry) ? repoEntry : bundledEntry);