ai-crew

ai-crew

A battle-tested, production-grade engineering orchestrator for Claude Code.

Describe the job. Approve the plan. Get the PR.

ai-crew encodes the workflows, quality gates, and best practices senior engineers run on every change — intake, spec, plan, build, verify, review, ship — and packages them as a Claude Code orchestrator for TypeScript, Node, backend, and React Native. An Opus team-lead reasons through every phase; scoped Sonnet developers handle implementation in sequence or in parallel; one human checkpoint sits between Plan and Build.

Built on top of Addy Osmani's agent-skills (vendored, MIT). See § Why this is different for what ai-crew adds on top.

Backstory

I love Superpowers and Addy Osmani's agent-skills, but I kept finding myself too much in the loop. All I wanted was to define the spec, approve the plan, and get a tested, working PR — not narrate the next step or remember which skill to invoke.

So I started with the obvious AI-team setup: architect, business analyst, QA lead, researcher, designer, developer, each as its own subagent. Burned tokens. Quality barely changed. So I cut them.

The unlock: main context stays lean. The orchestrator does analysis, spec, plan, and review inline. Only coding tasks and one-shot web research get delegated — the parts that benefit from a fresh, narrow context. Developers run in parallel when tasks are independent, in sequence when they're not.

That's ai-crew's team-lead. One brain at the wheel, scoping every task and delegating only what needs a fresh, narrow context. Guided Q&A for spec, and one human checkpoint for plan approval.

Demo

$ claude
> /team-lead Wire RevenueCat into our paywall, gate the premium tab, and track
              checkout events with our analytics SDK

ai-crew  [Intake — Q1 of 3]   one question at a time, A/B/C with tradeoffs
         How should the premium gate behave when a user without entitlement
         taps the tab?

         A. Hard gate — replace the tab entirely with the paywall
            (recommended: cleanest mental model, zero leakage of premium UI)
         B. Modal paywall over the existing tab; dismiss returns to free content
            (best if you have free content worth keeping inside the tab)
         C. Soft gate — inline teaser with a Subscribe CTA
            (highest conversion in some apps, mixed UX consistency)

You      B

ai-crew  [Q2 — RevenueCat SDK version?]  A: 4.x   B: 5.0   C: other
You      A

ai-crew  [Q3 — Analytics destination?]   A: Segment   B: Amplitude   C: custom
You      C — Mixpanel via our own wrapper

ai-crew  [Intake complete. Writing spec...]
         [spec.md written]
         [plan.md written — 6 tasks, 2 parallel waves]

         ✋  CHECKPOINT — review plan.md before I write a single file.
            Approve, or tell me what to change.

You      Looks good, go.

ai-crew  [Wave 1 — dispatching 3 parallel Sonnet developers...]
         [Wave 2 — dispatching 2 parallel Sonnet developers...]
         [Verify — all tests green]
         [Review — inline five-axis review, no critical findings]
         [Ship — PR opened]

         PR: https://github.com/your-org/your-app/pull/47
             "feat: RevenueCat paywall, premium gate, checkout analytics"

What you actually get

• A PR opened on a feature branch, with tests, ready to review.
• A written spec.md and plan.md before any code is touched — edit them if you want.
• One clear checkpoint: you approve the plan, then ai-crew runs without interruption.
• Tasks that can run in parallel are dispatched as concurrent Sonnet developers — no serial bottleneck on independent work.
• A five-axis review (correctness, readability, architecture, security, performance) done inline by the Opus team-lead before the PR opens.
• Max 3 fix loops on failures before the problem escalates back to you, never silently broken.

Quick Start

Click any tool to expand. Claude Code is the primary platform; the skills run anywhere agent-skills do.

/plugin marketplace add goktug/ai-crew
/plugin install ai-crew@ai-crew

git clone https://github.com/goktug/ai-crew.git
claude --plugin-dir /path/to/ai-crew

> /team-lead Migrate our Express auth middleware to JWT rotation, with tests and a rollback plan.