# orchestrator

Adopt this skill: https://proskills.md/skills/other/maxtechera-orchestrator

Page: https://proskills.md/skills/other/maxtechera-orchestrator
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: SKILL.md
size: 8055
upstream: https://github.com/maxtechera/orchestrator/blob/HEAD/SKILL.md

````text
---
name: orchestrator
version: "1.0.0"
description: "Expert orchestrator of agentic teams. Ticket contract defines work. Independent verification harness rules completion."
argument-hint: 'orchestrator sweep, orchestrator status, orchestrator review, orchestrator setup'
allowed-tools: Bash, Read, Write, Edit, Glob, Grep, Agent, AskUserQuestion, WebSearch
homepage: https://github.com/maxtechera/orchestrator
repository: https://github.com/maxtechera/orchestrator
author: maxtechera
license: MIT
user-invocable: true
triggers:
  - orchestrator
  - orchestrator sweep
  - orchestrator setup
  - sweep board
  - process tickets
metadata:
  openclaw:
    emoji: "🎯"
    requires:
      env: []
      optionalEnv:
        - BOARD_PROVIDER
        - LINEAR_API_KEY
        - GH_TOKEN
        - NOTION_API_KEY
        - JIRA_API_TOKEN
        - SHOPIFY_ACCESS_TOKEN
        - MAILERLITE_API_KEY
        - INSTAGRAM_ACCESS_TOKEN
        - META_ADS_TOKEN
        - GOOGLE_ADS_TOKEN
        - APOLLO_API_KEY
        - HUBSPOT_API_KEY
        - GA4_PROPERTY_ID
        - STRIPE_SECRET_KEY
        - QUICKBOOKS_TOKEN
        - ZENDESK_TOKEN
        - MERCADOLIBRE_TOKEN
        - XERO_TOKEN
        - DEFAULT_MODEL
      bins: []
    primaryEnv: ""
    files: []
    tags:
      - orchestration
      - dispatch
      - verification
      - multi-domain
      - autonomous
      - skill-first
      - self-improving
---

# The Orchestrator

Expert orchestrator of agentic teams. Define the ticket contract — the verification harness rules completion.

Dispatch agents. Verify deliverables independently. Improve with every cycle.

> Full vision and depth: [docs/VISION.md](docs/VISION.md)

## Commands

```
/orchestrator sweep                            Process all actionable tickets
/orchestrator sweep TICKET-046                 Re-run a single ticket
/orchestrator status                           Show current ticket states and verification results
/orchestrator review                           Show tickets awaiting your review (pre-verified)
/orchestrator approve TICKET-044               Approve → Done
/orchestrator approve TICKET-044 --note "..."  Approve with a note
/orchestrator reject TICKET-044 --note "..."   Reject → back to execution with your feedback
/orchestrator approve-rule "..."               Approve a proposed rule into the skill
/orchestrator reject-rule "..."                Reject a proposed rule
/orchestrator rules --pending                  List proposed rules awaiting approval
/orchestrator flag TICKET-XXX "description"    Report a verification false negative
/orchestrator setup                            Connect your board and validate integrations
/orchestrator stats                            Show this week's pass/fail rate, ticket count, cost
```

## Team Mode

Run a zero-idle agent team instead of single-dispatch. Use when your board has a sprint — 3+ related tickets with different role requirements.

```
/orchestrator team
```

Reads your sprint tickets, spawns a named team, and keeps every agent busy at all times.

**Team lifecycle:**
1. Read sprint tickets from board grouped by role/domain
2. `TeamCreate team_name="<project-sprint>"` — creates the team context
3. Spawn agents by role — code agents with `isolation="worktree"`, strategy/research without
4. Assign 2 tasks per agent: **primary** (current sprint) + **secondary** (next sprint prep)
5. On completion → `SendMessage` with next assignment — never re-spawn, never idle
6. `/loop 10m /orchestrator` — continuous status visibility without blocking
7. Sprint close: bundle worktree branches → single PR → CI → merge → measure → pull next sprint

