unicorn-team

10X Developer Unicorn

A Claude Code plugin that encodes the "hidden 80%" of software engineering expertise into 5 specialized agents and 14 composable skills — now with cost-aware model tiering, MCP-aware routing, and workflow fan-out.

What Is This?

Most AI coding tools help with the visible 20% -- writing code, answering syntax questions, generating boilerplate. But experienced developers spend 80% of their effort on skills that are rarely taught: reading code strategically, recognizing cross-domain patterns, estimating with risk awareness, self-reviewing before anyone sees the code, and managing technical debt deliberately.

This plugin encodes those skills into a coordinated agent team that Claude Code uses automatically.

New in v3.0

• Cost-aware model tiering — the orchestrator routes each delegation to the lowest model tier that does the job correctly (haiku → sonnet → opus, with fable reserved for the single hardest task and a free local-codegen tier below them all).
• MCP-aware routing — discovers the MCP servers you have configured and routes to them (code generation → local-codegen, library docs → context7, browser testing → playwright, memory → memory), degrading gracefully when they're absent.
• Workflow fan-out — ships three ready workflow templates (/review, /feature, /research) for multi-agent passes with adversarial verification, installable into .claude/workflows/.
• Goal-based delegation — prompts are written as objectives (Goal / Context / Constraints / Definition of done) instead of micro-steps, which the higher reasoning tiers handle better.

Install

# Add the marketplace
claude plugin marketplace add aj-geddes/unicorn-team

# Install the plugin
claude plugin install unicorn-team@unicorn-team

Done. Claude Code discovers all 14 skills, registers event hooks, and activates the orchestrator.

To register the bundled workflow templates as slash commands in a project:

# from your project root, after installing the plugin
./.claude/plugins/.../skills/orchestrator/scripts/install-workflows.sh
# (or ask Claude: "install the unicorn workflow templates")

How It Works

You make a request. The orchestrator picks an execution surface (a direct answer, a single agent, parallel agents, or a workflow), routes each delegation to the cheapest correct model tier, uses any MCP servers you have configured, and enforces quality gates on the result.

flowchart TB
    User([User Request])

    subgraph Orchestrator["ORCHESTRATOR (skill, main loop)"]
        O["Pick surface: direct / agent / workflow\nPick model tier: haiku→sonnet→opus→fable\nDiscover + route to MCP servers\nEnforce quality gates"]
    end

    subgraph Agents["AGENT TEAM (fresh 200K context each)"]
        direction LR
        AR["Architect\nopus"]
        DV["Developer\nsonnet"]
        QA["QA-Security\nsonnet"]
        DO["DevOps\nsonnet"]
        PG["Polyglot\nopus"]
    end

    subgraph Surfaces["EXECUTION SURFACES"]
        direction LR
        AG["Agent tool\n1–4 delegations"]
        WF["Workflow tool\nfan-out + verify"]
    end

    QG{{"Quality Gates\ntests pass · coverage ≥ 80%\nself-review · QA approved"}}

    User --> O
    O --> AG & WF
    AG & WF --> AR & DV & QA & DO & PG
    AR & DV & QA & DO & PG --> QG
    QG --> Result([Result + Proof])

    style Orchestrator fill:#313244,stroke:#cba6f7,stroke-width:2px,color:#ffffff
    style Agents fill:#313244,stroke:#fab387,stroke-width:2px,color:#ffffff
    style Surfaces fill:#313244,stroke:#89b4fa,stroke-width:2px,color:#ffffff
    style QG fill:#45475a,stroke:#a6e3a1,stroke-width:2px,color:#ffffff

Every implementation follows strict TDD:

flowchart LR
    R["RED\nWrite failing test"]
    G["GREEN\nMinimum code to pass"]
    F["REFACTOR\nImprove, tests still green"]
    V["VERIFY\nSelf-review + coverage"]

    R --> G --> F --> V -->|Next feature| R

    style R fill:#f38ba8,stroke:#f38ba8,color:#1e1e2e
    style G fill:#a6e3a1,stroke:#a6e3a1,color:#1e1e2e
    style F fill:#89b4fa,stroke:#89b4fa,color:#1e1e2e
    style V fill:#cba6f7,stroke:#cba6f7,color:#1e1e2e

Cost-Aware Model Tiering

The orchestrator routes each delegation to the lowest tier that produces a correct result, overriding the agent's default model per-invocation. Raise effort within a tier before jumping tiers, and escalate only behind a cheap verifier (tests/lint) — otherwise start at the right tier.