@josstei/maestro 1.6.4-rc.1

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.

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.