orchestrator

Plugin orchestrator from marketplace claude-team in grgrwlkr/claude-team. Commands read from the repo's manifest — 5 days ago.

Skills (1)

• orchestrator

  Run a task as a team of background Claude Code sessions with you as the lead — architect, analyst, researcher, designer, developer, qa, qa-lead, reviewer, design-reviewer, integrator — each in its own worktree, messaging each other directly, under guard rails you control. Use via /orchestrator <task

Subagents (10)

• analyst

  Business and systems analyst for an orchestrated team run — turns a task into a spec with testable acceptance criteria, a plan and the documentation that follows implementation. Spawned by the orchestrator skill as a background session; do not delegate to it directly.

• architect

  Architect for an orchestrated team run — first in every run that changes code, checks the project's architecture map (modules, dependencies, coupling, data flow) against the code and brings it up to date, designs the change against it, and updates the map after the change lands. Spawned by the orche

• design-reviewer

  Design reviewer for an orchestrated team run — checks that a developer's implementation matches the designer's brief, tokens and states, by screenshots of the running result, and delivers findings with the design reference and the screenshot for each. Proposes; the orchestrator judges. Spawned by th

• designer

  Designer for an orchestrated team run — UI, product screens, sites, game HUDs and menus, graphics, 3D asset briefs; delivers a design brief, tokens and assets a developer implements from. Self-contained: needs no design skills installed. Spawned by the orchestrator skill as a background session; do

• developer

  Developer for an orchestrated team run — implements one task from a spec in its own worktree, test-first, smallest change that solves it, and hands off with the three test runs as evidence. Spawned by the orchestrator skill as a background session; do not delegate to it directly.

• integrator

  Integrator and release engineer for an orchestrated team run — merges task branches into the base branch in dependency order, resolves conflicts, keeps CI green, bumps versions and writes the changelog. The only role allowed to merge into the base branch, and to push or clean it up when the run's pl

• qa-lead

  QA lead for an orchestrated team run — writes the acceptance tests for the whole change right after the spec, before any code, and at the end runs them on the integrated result and proposes whether the change is accepted. Owns the acceptance test paths; developers make them pass and never edit them.

• qa

  QA engineer for one developer task in an orchestrated team run — writes the task's test cases before the developer codes, so its TDD covers them, then audits the result for corner-cutting — skipped, weakened or hollow tests, mocks standing in for the unit, runs that were never real — and, when the b

• researcher

  Researcher for an orchestrated team run — answers questions about the outside world (library and API behaviour, versions, standards, prices, rules) from live sources with verbatim quotes, and stages the findings in a file for the analyst and developer. Spawned by the orchestrator skill as a backgrou

• reviewer

  Code reviewer for an orchestrated team run — reads a branch's diff for correctness, security and fit with the codebase and delivers findings with cited lines and a repro or reasoning for each. Proposes; the orchestrator judges. Spawned by the orchestrator skill as a background session; do not delega

Hooks (5)

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/guard.sh"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/guard.sh"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/guard.sh"

• PreToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/guard.sh"

• Stop

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/stop-gate.sh"

Similar plugins