**Zero-idle rule:** Every agent always has a primary and secondary task. When primary completes, secondary promotes and a new secondary is assigned from the backlog. No agent ever waits.

**Roster pattern (adapt to your project):**

| Agent | Isolation | Focus |
|-------|-----------|-------|
| `builder` | worktree | Feature code, integrations |
| `designer` | worktree | UI, landing pages, copy |
| `tester` | worktree | E2E specs (written before code lands) + regression |
| `strategist` | none | Content, positioning, sequences |
| `analyst` | none | Metrics, attribution, funnel |

**Key difference from sweep:** `/orchestrator sweep` dispatches one agent per ticket sequentially. `/orchestrator team` runs all agents in parallel with role specialization and zero-idle coordination.

**Independent verification still applies:** The verifier agent remains separate — the agent that did the work never grades its own homework. In team mode, `tester` handles verification for code; a separate verifier pass runs on final deliverables.

## How It Works

1. Read the board — identify tickets in actionable states
2. Prioritize — tickets closest to done come first (Review before Todo)
3. For each ticket:
   - Validate the ticket contract (Inputs, Deliverables, Verification, Artifacts)
   - Match to an installed domain skill (or use base agent capabilities)
   - Confirm required integrations are connected
   - Dispatch a worker agent with the skill loaded
4. Worker executes independently
5. Separate verification step runs (fresh context, zero knowledge of how work was done)
6. Verification report posted to ticket with evidence
7. Ticket moves to Done (pass), Review (needs human), or retries with failure context (failed check)

## The Ticket Contract

Every ticket has four required sections:

- **Inputs** — what the agent needs to start
- **Deliverables** — what "done" looks like, concretely
- **Verification** — how to confirm the work is correct
- **Artifacts** — proof that the work exists in the real world

Missing any section → ticket rejected to Backlog with a comment explaining what's needed.

## Verification

The agent that did the work never grades its own homework.

**Automated data checks:** real API calls, exact-match assertions, link validation, test suites. Strong and reliable.

**AI quality checks:** brand voice, content quality, visual inspection. Separate agent, fresh context, no bias. Better than self-checking, but not infallible.

The system moves checks from AI judgment to automated over time. Every check that CAN be automated BECOMES automated.

## Self-Improving

Every failure becomes a rule:

1. **Skill refinement** — repeated failures trigger proposed patches (you approve/reject)
2. **Verification hardening** — missed checks get added to domain verification
3. **Rule accumulation** — operational rules across all skills, version-controlled

## Failure Handling

- Nothing ships without passing verification
- Blocked tickets include a structured reason
- Destructive actions require approval rules you configure once
- Partial failures are caught and flagged
- Failed verification triggers auto-retry with failure context; if retry fails, escalates to Review
- System crash → tickets stay in last known state, next sweep picks up

## Board Support

Works with any issue tracker. Run `/orchestrator setup` to connect:

- Linear
- GitHub Issues
- Notion
- Jira

## Core Skills

| Skill | Plugin |
|-------|--------|
| Content production | `maxtechera/skill-content` |
| E-commerce operations | `maxtechera/skill-ecommerce` |
| SEO | `maxtechera/skill-seo` |
| Sales outreach | `maxtechera/skill-sales-outreach` |
| Financial reporting | `maxtechera/skill-finance` |
| Growth | `maxtechera/skill-growth` |
| Go-to-market launches | `maxtechera/skill-gtm` |
| Engineering | Built-in (agent default) |

### Starter Templates

| Skill | Plugin |
|-------|--------|
| Customer support | `maxtechera/skill-support` |
| Paid acquisition | `maxtechera/skill-paid-ads` |
| Brand design | `maxtechera/skill-brand` |
| Research / competitive intel | `maxtechera/skill-research` |

## Configuration

> The orchestrator detects available MCP servers (Linear, GitHub, etc.) and uses them when available. The .env file is a fallback for environments without MCP support.

