⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v0.43.0

dispatching-parallel-agents

xintaofei@xintaofei⭐ 4.4k stars· last commit 3d ago· 202 open issues

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 4.4k on GitHubGitHub ↗

Very popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

✨ Features

One Interface for Every Agent

Twenty agents, plus any ACP agent, in one rich chat with tool cards, live diffs, and interactive replies.

Docs → · Custom agents → · UI Render →

Every Session, Searchable

Import, search, and resume any agent's history. Share sessions with @ mentions and organize them with tags.

Docs → · Tags →

Multi-Agent Collaboration

@ an agent to delegate. Run agents side by side and watch their progress stream into your conversation.

Docs →

To-dos That Run Unattended

Schedule tasks in isolated worktrees. Agents handle the work; you review and approve the changes.

Docs → · Auto-processing →

Infinite Canvas

Arrange chats, files, terminals, and notes on an infinite board. Keep every agent's work in view.

Docs →

Desktop, Server, Mobile & Chat

Work on desktop, server, Docker, or mobile. Reach your agents through Telegram, Lark, and WeChat.

Docs → · Remote workspaces → · Mobile apps → · Chat channels →

Office Documents & Research

Create Office files with live previews and view PDFs beside chat. Research skills work with any agent.

Docs → · Research →

Browser & Computer Use

Share pages and errors from the desktop browser. Let agents operate shared windows with Computer Use (preview).

Docs → · Computer Use →

Command Line & CI

Run prompts from scripts or CI with codeg-cli. Connect to a running Codeg for replies or JSON events.

[Docs →](https://docs.codeg.app/gu

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • src-tauri/experts/skills/dispatching-parallel-agents/SKILL.md5.9 KB3fa091b348bbupstream ↗
    ---
    name: dispatching-parallel-agents
    description: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
    ---
    
    # Dispatching Parallel Agents
    
    ## Overview
    
    You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
    
    When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.
    
    **Core principle:** Dispatch one agent per independent problem domain. Let them work concurrently.
    
    ## When to Use
    
    ```dot
    digraph when_to_use {
        "Multiple failures?" [shape=diamond];
        "Are they independent?" [shape=diamond];
        "Single agent investigates all" [shape=box];
        "One agent per problem domain" [shape=box];
        "Can they work in parallel?" [shape=diamond];
        "Sequential agents" [shape=box];
        "Parallel dispatch" [shape=box];
    
        "Multiple failures?" -> "Are they independent?" [label="yes"];
        "Are they independent?" -> "Single agent investigates all" [label="no - related"];
        "Are they independent?" -> "Can they work in parallel?" [label="yes"];
        "Can they work in parallel?" -> "Parallel dispatch" [label="yes"];
        "Can they work in parallel?" -> "Sequential agents" [label="no - shared state"];
    }
    ```
    
    **Use when:**
    - 3+ test files failing with different root causes
    - Multiple subsystems broken independently
    - Each problem can be understood without context from others
    - No shared state between investigations
    
    **Don't use when:**
    - Failures are related (fix one might fix others)
    - Need to understand full system state
    - Agents would interfere with each other
    
    ## The Pattern
    
    ### 1. Identify Independent Domains
    
    Group failures by what's broken:
    - File A tests: Tool approval flow
    - File B tests: Batch completion behavior
    - File C tests: Abort functionality
    
    Each domain is independent - fixing tool approval doesn't affect abort tests.
    
    ### 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 what you found and fixed
    
    ### 3. Dispatch in Parallel
    
    Issue all three subagent dispatches in the same response — they run in parallel:
    
    ```text
    Subagent (general-purpose): "Fix agent-tool-abort.test.ts failures"
    Subagent (general-purpose): "Fix batch-completion-behavior.test.ts failures"
    Subagent (general-purpose): "Fix tool-approval-race-conditions.test.ts failures"
    # All three run concurrently.
    ```
    
    Multiple dispatch calls in one response = parallel execution. One per response = sequential.
    
    ### 4. Review and Integrate
    
    When agents return:
    - Read each summary
    - Verify fixes don't conflict
    - Run full test suite
    - Integrate all changes
    
    ## Agent Prompt Structure
    
    Good agent prompts are:
    1. **Focused** - One clear problem domain
    2. **Self-contained** - All context needed to understand the problem
    3. **Specific about output** - What should the agent return?
    
    ```markdown
    Fix the 3 failing tests in src/agents/agent-tool-abort.test.ts:
    
    1. "should abort tool with partial output capture" - expects 'interrupted at' in message
    2. "should handle mixed completed and aborted tools" - fast tool aborted instead of completed
    3. "should properly track pendingToolCount" - expects 3 results but gets 0
    
    These are timing/race condition issues. Your task:
    
    1. Read the test file and understand what each test verifies
    2. Identify root cause - timing issues or actual bugs?
    3. Fix by:
       - Replacing arbitrary timeouts with event-based waiting
       - Fixing bugs in abort implementation if found
       - Adjusting test expectations if testing changed behavior
    
    Do NOT just increase timeouts - find the real issue.
    
    Return: Summary of what you found and what you fixed.
    ```
    
    ## Common Mistakes
    
    **❌ Too broad:** "Fix all the tests" - agent gets lost
    **✅ Specific:** "Fix agent-tool-abort.test.ts" - focused scope
    
    **❌ No context:** "Fix the race condition" - agent doesn't know where
    **✅ Context:** Paste the error messages and test names
    
    **❌ No constraints:** Agent might refactor everything
    **✅ Constraints:** "Do NOT change production code" or "Fix tests only"
    
    **❌ Vague output:** "Fix it" - you don't know what changed
    **✅ Specific:** "Return summary of root cause and changes"
    
    ## When NOT to Use
    
    **Related failures:** Fixing one might fix others - investigate together first
    **Need full context:** Understanding requires seeing entire system
    **Exploratory debugging:** You don't know what's broken yet
    **Shared state:** Agents would interfere (editing same files, using same resources)
    
    ## Real Example from Session
    
    **Scenario:** 6 test failures across 3 files after major refactoring
    
    **Failures:**
    - agent-tool-abort.test.ts: 3 failures (timing issues)
    - batch-completion-behavior.test.ts: 2 failures (tools not executing)
    - tool-approval-race-conditions.test.ts: 1 failure (execution count = 0)
    
    **Decision:** Independent domains - abort logic separate from batch completion separate from race conditions
    
    **Dispatch:**
    ```
    Agent 1 → Fix agent-tool-abort.test.ts
    Agent 2 → Fix batch-completion-behavior.test.ts
    Agent 3 → Fix tool-approval-race-conditions.test.ts
    ```
    
    **Results:**
    - Agent 1: Replaced timeouts with event-based waiting
    - Agent 2: Fixed event structure bug (threadId in wrong place)
    - Agent 3: Added wait for async tool execution to complete
    
    **Integration:** All fixes independent, no conflicts, full suite green
    
    ## Verification
    
    After agents return:
    1. **Review each summary** - Understand what changed
    2. **Check for conflicts** - Did agents edit same code?
    3. **Run full suite** - Verify all fixes work together
    4. **Spot check** - Agents can make systematic errors
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/xintaofei-codeg-src-tauri-experts-skills-dispatching-parallel-agents.md

// REPO STATS

4.4k stars
202 open issues
Last commit: 3d ago