Expert orchestrator of agentic teams. The ticket contract defines work. The verification harness rules completion.
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.
/plugin marketplace add maxtechera/orchestrator
claude plugin update orchestrator@orchestrator
clawhub install orchestratorgit clone https://github.com/maxtechera/orchestrator.git ~/.claude/skills/orchestratorThe 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 below for a copy-paste template.
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.
Start using /orchestrator immediately. Add integrations when you want more domains.
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.
/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:
mkdir -p ~/.config/orchestrator && chmod 700 ~/.config/orchestratorThen add to ~/.config/orchestrator/.env:
# Add to ~/.config/orchestrator/.env
BOARD_PROVIDER=linear # or: github, notion, jira
LINEAR_API_KEY=lin_api_xxxxx # swap for your tracker's keyDomain 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 and 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 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
Connect your Shopify store for automated price, inventory, and product verification.
# Add to ~/.config/orchestrator/.env
SHOPIFY_ACCESS_TOKEN=shpat_xxxxxFree tier at mailerlite.com. Enables email sequence verification — link checks, segment validation, send tests.
# Add to ~/.config/orchestrator/.env
MAILERLITE_API_KEY=xxxxxFree tier at apollo.io. Enables lead sourcing verification — bounce rate, compliance, sequence validation.
# Add to ~/.config/orchestrator/.env
APOLLO_API_KEY=xxxxx# 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 publishingThe orchestrator validates every connection before dispatching. Missing integrations fail early with a clear message — not midway through execution.
| 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 | Free tier | Yes, for sales. Lead sourcing, outreach. |
| Free (Graph API) | Optional. Post publishing, carousels. | |
| Meta Ads | Paid | Optional. Campaign management. |
| Google Ads | Paid | Optional. Campaign management. |
| HubSpot | Free tier | Optional. CRM, pipeline. |
| GA4 | Free | Optional. Analytics, conversions. |
| Stripe | Paid | Optional. Payment verification. |
| QuickBooks | Paid | Optional. Invoicing, AR. |
| Xero | Paid | Optional. Alternative to QuickBooks. |
| Zendesk | Paid | Optional. Ticket management. |
| MercadoLibre | Free | Optional. LATAM marketplace listings. |
| GitHub | Free | For engineering. PRs, CI, deployments. |
All credentials stored locally in ~/.config/orchestrator/.env. Never transmitted. The orchestrator detects available MCP servers first and uses them when available — the .env is a fallback.
The orchestrator receives no money from any integration provider — no referrals, no kickbacks.
# Global config
~/.config/orchestrator/.env # API keys and credentials (chmod 600 recommended)
~/.orchestrator/skills/ # Installed domain skill files
~/.orchestrator/rules/ # Accumulated operational rules (grow automatically)
~/.orchestrator/history/ # Outcome logs for self-improvementThe Manual install works for Codex CLI, Gemini CLI, and OpenCode — clone to ~/.agents/skills/orchestrator and the skill is discovered via SKILL.md. Add credentials to ~/.config/orchestrator/.env.
/orchestrator sweep Process all actionable tickets
/orchestrator sweep TICKET-046 Re-run a single ticket
/orchestrator status Current ticket states and verification results
/orchestrator review 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 This week's pass/fail rate, ticket count, cost
Reviewing verified work: When tickets land in Review, run /orchestrator review to see the verification report — what passed, what failed, and the evidence. Then approve, reject with a note, or approve with a note. This is your only daily touchpoint.
When rules are proposed: After repeated failures with the same root cause, the system proposes a new rule in the review output and via /orchestrator rules --pending. Approve or reject inline. Approved rules are added to the skill file and apply to all future tickets.
Three steps, every ticket:
- Dispatch — read the board, prioritize by proximity to done (Review > Verification > In Progress stale > Todo), match to domain skill, validate integrations, dispatch worker agent
- Verify — separate verification pass with fresh context. Automated checks (API assertions, link validation, test suites) + AI judgment (brand voice, content quality). The verifier never knows how the work was done — no confirmation bias.
- Proof — verification report posted to ticket with evidence. PASS → Done. PARTIAL → Review (human decides). FAIL → auto-retry with failure context, or escalates to Review.
The harness is the invariant. The worker changes. The verification contract never does.
Add the four sections as markdown headers (## Inputs, ## Deliverables, ## Verification, ## Artifacts) in your ticket description. Copy this to your board and run /orchestrator sweep:
Publish SEO blog post
## Inputs
Keyword brief "AI agent verification", brand voice guide, 3 competitor URLs
## Deliverables
Blog post published on CMS, meta tags set, internal links added
## Verification
Page returns 200, word count > 1,500, SEO score green, no brand violations
## Artifacts
Published URL, screenshot of live page
What to expect on your first sweep:
- Tickets with all four sections get dispatched
- Tickets missing sections get moved to Backlog with a comment explaining what's needed
- If none of your tickets are in this format, the orchestrator tells you and offers to help reformat them
More templates for every domain in docs/VISION.md.
After the orchestrator verifies a ticket, this is posted to the ticket:
## Verification Report — TICKET-043
Status: PASS ✓
Checks:
✓ Page returns 200 (automated — 0.3s)
✓ Word count: 1,847 > 1,500 (automated — 0.1s)
✓ SEO score: 92/100, green (automated — 1.2s)
✓ Meta title set, under 60 chars (automated — 0.1s)
✓ og:image present and resolves (automated — 0.4s)
✓ 3 internal links found (automated — 0.2s)
✓ Brand voice check: consistent, no violations (AI judgment — 2.1s)
Evidence:
- Screenshot: live page captured
- Lighthouse report: attached
- All links validated: 3/3 resolve
Result: PASS — moved to Done
Domain skills extend the orchestrator with specialized verification rules for specific work types. Each skill is a composition wrapper — it adds domain rules and verification criteria on top of the base harness.
| Skill | What it adds | Plugin |
|---|---|---|
| content | Brand voice, format specs, engagement baseline | maxtechera/skill-content |
| ecommerce | Price/compare-at checks, image count, Shopify API | maxtechera/skill-ecommerce |
| seo | Meta limits, word count, Lighthouse, GSC inspection | maxtechera/skill-seo |
| engineering | Build/test/lint/CI gates, PR required, no self-merge | Built-in (agent default) |
Full skill list and composition chains: skills/README.md
Harness over trust — the verification harness rules completion. No evidence, no done. This is the invariant.
The ticket contract — every ticket has four sections: Inputs, Deliverables, Verification, Artifacts. Missing any → rejected to Backlog with guidance. Full spec.
Finishing beats starting — tickets closest to done get dispatched first.
Self-improving harness — every failure becomes a rule. Skills evolve, verification hardens, rules accumulate. All version-controlled. You approve every change.
Fail visible — nothing ships without passing verification. Blocked tickets include a structured reason. Partial failures are caught. The system fails visibly, not silently.
orchestrator/
SKILL.md # Core orchestrator skill — the agent reads this
WORKFLOW.md # Ticket lifecycle (intake → execute → verify → done)
.claude-plugin/ # Claude Code marketplace manifests
.codex-plugin/ # Codex CLI discovery
.agents/ # OpenCode/OpenClaw skill discovery
gemini-extension.json # Gemini CLI extension manifest
.clawhubignore # Distribution exclusions
.env.example # All configuration variables
CHANGELOG.md # Release history
docs/
VISION.md # Vision deck — the full story
STATE_MACHINE.md # Ticket state transitions (detailed)
skills/ # Domain skill directory
examples/ # Example workflows and tickets
- Your ticket board is the single source of truth
- The executor and the verifier are always different
Doneis fail-closed: no evidence, no completion- The system fails visibly, not silently
- Finishing beats starting
- You define the boundaries. The system operates inside them.
Read the full north star document: docs/VISION.md
One board. Any domain. Verified output. The operator's leverage finally scales.
MIT