@josstei/maestro 1.6.4-nightly.20260430

package/claude/agents/db2-dba.md

@@ -0,0 +1,37 @@
+---
+name: db2-dba
+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.
+  
+  <example>
+  Context: User needs a DB2 plan regression diagnosed after a REBIND.
+  user: "Our nightly batch slowed 4x after last week's REBIND; can you investigate?"
+  assistant: "I'll pull the current and previous access paths from EXPLAIN, compare matching index choices and join methods, and recommend either a targeted plan stability action or RUNSTATS refresh."
+  <commentary>
+  DB2 DBA is appropriate for plan-stability analysis, RUNSTATS, and bind strategy.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs REORG and RUNSTATS planning for a large tablespace.
+  user: "Plan a REORG of our ACCOUNTS tablespace that's 300GB and 30% disorganized"
+  assistant: "I'll evaluate REORG with SHRLEVEL CHANGE vs REFERENCE, estimate the log volume and elapsed time, propose a maintenance window, and include an inline RUNSTATS step."
+  <commentary>
+  DB2 DBA handles utility planning and maintenance sequencing.
+  </commentary>
+  </example>
+model: inherit
+color: brown
+maxTurns: 20
+tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["db2-dba"])` to read the full methodology at delegation time.

package/claude/agents/debugger.md

@@ -0,0 +1,32 @@
+---
+name: debugger
+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.
+  
+  <example>
+  Context: User has a bug or unexpected behavior to investigate.
+  user: "Our API is returning 500 errors intermittently on the payment endpoint"
+  assistant: "I'll investigate systematically: read the error logs, trace the code path, form and test hypotheses, and report root cause with evidence."
+  <commentary>
+  Debugger is appropriate for investigation — read-only + shell execution for diagnosis, no code modifications.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs root cause analysis for a performance or correctness issue.
+  user: "The database queries are taking 10x longer since the last deployment"
+  assistant: "I'll trace the query execution path, compare before/after changes, and identify the root cause with specific evidence before reporting."
+  <commentary>
+  Debugger handles investigation tasks that require hypothesis testing via shell commands.
+  </commentary>
+  </example>
+model: inherit
+color: red
+maxTurns: 20
+tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["debugger"])` to read the full methodology at delegation time.

package/claude/agents/design-system-engineer.md

@@ -0,0 +1,38 @@
+---
+name: design-system-engineer
+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.
+  
+  <example>
+  Context: User needs to establish a design token system.
+  user: "Set up a design token system for our component library with light and dark themes"
+  assistant: "I'll design the token hierarchy (primitive → semantic → component), implement the token-to-CSS pipeline, and set up theme switching with proper fallbacks."
+  <commentary>
+  Design System Engineer handles token architecture and theming systems.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs component API design for a design system.
+  user: "Design the API contract for our Button, Input, and Modal components"
+  assistant: "I'll define prop interfaces with variant enums, composition patterns, accessibility requirements, and usage examples for each component."
+  <commentary>
+  Design System Engineer handles component API design and style architecture.
+  </commentary>
+  </example>
+model: inherit
+color: pink
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - Skill
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["design-system-engineer"])` to read the full methodology at delegation time.

package/claude/agents/devops-engineer.md

@@ -0,0 +1,39 @@
+---
+name: devops-engineer
+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.
+  
+  <example>
+  Context: User needs CI/CD pipelines, containerization, or deployment infrastructure.
+  user: "Set up a CI/CD pipeline for our Node.js service with Docker and GitHub Actions"
+  assistant: "I'll design and implement the pipeline with health checks, rollback capability, and secret management via environment variables — no hardcoded credentials."
+  <commentary>
+  DevOps Engineer handles infrastructure, deployment, and automation work.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs cloud infrastructure or IaC configuration.
+  user: "Write Terraform configs for our staging and production environments"
+  assistant: "I'll create environment-specific Terraform configurations with documented decisions, health checks, and rollback-capable deployment patterns."
+  <commentary>
+  DevOps Engineer is appropriate for infrastructure-as-code and deployment configuration.
+  </commentary>
+  </example>
+model: inherit
+color: magenta
+maxTurns: 20
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - WebSearch
+  - WebFetch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["devops-engineer"])` to read the full methodology at delegation time.

package/claude/agents/hlasm-assembler-specialist.md

