parallel-agent-dispatch
Use when facing 2+ independent tasks that can be worked on without shared state. Dispatch one agent per problem domain for concurrent investigation.
What this skill does
# Parallel Agent Dispatch
When you have multiple unrelated problems, investigating sequentially wastes time. Dispatch one agent per independent problem domain.
## When to Use
- MUST: When 3+ independent failures exist
- MUST: When problems have no shared state
- SHOULD: When each problem can be understood in isolation
- NEVER: When failures might be related (fix one might fix others)
- NEVER: When agents would edit same files
## Decision Flow
```
Multiple failures?
↓ yes
Are they independent?
↓ yes → no: Single agent investigates all
Can they work in parallel?
↓ yes → no: Sequential agents
Parallel dispatch
```
## The Pattern
### 1. Identify Independent Domains
Group failures by what's broken:
- File A tests: User authentication
- File B tests: Order processing
- File C tests: Email notifications
Each domain is independent - fixing auth doesn't affect email.
### 2. Create Focused Agent Tasks
Each agent gets:
- **Specific scope:** One test file or subsystem
- **Clear goal:** Make these tests pass
- **Constraints:** Don't change other code
- **Expected output:** Summary of findings and fixes
### 3. Dispatch in Parallel
```typescript
// Dispatch all three concurrently
Task("Fix user-auth.test.ts failures")
Task("Fix order-processing.test.ts failures")
Task("Fix email-notifications.test.ts failures")
```
### 4. Review and Integrate
When agents return:
1. Read each summary
2. Verify fixes don't conflict
3. Run full test suite
4. Integrate all changes
## Agent Prompt Structure
```markdown
Fix the 3 failing tests in src/auth/user-auth.test.ts:
1. "should validate JWT token" - expects valid token, gets null
2. "should reject expired token" - not rejecting expired
3. "should refresh token" - refresh returns old token
Your task:
1. Read the test file, understand what each test verifies
2. Identify root cause - timing, logic, or configuration?
3. Fix by addressing actual issue (not just making tests pass)
Do NOT increase timeouts - find the real issue.
Return: Summary of root cause and what you fixed.
```
## MUST/SHOULD/NEVER Rules
### MUST
- MUST: Verify problems are independent before dispatching
- MUST: Give each agent specific, focused scope
- MUST: Include expected output format in prompt
- MUST: Verify fixes don't conflict after agents return
- MUST: Run full test suite after integration
### SHOULD
- SHOULD: Include error messages in agent prompts
- SHOULD: Specify constraints (what NOT to change)
- SHOULD: Request summary of root cause, not just "fixed"
### NEVER
- NEVER: Dispatch for related failures
- NEVER: Let agents edit same files
- NEVER: Skip post-integration verification
- NEVER: Use vague prompts ("fix the tests")
## Common Mistakes
| Mistake | Fix |
|---------|-----|
| Too broad scope | "Fix auth tests" not "fix all tests" |
| No context | Include error messages in prompt |
| No constraints | Specify what NOT to change |
| Vague output | Request specific summary format |
## When NOT to Use
- **Related failures:** Fix one might fix others
- **Need full context:** Understanding requires system-wide view
- **Exploratory debugging:** Don't know what's broken yet
- **Shared state:** Agents would interfere
## Integration
| Skill | Relationship |
|-------|--------------|
| `debugging-methodology` | Each agent follows debugging process |
| `verification-before-completion` | Verify after integration |
| `tdd-workflow` | Agents follow TDD when fixing |
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.