```
~/.config/orchestrator/.env       # A
````

## File: README.md
upstream: https://github.com/maxtechera/orchestrator/blob/HEAD/README.md

````text
# /orchestrator

[![GitHub stars](https://img.shields.io/github/stars/maxtechera/orchestrator?style=flat&label=GitHub%20stars)](https://github.com/maxtechera/orchestrator/stargazers)
[![Proof-driven workflow](https://img.shields.io/badge/proof--driven-verified%20delivery-2563eb)](https://github.com/maxtechera/orchestrator/blob/main/README.md#orchestrator)
[![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
[![Version](https://img.shields.io/badge/version-1.0.0-green.svg)](CHANGELOG.md)

**Verified AI-agent workflow orchestrator for Claude Code. Dispatch workers, run independent checks, ship only what passes.**

Claude Code:
```
/plugin marketplace add maxtechera/orchestrator
```

OpenClaw:
```
clawhub install orchestrator
```

Zero config. Run `/orchestrator sweep` immediately — if no board is connected, the setup wizard runs automatically.

---

## Install

### Claude Code

#### Install
```
/plugin marketplace add maxtechera/orchestrator
```

#### Update
```
claude plugin update orchestrator@orchestrator
```

### OpenClaw
```bash
clawhub install orchestrator
```

### Manual
```bash
git clone https://github.com/maxtechera/orchestrator.git ~/.claude/skills/orchestrator
```

**The agent that did the work never grades its own homework.** A separate verification pass runs with fresh context — real API calls, screenshots, link checks, compliance validation. Not another AI saying "looks good."

**The core pattern:** Ticket contract (Inputs / Deliverables / Verification / Artifacts) → dispatch worker agent → independent verifier → evidence posted to ticket. One cycle, every ticket.

**Best for:** operators running agentic teams who want verified output, not just agent output.

That's it. Run `/orchestrator sweep` to get started. If no board is connected, the orchestrator will prompt you to run `/orchestrator setup`. See [Your First Ticket](#your-first-ticket) below for a copy-paste template.

## Learn `/orchestrator`

Want the full operating system behind reliable agent teams?

- **Course:** [`/orchestrator` course outline](docs/course-outline.md)
- **Free lesson workbook:** [The context-limit wall and why single-agent workflows break](docs/sample-lessons/module-1-lesson-1-context-limit-wall.md)
- **Paid course CTA:** **Aprendé a orquestar equipos de agentes → curso `/orchestrator` ($197)**

The free OSS skill helps you run the workflow. The paid course teaches you how to design the contracts, memory, reliability layers, and production patterns behind it.

### Marketplace packaging playbooks

If you are preparing a companion skill or repo for Claude Code marketplace submission, use these proof-first packaging docs:

- [Memory marketplace optimization package](docs/memory-marketplace-package.md)
- [MAX-534 proof pack](artifacts/MAX-534/proof-pack.md)

The memory package includes the final GitHub description, topic set, social preview card, manifest verification checklist, and install steps to copy into the target repo README before submitting.

---

## What people use it for

**Running a content operation.** `/orchestrator sweep` reads all open tickets, dispatches content agents loaded with your brand voice, and independently verifies every deliverable before marking it done. Not just "here's a draft" — checked output.

**Managing an e-commerce store.** Set `BOARD_PROVIDER=linear` and connect Shopify. The orchestrator processes inventory updates, price changes, and product listings — and verifies prices, compare-at fields, and image counts before closing tickets.

**Engineering ticket flow.** `/orchestrator sweep` picks up GitHub Issues, runs domain-specific verification (link checks, schema validation, test presence), and only marks tickets done when the deliverable actually passes.

**Auditing before a release.** `/orchestrator review <ticket>` independently checks a specific deliverable. The agent that did the work never grades its own homework.

---

## Setup: Progressive Integration Unlocking

Start using `/orchestrator` immediately. Add integrations when you want more domains.

### 1. Zero Config (built-in skills) — Just install

Run `/orchestrator sweep`. The orchestrator uses your existing board connections (MCP servers for Linear, GitHub, etc.) and built-in agent capabilities. No API keys, no configuration. If no board is detected, you'll be prompted to run `/orchestrator setup`.

### 2. Run the setup wizard (connect your board)

```
/orchestrator setup
```

The setup wizard detects your environment, connects your issue tracker, and validates integrations. Takes about 30 seconds. Supports Linear, GitHub Issues, Notion, and Jira. It writes `BOARD_PROVIDER` and your API key to `~/.config/orchestrator/.env`.

If you prefer manual config:

```bash
mkdir -p ~/.config/orchestrator && chmod 700 ~/.config/orchestrator
```

Then add to `~/.config/orchestrator/.env`:

```bash
# Add to ~/.config/orchestrator/.env
BOARD_PROVIDER=linear        # or: github, notion, jira
LINEAR_API_KEY=lin_api_xxxxx  # swap for your tracker's key
```

### 3. Add domain skills (RECOMMENDED — the single most impactful upgrade)

**Domain skills give agents real expertise** — domain-specific rules, verification criteria, and best practices learned from actual executions. Without them, agents use general capabilities. With them, they follow rules like "carousel images must be 1080x1350" and "always verify compare-at price is cleared when not on sale."

Domain skills are **composition wrappers** — they load [`maxtechera/ship`](https://github.com/maxtechera/ship) and [`maxtechera/memory`](https://github.com/maxtechera/memory) skills and add domain-specific verification rules on top. Install ship and memory first, then the domain skill activates their capabilities for orchestrator verification. See [skills/README.md](skills/README.md) for the full list and their composition chains.

```
/plugin marketplace add maxtechera/skill-content
/plugin marketplace add maxtechera/skill-ecommerce
/plugin marketplace add maxtechera/skill-seo
```

### 4. Add Shopify (e-commerce verification)

Connect your Shopify store for automated price, inventory, and product verification.

```bash
# Add to ~/.config/orchestrator/.env
SHOPIFY_ACCESS_TOKEN=shpat_xxxxx
```

### 5. Add MailerLite (content/newsletter verification)

Free tier at [mailerlite.com](https://mailerlite.com). Enables email sequence verification — link checks, segment validation, send tests.

```bash
# Add to ~/.config/orchestrator/.env
MAILERLITE_API_KEY=xxxxx
```

### 6. Add Apollo (sales verification)

Free tier at [apollo.io](https://apollo.io). Enables lead sourcing verification — bounce rate, compliance, sequence validation.

```bash
# Add to ~/.config/orchestrator/.env
APOLLO_API_KEY=xxxxx
```

### 7. Optional integrations

```bash
# Add to ~/.config/orchestrator/.env
META_ADS_TOKEN=xxxxx          # Meta Ads — campaign management
GOOGLE_ADS_TOKEN=xxxxx        # Google Ads — campaign management
GA4_PROPERTY_ID=xxxxx         # Google Analytics — conversions
HUBSPOT_API_KEY=xxxxx         # HubSpot — CRM, pipeline
STRIPE_SECRET_KEY=xxxxx       # Stripe — payment verification
QUICKBOOKS_TOKEN=xxxxx        # QuickBooks — invoicing, AR
XERO_TOKEN=xxxxx              # Xero — alternative to QuickBooks
ZENDESK_TOKEN=xxxxx           # Zendesk — support ticket management
MERCADOLIBRE_TOKEN=xxxxx      # MercadoLibre — LATAM marketplace
INSTAGRAM_ACCESS_TOKEN=xxxxx  # Instagram Graph API — post publishing
```

The orchestrator validates every connection before dispatching. Missing integrations fail early with a clear message — not midway through execution.

---

### Do I need API keys?

| Integration | Free? | Do you need it? |
|-------------|-------|-----------------|
| Issue tracker | Free | **Yes — pick one.** Linear, GitHub Issues, Notion, or Jira. |
| Shopify | Paid | **Yes, for e-commerce.** Product pages, pricing, inventory. |
| MailerLite | Free tier | **Yes, for content.** Email sequences, newsletters. |
| Apollo |
````