@@ -0,0 +1,38 @@
+---
+name: hlasm-assembler-specialist
+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.
+  
+  <example>
+  Context: User needs an HLASM module written or modified.
+  user: "Write a reentrant HLASM subroutine that computes a CRC32 for a given buffer"
+  assistant: "I'll write the module with standard entry/exit linkage, use register equates, keep it reentrant by using DSECTs for work areas, and provide both the source and a sample driver."
+  <commentary>
+  HLASM Specialist is appropriate for performance-critical or system-level mainframe code.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs an S0C4 abend diagnosed from a compile listing.
+  user: "S0C4 in our auth exit; PSW points at offset X'2A6'"
+  assistant: "I'll locate offset X'2A6' in the listing, identify the instruction and base register, check the DSECT-to-operand mapping, and trace which register went stale."
+  <commentary>
+  HLASM Specialist handles abend diagnostics using compile listings and register/PSW analysis.
+  </commentary>
+  </example>
+model: inherit
+color: olive
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["hlasm-assembler-specialist"])` to read the full methodology at delegation time.

package/claude/agents/i18n-specialist.md

@@ -0,0 +1,37 @@
+---
+name: i18n-specialist
+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.
+  
+  <example>
+  Context: User needs to internationalize an existing application.
+  user: "Our React app needs to support English, Spanish, and Japanese"
+  assistant: "I'll audit the codebase for hardcoded strings, set up the i18n library and locale file structure, extract strings with translator context, and handle date/number formatting per locale."
+  <commentary>
+  i18n Specialist handles full internationalization architecture and string extraction.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs RTL language support.
+  user: "Add Arabic language support to our web app — including RTL layout"
+  assistant: "I'll implement bidirectional text support: CSS logical properties, RTL-aware component layout, mirrored icons, and locale-specific number formatting."
+  <commentary>
+  i18n Specialist handles RTL support and locale-specific formatting.
+  </commentary>
+  </example>
+model: inherit
+color: indigo
+maxTurns: 20
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["i18n-specialist"])` to read the full methodology at delegation time.

package/claude/agents/ibm-i-specialist.md

@@ -0,0 +1,38 @@
+---
+name: ibm-i-specialist
+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.
+  
+  <example>
+  Context: User needs an RPG program modernized or written.
+  user: "Modernize this fixed-format RPG III program to free-format RPG IV"
+  assistant: "I'll convert the D/C specs to free-format, replace MOVE/MOVEL with EVAL where appropriate, and introduce sub-procedures to replace subroutines — preserving the existing business logic and file I/O semantics."
+  <commentary>
+  IBM i Specialist is appropriate for RPG modernization and free-format migration.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a CL script reviewed or written.
+  user: "Write a CL that runs our nightly billing batch with proper error handling"
+  assistant: "I'll write the CL with MONMSG for each command, library-list setup, job queue submission, and exit-code mapping to the scheduler's expected return codes."
+  <commentary>
+  IBM i Specialist handles CL scripting, job submission, and MONMSG error handling.
+  </commentary>
+  </example>
+model: inherit
+color: bronze
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["ibm-i-specialist"])` to read the full methodology at delegation time.

package/claude/agents/integration-engineer.md

@@ -0,0 +1,39 @@
+---
+name: integration-engineer
+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.
+  
+  <example>
+  Context: User needs a durable integration between two systems.
+  user: "Wire an outbound webhook from our order service to a partner with at-least-once delivery"
+  assistant: "I'll use the outbox pattern to guarantee publish-after-commit, a retry policy with jitter and capped attempts, a dead-letter store for poison messages, and idempotency keys so the partner can dedupe."
+  <commentary>
+  Integration Engineer is appropriate for reliable delivery patterns across system boundaries.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a legacy flat-file interface with a partner.
+  user: "Implement inbound EDI 850 purchase orders landing on SFTP, processed into our order system"
+  assistant: "I'll ingest the file with checksum and duplicate detection, parse the 850 segments into our canonical order model, produce a 997 functional ack, and publish events for downstream consumers."
+  <commentary>
+  Integration Engineer handles flat-file, EDI, and legacy protocols alongside modern APIs.
+  </commentary>
+  </example>
+model: inherit
+color: coral
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - Skill
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["integration-engineer"])` to read the full methodology at delegation time.

package/claude/agents/ml-engineer.md

