parallel-launch
Decompose a task into independent concerns and execute them through aggressively 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.
Installation
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Voir la source ↗GuidesInstructions
Parallel Launch
Decompose the given task into independent agent groups and execute them in maximum parallel.
Process
-
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.
-
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.
-
Launch all independent agents in a single tool call — never sequentially when parallel is possible.
-
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.
Constraints
- Maximum 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.
Exemples
Consultez les exemples du dépôt source.
Voir la source ↗Historique source
- Date d’indexation
- 2026-03-11
- Mise à jour de l’index
- 2026-03-11
- Branch
- main
Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!