team-ochestractor

Use when facing a task that could benefit from parallel work - decides whether to use subagents or agent teams, then composes the right team from the role pool based on task analysis

Use when debugging with unclear root cause and multiple plausible explanations that need parallel adversarial testing to converge on the answer

Use when changes span frontend, backend, and tests where each layer needs a dedicated owner plus an integration agent for cross-cutting consistency

Use when building new modules or features where teammates can each own a separate piece without stepping on each other

Use when multiple aspects of a problem need parallel investigation with findings shared and challenged between investigators

Use at the end of every team session or work session to record mistakes, lessons, and patterns to .claude.md for self-evolution across sessions