---
name: agent-coordination
description: > Spawn and coordinate agents for complex multi-agent tasks. npx claude-flow agent spawn --type…
category: ai
runtime: no special runtime
---

# agent-coordination output preview

## PART A: Task fit
- Use case: > Spawn and coordinate agents for complex multi-agent tasks. npx claude-flow agent spawn --type coder --name my-coder npx claude-flow agent list --filter active npx claude-flow agent status --id agent-123 npx claude-flow agent metrics --id agent-123 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Purpose / Agent Types / Core Development” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “> Spawn and coordinate agents for complex multi-agent tasks. npx claude-flow agent spawn --type coder --name my-coder npx claude-flow agent list --filter active npx claude-flow agent status --id agent-123 npx claude-flow agent metrics --id agent-123 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Purpose / Agent Types / Core Development” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.