@josstei/maestro 1.6.4-nightly.20260430

package/claude/README.md

@@ -0,0 +1,191 @@
+# Maestro — Claude Code Plugin
+
+[![Version](https://img.shields.io/badge/version-1.6.4-blue)](https://github.com/josstei/maestro-orchestrate/releases)
+[![License](https://img.shields.io/badge/license-Apache-2.0-green)](LICENSE)
+[![Claude Code](https://img.shields.io/badge/Claude_Code-plugin-orange)](https://docs.anthropic.com/en/docs/claude-code)
+
+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
+
+## Installation
+
+### From Marketplace (recommended)
+
+Add the maestro marketplace, then install the plugin:
+
+```bash
+claude plugin marketplace add josstei/maestro-orchestrate
+claude plugin install maestro@maestro-orchestrator --scope user
+```
+
+### Installation Scopes
+
+| Scope | Flag | Effect |
+|-------|------|--------|
+| User (default) | `--scope user` | Available across all your projects |
+| Project | `--scope project` | Shared with your team via version control |
+| Local | `--scope local` | Project-specific, gitignored |
+
+### Plugin Management
+
+```bash
+claude plugin update maestro          # Pull the latest version
+claude plugin disable maestro         # Disable without uninstalling
+claude plugin uninstall maestro       # Remove the plugin entirely
+```
+
+### Development / Testing
+
+Load the plugin for a single session without persistent registration:
+
+```bash
+claude --plugin-dir /path/to/maestro-orchestrate/claude
+```
+
+Use `/reload-plugins` inside the session to pick up file changes without restarting.
+
+For local development, clone the repo first:
+
+```bash
+git clone https://github.com/josstei/maestro-orchestrate
+claude --plugin-dir /path/to/maestro-orchestrate/claude
+```
+
+### Verify Installation
+
+After starting Claude Code with the plugin loaded:
+
+- Type `/` and verify `orchestrate`, `review-code`, `debug-workflow`, `security-audit`, `perf-check`, `seo-audit`, `a11y-audit`, and `compliance-check` appear in autocomplete.
+- Run `/agents` and verify agents with the `maestro:` prefix appear (e.g., `maestro:coder`, `maestro:architect`).
+- Confirm MCP tools are registered: `mcp__plugin_maestro_maestro__*` tools should be available (e.g., `mcp__plugin_maestro_maestro__get_session_status`).
+
+### MCP Server
+
+The MCP server is auto-registered via `claude/.mcp.json`. If MCP tools are not available, verify the `.mcp.json` file exists at the plugin root:
+
+```json
+{
+  "mcpServers": {
+    "maestro": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/mcp/maestro-server.js"],
+      "cwd": "${CLAUDE_PLUGIN_ROOT}"
+    }
+  }
+}
+```
+
+**Note:** Claude is filesystem-backed for shared MCP content. Published Claude bundles carry a generated local `src/` payload derived from the canonical source tree, and shared skills, templates, references, and delegation protocols are loaded from that local payload through `get_skill_content`. Runtime-local `SKILL.md` files remain only where Claude needs on-disk discovery stubs or public entry points.
+
+## Quick Start
+
+Start a full orchestration by describing what you want to build:
+
+```
+/orchestrate Build a REST API for a task management system with user authentication
+```
+
+Maestro will walk you through the complete lifecycle:
+
+1. **Design Dialogue** -- Structured questions one at a time, 2-3 architectural approaches with trade-offs.
+2. **Design Review** -- Section-by-section approval of the design document.
+3. **Implementation Planning** -- Phase breakdown, agent assignments, dependency graph, parallel execution opportunities.
+4. **Execution Mode Selection** -- Parallel or sequential dispatch.
+5. **Phase-by-Phase Execution** -- Specialized agents implement the plan with session state updates after each phase.
+6. **Quality Gate** -- Final code review blocks on unresolved Critical or Major findings.
+7. **Completion & Archival** -- Summary of files changed, token usage, and next steps.
+
+**Express mode** -- For simple tasks, Maestro detects low complexity and uses a streamlined flow: 1-2 questions, brief approval, single agent, code review, done.
+
+## Commands
+
+| Command | Purpose |
+|---------|---------|
+| `/orchestrate` | Full orchestration workflow (design, plan, execute, complete) |
+| `/execute` | Execute an approved implementation plan |
+| `/status` | Display current session status |
+| `/resume-session` | Resume an interrupted session |
+| `/archive` | Archive the active session |
+| `/review-code` | Standalone code review |
+| `/debug-workflow` | Standalone debugging session |
+| `/security-audit` | Standalone security assessment |
+| `/perf-check` | Standalone performance analysis |
+| `/seo-audit` | Standalone SEO assessment |
+| `/a11y-audit` | Standalone accessibility audit |
+| `/compliance-check` | Standalone compliance review |
+
+These Claude entrypoints come from the public top-level skills in `skills/`. Internal methodology skills remain hidden with `user-invocable: false`.
+
+## Agents
+
+All agents are registered with a `maestro:` namespace prefix. When the orchestrator delegates work, it dispatches agents as `maestro:coder`, `maestro:architect`, etc. Claude Code agents use **kebab-case** naming (e.g., `code-reviewer`, `api-designer`), contrasting with Gemini CLI's snake_case convention (e.g., `code_reviewer`, `api_designer`). The `maestro:` prefix is always required when dispatching.
+
+All agents share a baseline tool set: `Read`, `Glob`, `Grep`, `Skill`. Tool tiers reflect additional capabilities beyond that baseline.
+
+| Agent | Domain | Specialization | Tool Tier |
+|-------|--------|----------------|-----------|
+| accessibility-specialist | Design | WCAG compliance auditing, ARIA review | Read + Shell |
+| analytics-engineer | Analytics | Event tracking, conversion funnels | Full Access |
+| api-designer | Engineering | API contracts and endpoint design | Read-Only |
+| architect | Engineering | System design and architecture decisions | Read-Only |
+| cloud-architect | Platform | AWS/GCP/Azure topology, IaC, multi-region design | Read-Only |
+| cobol-engineer | Mainframe | Mainframe COBOL, JCL, CICS/IMS on z/OS | Full Access |
+| code-reviewer | Engineering | Code quality review and bug identification | Read-Only |
+| coder | Engineering | Feature implementation | Full Access |
+| compliance-reviewer | Compliance | Legal and regulatory compliance (GDPR, CCPA, licensing) | Read-Only |
+| content-strategist | Content | Content planning and strategy | Read-Only |
+| copywriter | Content | Marketing copy and landing-page content | Read + Write |
+| data-engineer | Engineering | Schema design, queries, and data pipelines | Full Access |
+| database-administrator | Engineering | RDBMS tuning, indexes, migration safety (Postgres, MySQL, Oracle, SQL Server) | Read + Shell |
+| db2-dba | Mainframe | DB2 for z/OS and LUW, REORG, RUNSTATS, bind/rebind | Read + Shell |
+| debugger | Engineering | Root cause analysis and defect investigation | Read + Shell |
+| design-system-engineer | Design | Design tokens and theming | Full Access |
+| devops-engineer | Engineering | CI/CD, containerization, and deployment | Full Access |
+| hlasm-assembler-specialist | Mainframe | IBM HLASM for z/OS, macros, SVCs | Full Access |
+| i18n-specialist | Internationalization | Internationalization and locale management | Full Access |
+| ibm-i-specialist | Mainframe | IBM i RPG/CL, DB2 for i, OS/400 | Full Access |
+| integration-engineer | Platform | B2B APIs, ETL, message brokers (Kafka, MQ) | Full Access |
+| ml-engineer | ML/AI | Model training, feature pipelines, evaluation | Full Access |
+| mlops-engineer | ML/AI | Model registry, CI/CD for models, drift detection | Full Access |
+| mobile-engineer | Engineering | iOS/Android/React Native/Flutter platform work | Full Access |
+| observability-engineer | Ops | Metrics, logs, traces, OpenTelemetry, dashboards | Full Access |
+| performance-engineer | Engineering | Performance profiling and optimization | Read + Shell |
+| platform-engineer | Platform | Internal developer platforms, paved paths | Full Access |
+| product-manager | Product | Requirements and product strategy | Read + Write |
+| prompt-engineer | ML/AI | LLM prompt design, few-shot, RAG tuning | Read + Write |
+| refactor | Engineering | Structural refactoring and technical debt | Full Access |
+| release-manager | Ops | Release notes, changelogs, rollout planning | Read + Write |
+| security-engineer | Engineering | Security assessment and vulnerability analysis | Read + Shell |
+| seo-specialist | SEO | Technical SEO auditing and structured data | Read + Shell |
+| site-reliability-engineer | Ops | SLOs, error budgets, runbooks, postmortems | Read + Shell |
+| solutions-architect | Platform | Enterprise integration, cross-team architecture | Read-Only |
+| technical-writer | Engineering | Documentation and technical writing | Read + Write |
+| tester | Engineering | Test implementation and coverage analysis | Full Access |
+| ux-designer | Design | User experience design | Read + Write |
+| zos-sysprog | Mainframe | z/OS systems programming, JCL, USS, RACF | Read + Shell |
+
+## Claude Code Specifics
+
+### MCP Tool Names
+
+MCP tools are registered with a namespace prefix. Skills reference bare names like `initialize_workspace` but the actual tool name is `mcp__plugin_maestro_maestro__initialize_workspace`. The orchestrate skill includes a mapping table that handles this automatically.
+
+### Agent Names
+
+Agents are registered as `maestro:<agent-name>` (e.g., `maestro:coder`, `maestro:code-reviewer`). The orchestrate skill includes a mapping that handles this automatically.
+
+### Hooks
+
+Claude Code hooks are registered in `hooks/claude-hooks.json`:
+
+- **SessionStart** — Prune stale sessions, initialize hook state
+- **SessionEnd** — Clean up hook state
+- **PreToolUse (Agent matcher)** — Track active agent, inject session context
+- **PreToolUse (Bash matcher)** — Policy enforcement (blocks destructive commands)
+
+## Configuration
+
+Supported settings include `MAESTRO_STATE_DIR`, `MAESTRO_DISABLED_AGENTS`, `MAESTRO_EXECUTION_MODE`, `MAESTRO_VALIDATION_STRICTNESS`, `MAESTRO_AUTO_ARCHIVE`, `MAESTRO_MAX_RETRIES`, and `MAESTRO_MAX_CONCURRENT`. Claude-specific runtime paths come from `CLAUDE_PLUGIN_ROOT` and `CLAUDE_PROJECT_DIR`.
+
+## License
+
+Apache-2.0

package/claude/agents/accessibility-specialist.md

@@ -0,0 +1,36 @@
+---
+name: accessibility-specialist
+description: |
+  Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for WCAG 2.1 AA compliance, reviewing keyboard navigation in modal dialogs, or validating ARIA usage in custom components.
+  
+  <example>
+  Context: User needs a WCAG accessibility audit.
+  user: "Audit our web app for WCAG 2.1 AA compliance"
+  assistant: "I'll systematically audit against all WCAG 2.1 AA success criteria: perceivable (alt text, contrast, captions), operable (keyboard, timing), understandable (readability, predictability), and robust (parsing, ARIA)."
+  <commentary>
+  Accessibility Specialist handles WCAG compliance auditing — read-only + shell for a11y tools.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs keyboard navigation review.
+  user: "Check if our modal dialogs and dropdown menus are keyboard accessible"
+  assistant: "I'll review focus management, tab order, escape key handling, and ARIA roles for each interactive component, providing specific remediation patterns."
+  <commentary>
+  Accessibility Specialist handles keyboard accessibility and ARIA implementation review.
+  </commentary>
+  </example>
+model: inherit
+color: violet
+maxTurns: 20
+tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["accessibility-specialist"])` to read the full methodology at delegation time.

package/claude/agents/analytics-engineer.md

@@ -0,0 +1,38 @@
+---
+name: analytics-engineer
+description: |
+  Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding event tracking to a checkout flow, designing an A/B test for a pricing page, or defining KPI dashboards.
+  
+  <example>
+  Context: User needs to instrument a feature with analytics tracking.
+  user: "Add event tracking to our checkout flow to measure conversion funnel"
+  assistant: "I'll design the event taxonomy for the checkout funnel, implement tracking calls at each step, and validate data collection with test events."
+  <commentary>
+  Analytics Engineer handles tracking implementation and event schema design.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs A/B test design for a feature experiment.
+  user: "Design an A/B test for our new pricing page layout"
+  assistant: "I'll define test hypotheses, calculate sample size for statistical significance, design event tracking for both variants, and specify success metrics."
+  <commentary>
+  Analytics Engineer handles experiment design and measurement planning.
+  </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: ["analytics-engineer"])` to read the full methodology at delegation time.

package/claude/agents/api-designer.md

@@ -0,0 +1,33 @@
+---
+name: api-designer
+description: |
+  API design specialist for endpoint design, request/response contracts, and API versioning strategies. Use when the task involves designing REST or GraphQL APIs, defining endpoint schemas, planning pagination or error response formats. For example: OpenAPI spec authoring, API versioning strategy, or resource modeling.
+  
+  <example>
+  Context: User needs REST or GraphQL API contracts designed.
+  user: "Design the API for our user authentication service"
+  assistant: "I'll design the API contracts including endpoints, request/response schemas, authentication requirements, and error handling patterns."
+  <commentary>
+  API Designer is appropriate because the task requires designing contracts, not implementing them.
+  </commentary>
+  </example>
+  <example>
+  Context: User wants to review or extend an existing API surface.
+  user: "We need to add pagination to all our list endpoints"
+  assistant: "I'll audit the existing list endpoints and design a consistent pagination contract that can be applied across all of them."
+  <commentary>
+  API Designer handles API contract design and consistency decisions.
+  </commentary>
+  </example>
+model: inherit
+color: cyan
+maxTurns: 15
+tools:
+  - Read
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["api-designer"])` to read the full methodology at delegation time.

package/claude/agents/architect.md

@@ -0,0 +1,33 @@
+---
+name: architect
+description: |
+  System design specialist for architecture decisions, technology selection, and high-level component design. Use when the task requires evaluating architectural trade-offs, designing system components, selecting technology stacks, or planning service boundaries. For example: microservice decomposition, database schema design, or API contract planning.
+  
+  <example>
+  Context: User needs to design a new system or evaluate architectural trade-offs.
+  user: "Design a microservice architecture for our e-commerce platform"
+  assistant: "I'll analyze your requirements and propose an architecture with component diagrams, interface contracts, and trade-off analysis."
+  <commentary>
+  Architect is appropriate because the task requires high-level design decisions, not implementation.
+  </commentary>
+  </example>
+  <example>
+  Context: User is selecting technology stacks or evaluating options.
+  user: "Should we use PostgreSQL or MongoDB for our user data?"
+  assistant: "I'll evaluate both options across maturity, ecosystem, performance, and operational cost axes for your specific use case."
+  <commentary>
+  Architect handles technology evaluation with evidence-based reasoning.
+  </commentary>
+  </example>
+model: inherit
+color: blue
+maxTurns: 15
+tools:
+  - Read
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["architect"])` to read the full methodology at delegation time.

package/claude/agents/cloud-architect.md

@@ -0,0 +1,33 @@
+---
+name: cloud-architect
+description: |
+  Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS, designing a VPC topology, or evaluating a CDN/edge-compute strategy.
+  
+  <example>
+  Context: User needs a cloud topology designed or reviewed.
+  user: "Design the AWS topology for our multi-tenant SaaS with per-tenant isolation"
+  assistant: "I'll propose a landing-zone layout, per-tenant account/VPC isolation pattern, shared-services account, and tenant-lifecycle operations, with cost and blast-radius trade-offs."
+  <commentary>
+  Cloud Architect is appropriate for topology design and trade-off analysis; it does not write IaC.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs an IaC review for best practices.
+  user: "Review our Terraform modules for security and cost risks"
+  assistant: "I'll audit state handling, IAM least-privilege, tagging, data perimeter, and cost levers (autoscaling, spot, right-sizing), and list findings by severity."
+  <commentary>
+  Cloud Architect handles IaC pattern review, read-only.
+  </commentary>
+  </example>
+model: inherit
+color: sky
+maxTurns: 15
+tools:
+  - Read
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["cloud-architect"])` to read the full methodology at delegation time.

package/claude/agents/cobol-engineer.md

@@ -0,0 +1,38 @@
+---
+name: cobol-engineer
+description: |
+  COBOL engineering specialist for mainframe program development, maintenance, and modernization on z/OS. Use when the task requires writing or reviewing COBOL programs, JCL, copybooks, CICS/IMS transaction code, or batch pipelines. For example: implementing a new batch job, refactoring a monolithic COBOL program, or reviewing a copybook change for binary compatibility.
+  
+  <example>
+  Context: User needs a COBOL program implemented or reviewed for a mainframe batch job.
+  user: "Implement a nightly batch that reads the transactions VSAM file and produces a posting file"
+  assistant: "I'll structure the program with standard divisions, use the existing copybook for the transaction record, implement sequential processing with file status checks, and write JCL that allocates the datasets with correct DCB attributes."
+  <commentary>
+  COBOL Engineer is appropriate for batch program authoring and JCL wiring.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a copybook change reviewed for downstream binary impact.
+  user: "Review this copybook change adding a new field mid-structure"
+  assistant: "I'll check every program referencing this copybook, assess recompile-vs-runtime compatibility, and flag downstream impacts on unload files, MQ messages, and DB2 row layouts."
+  <commentary>
+  COBOL Engineer handles copybook/record-layout impact analysis across the mainframe estate.
+  </commentary>
+  </example>
+model: inherit
+color: maroon
+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: ["cobol-engineer"])` to read the full methodology at delegation time.

package/claude/agents/code-reviewer.md

@@ -0,0 +1,31 @@
+---
+name: code-reviewer
+description: |
+  Code review specialist for identifying bugs, security vulnerabilities, and code quality issues. Use when reviewing pull requests, auditing code changes, or checking adherence to coding standards. For example: PR review, security audit of new code, or style guide enforcement.
+  
+  <example>
+  Context: User wants a code review before merging or shipping.
+  user: "Review the authentication service implementation for correctness and quality"
+  assistant: "I'll review the implementation for correctness, SOLID principles, error handling, security concerns, and consistency with established patterns."
+  <commentary>
+  Code Reviewer is appropriate for review tasks — read-only analysis and recommendations.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a second opinion on implementation decisions.
+  user: "Can you check if our new API layer follows our conventions?"
+  assistant: "I'll read the existing codebase patterns and compare against the new API layer, identifying any deviations with specific line references."
+  <commentary>
+  Code Reviewer handles convention audits and targeted feedback.
+  </commentary>
+  </example>
+model: inherit
+color: blue
+maxTurns: 15
+tools:
+  - Read
+  - Glob
+  - Grep
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["code-reviewer"])` to read the full methodology at delegation time.

package/claude/agents/coder.md

@@ -0,0 +1,38 @@
+---
+name: coder
+description: |
+  Implementation specialist for writing clean, well-structured code following established patterns and SOLID principles. Use when the task requires feature implementation, writing new modules, or building out functionality from specifications. For example: building a new API endpoint, implementing a service class, or writing utility functions.
+  
+  <example>
+  Context: User needs a new feature implemented from a specification or design.
+  user: "Implement the user authentication service based on the API contracts we just designed"
+  assistant: "I'll implement the service following the interface-first workflow: types and contracts first, then dependencies before dependents, matching existing codebase patterns."
+  <commentary>
+  Coder is appropriate for feature implementation from a known specification.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs new modules or utility code built out.
+  user: "Build the repository layer for our User domain"
+  assistant: "I'll read existing repository implementations first to extract patterns, then implement the User repository following the same conventions."
+  <commentary>
+  Coder handles implementation tasks that require pattern matching and code writing.
+  </commentary>
+  </example>
+model: inherit
+color: green
+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: ["coder"])` to read the full methodology at delegation time.

package/claude/agents/compliance-reviewer.md

@@ -0,0 +1,33 @@
+---
+name: compliance-reviewer
+description: |
+  Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture, or license compatibility checks. For example: auditing an app for GDPR compliance, designing cookie consent that satisfies ePrivacy, or checking open-source license compatibility.
+  
+  <example>
+  Context: User needs GDPR compliance review for their web application.
+  user: "Review our app for GDPR compliance — we collect user data for analytics and marketing"
+  assistant: "I'll audit data collection practices, consent mechanisms, data subject rights implementation, and third-party data sharing. Findings will reference specific GDPR articles with remediation guidance."
+  <commentary>
+  Compliance Reviewer handles regulatory compliance auditing — advisory role with web research.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs cookie consent implementation guidance.
+  user: "We need to implement cookie consent that complies with EU ePrivacy and GDPR"
+  assistant: "I'll classify your cookies (necessary, analytics, marketing, functional), audit third-party scripts, and provide consent banner requirements with preference management specifications."
+  <commentary>
+  Compliance Reviewer handles cookie compliance and consent mechanism design.
+  </commentary>
+  </example>
+model: inherit
+color: maroon
+maxTurns: 15
+tools:
+  - Read
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["compliance-reviewer"])` to read the full methodology at delegation time.

package/claude/agents/content-strategist.md

@@ -0,0 +1,33 @@
+---
+name: content-strategist
+description: |
+  Content strategy specialist for content planning, editorial calendars, audience targeting, and content gap analysis. Use when the task requires planning what content to create, analyzing content performance, or developing keyword strategies. For example: building an editorial calendar, conducting content gap analysis, or defining content pillars for a product launch.
+  
+  <example>
+  Context: User needs a content strategy for a product launch.
+  user: "Plan the content strategy for our new developer tools platform launch"
+  assistant: "I'll analyze your target audience, map their information needs by journey stage, identify content gaps, and create a prioritized editorial plan with topics, formats, and distribution channels."
+  <commentary>
+  Content Strategist handles strategic content planning — advisory role with web research.
+  </commentary>
+  </example>
+  <example>
+  Context: User wants to audit and improve existing content.
+  user: "Our blog has 200 posts but traffic is flat — what should we focus on?"
+  assistant: "I'll audit your existing content for gaps, redundancies, and staleness, then produce a prioritized action plan: which posts to update, which gaps to fill, and which topics to retire."
+  <commentary>
+  Content Strategist handles content audits and optimization planning.
+  </commentary>
+  </example>
+model: inherit
+color: amber
+maxTurns: 15
+tools:
+  - Read
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["content-strategist"])` to read the full methodology at delegation time.

package/claude/agents/copywriter.md

@@ -0,0 +1,33 @@
+---
+name: copywriter
+description: |
+  Marketing copywriter for persuasive content, landing pages, CTAs, and brand voice consistency. Use when the task requires writing marketing copy, product descriptions, email campaigns, or user-facing content that drives action. For example: writing landing page hero text, crafting email subject lines, or creating product feature descriptions.
+  
+  <example>
+  Context: User needs marketing copy for a web product.
+  user: "Write the landing page copy for our new analytics dashboard product"
+  assistant: "I'll craft conversion-focused copy: hero section with value proposition, feature benefits, social proof placement, and CTAs — all calibrated to your target audience."
+  <commentary>
+  Copywriter handles persuasive marketing content creation.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs email campaign content.
+  user: "Write a 3-email onboarding sequence for new trial users"
+  assistant: "I'll create an onboarding sequence: welcome email, feature highlight, and conversion nudge — each with subject line variants, preview text, and clear CTAs."
+  <commentary>
+  Copywriter handles email marketing copy with conversion focus.
+  </commentary>
+  </example>
+model: inherit
+color: coral
+maxTurns: 20
+tools:
+  - Read
+  - Write
+  - Edit
+  - Glob
+  - Grep
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["copywriter"])` to read the full methodology at delegation time.

package/claude/agents/data-engineer.md

@@ -0,0 +1,37 @@
+---
+name: data-engineer
+description: |
+  Data engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline construction, or schema evolution. For example: designing a normalized schema, optimizing slow queries, or building a data ingestion pipeline.
+  
+  <example>
+  Context: User needs database schema design or migration work.
+  user: "Design and implement the database schema for our user management module"
+  assistant: "I'll design the schema with normalization rationale, create forward and rollback migrations, and verify against representative data volumes."
+  <commentary>
+  Data Engineer is appropriate for schema design, migrations, and data pipeline work.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs data pipeline or ETL work.
+  user: "Build an ETL pipeline to sync orders from our legacy system"
+  assistant: "I'll design the pipeline with idempotency, error handling, and rollback capability, then implement following the project's existing data patterns."
+  <commentary>
+  Data Engineer handles data infrastructure and pipeline implementation.
+  </commentary>
+  </example>
+model: inherit
+color: yellow
+maxTurns: 20
+tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["data-engineer"])` to read the full methodology at delegation time.

