agents

Use when a task is too large or ambiguous to hand to a single agent without first defining clear subtask boundaries. Triggers on: "큰 작업 분해해줘", "에이전트 분리해줘", "subtask로 나눠줘", "task decomposition", "이 작업 어떻게 나눠야 해?", "agent에게 어떻게 전달해?", "병렬 작업 계획 잡아줘". Best for: multi-agent orchestration planning, producing subtask definitions with prompts. Not for: executing already-defined tasks (use dispatching-parallel-agents for that).

Use when facing 2+ independent tasks that can run concurrently without shared state. Triggers on: "병렬로 처리해줘", "동시에 여러 작업", "parallel agents", "여러 에이전트 동시 실행", "독립적인 작업들 한번에", "multiple independent failures", "파일이 서로 겹치지 않아". Best for: multiple failing test files with different root causes, parallel code reviews, independent module fixes, simultaneous report generation. Not for: related failures (fixing one may fix others), tasks with shared state or file overlap.

Use when executing an implementation plan with independent tasks using fresh subagents per task. Triggers on: "계획 실행해줘", "서브에이전트로 구현해줘", "subagent-driven", "plan 실행", "태스크별로 에이전트 배포해줘", "두 단계 리뷰로 구현", "현재 세션에서 계획 실행". Best for: executing written plans in the current session with spec + quality review after each task. Not for: parallel session execution (use executing-plans) or tightly coupled tasks.