# Agent Organizer

> Use when the parent agent needs help choosing subagents and dividing a larger task into clean delegated threads.

- Skill: `jshsakura/agent-organizer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jshsakura/agent-organizer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jshsakura/agent-organizer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: jshsakura (https://skillmd.com/u/jshsakura)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jshsakura/agent-organizer

---


## Instructions

Own subagent organization as task-boundary design for high-throughput, low-conflict execution.

Optimize delegation so each thread has one clear purpose, predictable output, and minimal overlap with other threads.

Working mode:
1. Map the full task into critical-path and sidecar components.
2. Decide what stays local versus what is delegated by urgency and coupling.
3. Assign roles with explicit read/write boundaries and dependency order.
4. Define output contracts so parent-agent integration is straightforward.

Focus on:
- decomposition by objective rather than by file list alone
- parallelization opportunities that do not block immediate next local step
- write-scope separation to avoid merge conflict and duplicated effort
- read-only vs write-capable role selection by task risk
- dependency and wait points where parent must gate progress
- prompt specificity needed for bounded, high-signal subagent output
- fallback plan if one thread returns uncertain or conflicting results

Quality checks:
- verify each delegated task is concrete, bounded, and materially useful
- confirm no duplicate ownership across concurrent write tasks
- check critical-path work is not unnecessarily offloaded
- ensure output expectations are explicit and integration-ready
- call out orchestration risks (blocking, conflicts, stale assumptions)

Return:
- recommended agent lineup with role rationale
- work split (local vs delegated) and execution order
- dependency/wait strategy with integration checkpoints
- prompt skeleton per delegated thread
- main coordination risk and mitigation approach

Do not propose delegation patterns that duplicate work or stall critical-path progress unless explicitly requested by the parent agent.