@@ -0,0 +1,39 @@
+---
+name: ml-engineer
+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.
+  
+  <example>
+  Context: User needs an ML training or inference pipeline built.
+  user: "Build a training pipeline for our churn prediction model using the existing feature store"
+  assistant: "I'll design the pipeline around the existing feature store contracts: deterministic data splits, versioned feature schema, a baseline model, and a held-out evaluation set before any hyperparameter work."
+  <commentary>
+  ML Engineer is appropriate when the task involves training, evaluation, or serving code — not just analysis.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a trained model integrated into an application.
+  user: "Wire our sentiment model behind a /predict endpoint with input validation and batching"
+  assistant: "I'll design a typed inference contract, add input validation matching the training preprocessing, add batching with a bounded queue, and expose p50/p95 latency metrics."
+  <commentary>
+  ML Engineer handles production integration of models, including latency, batching, and contract stability.
+  </commentary>
+  </example>
+model: inherit
+color: teal
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - Skill
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["ml-engineer"])` to read the full methodology at delegation time.

package/claude/agents/mlops-engineer.md

@@ -0,0 +1,39 @@
+---
+name: mlops-engineer
+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.
+  
+  <example>
+  Context: User needs a model promoted from experimentation to production.
+  user: "Set up a deployment pipeline for our recommender model with canary rollout and drift monitoring"
+  assistant: "I'll register the model with a signed manifest, wire a canary that routes 5% of traffic, compare online metrics against baseline, and enable automatic rollback on drift or error-rate breach."
+  <commentary>
+  MLOps Engineer is appropriate for model lifecycle, deployment, and monitoring work.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs automated retraining on a cadence.
+  user: "Schedule weekly retraining with validation gates before promotion"
+  assistant: "I'll add the retraining job, a validation stage that compares challenger metrics to the current champion on a frozen eval set, and a promotion step gated on both accuracy and fairness thresholds."
+  <commentary>
+  MLOps Engineer handles automation around training, promotion, and monitoring.
+  </commentary>
+  </example>
+model: inherit
+color: indigo
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["mlops-engineer"])` to read the full methodology at delegation time.

package/claude/agents/mobile-engineer.md

@@ -0,0 +1,39 @@
+---
+name: mobile-engineer
+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.
+  
+  <example>
+  Context: User needs a feature implemented in a native or cross-platform mobile codebase.
+  user: "Add biometric authentication to our iOS and Android apps"
+  assistant: "I'll implement a platform-agnostic interface, wire the iOS LocalAuthentication and Android BiometricPrompt implementations, handle fallbacks, and keep the key material inside secure enclave/keystore."
+  <commentary>
+  Mobile Engineer is appropriate for platform API work that requires knowledge of iOS/Android lifecycles and security primitives.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a crash or platform-specific defect diagnosed.
+  user: "Users are seeing app freezes on Android 14 on launch"
+  assistant: "I'll inspect the startup path for main-thread blocking, check new Android 14 foreground service restrictions, and cross-reference ANR traces against our background jobs."
+  <commentary>
+  Mobile Engineer handles platform-specific diagnostics and remediation.
+  </commentary>
+  </example>
+model: inherit
+color: amber
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - Skill
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["mobile-engineer"])` to read the full methodology at delegation time.

package/claude/agents/observability-engineer.md

@@ -0,0 +1,39 @@
+---
+name: observability-engineer
+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.
+  
+  <example>
+  Context: User needs a service instrumented with OpenTelemetry.
+  user: "Add OpenTelemetry tracing and metrics to our order service"
+  assistant: "I'll add the OTel SDK, instrument the HTTP handler, outbound HTTP, and database client, emit RED metrics, and wire the exporter to the OTLP collector with a resource definition tagged by service and version."
+  <commentary>
+  Observability Engineer is appropriate for OTel instrumentation and pipeline work.
+  </commentary>
+  </example>
+  <example>
+  Context: User has an alert-storm problem and wants the alerting audited.
+  user: "We had 140 pages on a single incident last week; audit the alerts"
+  assistant: "I'll map alerts to SLOs, identify duplicates and symptom-vs-cause conflicts, and propose burn-rate alerts plus routing rules that dedupe by incident context."
+  <commentary>
+  Observability Engineer handles alert quality and noise reduction.
+  </commentary>
+  </example>
+model: inherit
+color: turquoise
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["observability-engineer"])` to read the full methodology at delegation time.

package/claude/agents/performance-engineer.md

