parallel-launch
Decompose a task into independent concerns and execute them through broadly parallel, specialized agent groups. Use when a request involves multiple independent sub-tasks, research across separate domains, or work that can be parallelized across files or modules.
What this skill does
# Parallel Launch Decompose the given task into independent agent groups and execute them in broad parallel. ## Process 1. **Analyze the task** and identify independent concerns that can run concurrently. - Each concern must be self-contained: no shared mutable state, no ordering dependency. - If concerns have dependencies, sequence the dependent batch after the independent batch completes. - Consult [delegation scenarios](./references/delegation-scenarios.md) for parallelism decisions. 2. **Design agent groups** — for each independent concern: - Assign a clear, scoped objective (one concern per agent). - Select the appropriate agent type (Explore, Plan, general-purpose, or domain specialist). - Define expected output format so results can be composed. 3. **Launch all independent agents in a single tool call** — never sequentially when parallel is possible. 4. **Compose results** once all agents complete: - Merge non-conflicting outputs directly. - For conflicting or overlapping results, reconcile and present trade-offs to the user. - If any agent failed or returned incomplete results, report the gap and propose a targeted follow-up. 5. **Review composed output** — dispatch a review agent to verify: - **Completeness:** All original concerns addressed, no gaps. - **Consistency:** No contradictions between agent outputs. - **Accuracy:** Claims are substantiated, sources checked, no hallucinated findings. - **Scope:** Nothing extra built beyond what was asked. - For implementation work, additionally verify spec compliance and code quality. 6. **Report to user** only after review passes. ## Constraints - Agents per batch: match the number of truly independent concerns (avoid artificial splitting). - Each agent prompt must include full context — agents do not share memory. - Do not launch agents for trivially sequential work (single file, single concern). - If the task has fewer than 2 independent concerns, execute directly instead of launching agents. ## Red Flags - **Never skip review.** Composed output must always pass through a review agent before reporting. - **Never accept unverified composed output.** If agents return conflicting results, the review agent must flag them — not silently pick one. - **Never report to user before review passes.** The review step is mandatory, not advisory.
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.