Orchestrator Agent Kit

orchestrator-agent-kit

A 4-agent coding pipeline — **Architect → Developer → Tester → Reviewer** — driven by an **Orchestrator**, that coordinates entirely through plain files in `.agent-memory/`. No vendor lock-in: install it into [opencode](https://opencode.ai), [Claude Code](https://claude.com/claude-code), or GitHub Copilot Chat (VS Code) with a single command.

npx orchestrator-agent-kit install --target all

Why

AI coding tools are good at single-shot edits but weak at disciplined, multi-step feature work: planning gets skipped, tests mirror the implementation, and reviews rubber-stamp whatever was written.

This kit fixes that by imposing a **pipeline with hard gates and separation of concerns**:

• The planner never codes, the coder never tests, the tester never fixes, and the reviewer approves nothing silently.
• A mandatory plan-approval gate stops the pipeline until you sign off.
• All coordination happens through plain markdown/JSON files on disk — no proprietary APIs, no server, no lock-in. Any tool that reads/writes files can participate.

How it works

            ┌─────────────────────────────────────────────┐
            │                 ORCHESTRATOR                │
            │  (coordinates, manages state, enforces gate)│
            └──────┬──────────┬──────────┬──────────┬─────┘
                   ▼          ▼          ▼          ▼
              ┌────────┐ ┌─────────┐ ┌────────┐ ┌──────────┐
              │ARCHITECT│→│DEVELOPER│→│ TESTER │→│ REVIEWER │─┐
              └────────┘ └─────────┘ └────────┘ └──────────┘ │
                   ▲                                         │ changes-requested
                   └────────────── loop (max 3 iters) ───────┘

1. Orchestrator takes your feature request, writes it to .agent-memory/plan.md, initializes state.json, and delegates to the Architect.
2. Architect turns the requirement into a concrete plan — scope (in/o