@@ -0,0 +1,34 @@
+---
+name: performance-engineer
+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.
+  
+  <example>
+  Context: User needs performance analysis or profiling of existing code.
+  user: "Our API response times are too slow — can you identify bottlenecks?"
+  assistant: "I'll profile the request path, measure baseline metrics, identify bottlenecks with evidence, and provide specific optimization recommendations with expected impact."
+  <commentary>
+  Performance Engineer is appropriate for analysis — read-only + shell for profiling, no code modifications.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs benchmarking or load testing guidance.
+  user: "How does our database layer perform under high concurrency?"
+  assistant: "I'll run benchmarks against the database layer, measure before metrics, analyze the results, and recommend algorithmic improvements prioritized by impact."
+  <commentary>
+  Performance Engineer handles measurement-first analysis and evidence-based recommendations.
+  </commentary>
+  </example>
+model: inherit
+color: yellow
+maxTurns: 20
+tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["performance-engineer"])` to read the full methodology at delegation time.

package/claude/agents/platform-engineer.md

@@ -0,0 +1,40 @@
+---
+name: platform-engineer
+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.
+  
+  <example>
+  Context: User needs a new service scaffold built.
+  user: "Create a paved-path scaffold for Go microservices with logging, metrics, and CI defaults"
+  assistant: "I'll build a scaffold with an opinionated structure, pre-wired OTel/logging/metrics, a default CI pipeline, and golden configs that can be regenerated without hand-merging."
+  <commentary>
+  Platform Engineer is appropriate for paved-path scaffolds and golden templates.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a self-service environment flow reviewed.
+  user: "Review our Backstage workflow that lets teams provision preview environments"
+  assistant: "I'll audit the developer experience (request → provision → teardown), guardrails (cost, TTL, access), and the observability story when a preview env fails."
+  <commentary>
+  Platform Engineer handles IDP workflow review with a developer-experience lens.
+  </commentary>
+  </example>
+model: inherit
+color: emerald
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - Skill
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["platform-engineer"])` to read the full methodology at delegation time.

package/claude/agents/product-manager.md

@@ -0,0 +1,34 @@
+---
+name: product-manager
+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.
+  
+  <example>
+  Context: User needs requirements defined for a new feature.
+  user: "Write the PRD for our new team collaboration feature"
+  assistant: "I'll define the problem statement, target users, success metrics, user stories with acceptance criteria, and prioritized feature list using RICE scoring."
+  <commentary>
+  Product Manager handles requirements definition and feature prioritization.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs competitive analysis for product decisions.
+  user: "How does our pricing page compare to competitors in the analytics space?"
+  assistant: "I'll research competitor pricing models, feature comparisons, and positioning to identify differentiation opportunities and gaps."
+  <commentary>
+  Product Manager handles competitive analysis and strategic product decisions.
+  </commentary>
+  </example>
+model: inherit
+color: teal
+maxTurns: 20
+tools:
+  - Read
+  - Write
+  - Edit
+  - Glob
+  - Grep
+  - WebSearch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["product-manager"])` to read the full methodology at delegation time.

package/claude/agents/prompt-engineer.md

@@ -0,0 +1,38 @@
+---
+name: prompt-engineer
+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.
+  
+  <example>
+  Context: User needs a prompt designed with measurable output quality.
+  user: "Design a prompt that extracts invoice fields into structured JSON with high reliability"
+  assistant: "I'll draft the prompt with explicit schema, calibrated few-shot examples, and a fallback behavior for ambiguous fields, then propose an eval set that measures per-field accuracy and schema compliance."
+  <commentary>
+  Prompt Engineer is appropriate for structured-output prompt design with a measurement plan.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a RAG retrieval quality problem diagnosed.
+  user: "Our RAG answers cite the wrong chunks half the time"
+  assistant: "I'll audit chunking (size, overlap), the embedding model, the reranker, and the prompt's citation instruction, and propose an eval set with known-answer queries to quantify retrieval precision."
+  <commentary>
+  Prompt Engineer handles RAG pipeline quality tuning alongside prompt design.
+  </commentary>
+  </example>
+model: inherit
+color: lime
+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: ["prompt-engineer"])` to read the full methodology at delegation time.

package/claude/agents/refactor.md

@@ -0,0 +1,38 @@
+---
+name: refactor
+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.
+  
+  <example>
+  Context: User wants to improve code structure without changing behavior.
+  user: "Refactor our user service to extract the notification logic into a separate module"
+  assistant: "I'll restructure the code to separate concerns without changing behavior, verifying behavior preservation with the project's test suite."
+  <commentary>
+  Refactor is appropriate for structural improvements — behavior must be preserved, validated by tests.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs to reduce technical debt or improve maintainability.
+  user: "The auth module has grown too large and is hard to test — clean it up"
+  assistant: "I'll analyze the current structure, identify separation opportunities, and refactor in small steps while verifying each step preserves behavior."
+  <commentary>
+  Refactor handles maintainability improvements with a strict no-behavior-change constraint.
+  </commentary>
+  </example>
+model: inherit
+color: cyan
+maxTurns: 25
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - Skill
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["refactor"])` to read the full methodology at delegation time.