← ClaudeAtlas

spawning-planlisted

Spawning Plan. Use when user wants to spawn agents, create a team, or coordinate multiple agents. Automatically gathers context, asks team topology questions, outputs clean TEAM PLAN markdown, and gets user approval. 3 steps: context gathering -> questions -> present plan. Requires Claude Code with Agent Teams support.
citedy/skills · ★ 1 · Data & Documents · score 72
Install: claude install-skill citedy/skills
# Spawning Plan Design the optimal agent team for the task. Performant, precise, minimal. > **Note:** This skill requires Claude Code with Agent Teams support (TeamCreate, TaskCreate, SendMessage tools). **Task:** `$ARGUMENTS` ## Step 1: Context Gathering (Silent -- no user interaction) **A) Read environment:** - `CLAUDE.md` -- workflow rules, conventions, constraints - Project manifests -- `package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, etc. - Directory structure -- `src/`, `app/`, `packages/`, test dirs, monorepo indicators **B) Inventory existing agents:** - Scan `~/.claude/agents/*.md` -- reuse matching agents instead of creating duplicates **C) Analyze task complexity:** - **Work type**: research, implementation, review, debugging, refactoring - **Scope**: single-layer vs cross-layer - **Parallelism**: can work split into independent streams? - **Complexity -> team size**: simple (2 agents), medium (3-4), complex cross-cutting (5-6, max 8) ## Step 2: Ask Team Questions (AskUserQuestion Tool) Ask 3-5 questions based on Step 1 findings. Not all apply every time -- pick what matters. 1. **Team Composition** -- "For this [work type] on [stack], I'm thinking [N] agents: [role list]. What would you change?" Options: Perfect / Add role / Remove role / Different approach 2. **Coordination** -- "How should agents work together?" Options: Independent (no messaging) / Team (peer messaging) / Hub-spoke (lead coordinates) 3. **Dependencies** -- "Work order