package/claude/agents/database-administrator.md

@@ -0,0 +1,37 @@
+---
+name: database-administrator
+description: |
+  Database administration specialist for RDBMS schema review, query tuning, index strategy, and migration safety on PostgreSQL, MySQL, SQL Server, and Oracle. Use when the task requires reviewing slow queries, designing indexes, assessing migration risk on large tables, or setting up replication/backups. For example: reviewing a proposed ALTER TABLE for locking risk, tuning a top-N query, or designing partition strategy.
+  
+  <example>
+  Context: User needs a slow query diagnosed and optimized.
+  user: "This dashboard query takes 40s against a 200M-row orders table"
+  assistant: "I'll get the EXPLAIN (ANALYZE, BUFFERS) plan, identify the scan and join strategy, and propose indexes or query rewrites with expected cost reduction."
+  <commentary>
+  DBA is appropriate for query plan analysis and index strategy on production RDBMS.
+  </commentary>
+  </example>
+  <example>
+  Context: User needs a schema change reviewed for locking and migration safety.
+  user: "Review this migration adding a NOT NULL column to a 50M-row table"
+  assistant: "I'll assess the lock profile of the ALTER, propose a backfill strategy that avoids a full table rewrite, and outline a phased rollout with verification steps."
+  <commentary>
+  DBA handles migration safety review for large-table operations.
+  </commentary>
+  </example>
+model: inherit
+color: navy
+maxTurns: 20
+tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - WebSearch
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+---
+
+Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["database-administrator"])` to read the full methodology at delegation time.