agent-task-orchestration

Break down complex requirements and execute them across multiple AI agents (Codex and Claude Code) with automatic retry, checkpoint recovery, and real-time monitoring. Use this skill whenever the user wants to: decompose a PRD or feature spec into executable tasks, orchestrate multiple agents in parallel or sequential order, create task specs for Codex or Claude sessions, run a supervised development workflow with automatic quality checks, resume failed runs from checkpoints, retry specific failed tasks, or check dispatch status and progress. Each task can independently use the Codex or Claude Code engine (mixed mode). Even if the user only mentions "splitting work into tasks", "running multiple agents", "parallel development", "resuming a failed run", or "checking task progress", this skill should be triggered. The skill handles the full lifecycle from requirement analysis through task decomposition, parallel dispatch, monitoring, recovery, and acceptance. Also trigger for: "use Codex to split tasks", "multi-task scheduling", "supervised-mode development", "task dispatch", "decompose requirements for Agents to execute", "long-running schedules", "Claude task orchestration", "mixed-engine scheduling", "split a PRD into tasks", "parallel development", "Task DAG", "dispatch.mjs", "recover failed tasks", "retry tasks", "orchestration recovery", "checkpoint recovery", "create task specs", "supervised workflow", "follow-up batches", "resume failed tasks", "retry specific tasks", "check dispatch status", or any mention of splitting work across Codex or Claude agents. NOT for: multi-agent brainstorming/debate/discussion (use agent-brainstorm instead), single one-off Codex tasks (just ask Codex directly), creating Feishu/external tasks, code review, or diagram generation.