grove-multi-agent

name	grove-multi-agent
description	Use when multiple independent tasks need to be executed in parallel, each in an isolated workspace with warm build state

I'm using the grove-multi-agent skill to orchestrate parallel agents across isolated Grove workspaces.

When to Use This Skill

digraph {
    "Multiple tasks?" [shape=diamond];
    "Independent?" [shape=diamond];
    "grove-multi-agent" [shape=box];
    "Sequential execution" [shape=box];
    "Single grove:using-grove" [shape=box];

    "Multiple tasks?" -> "Single grove:using-grove" [label="1 task"];
    "Multiple tasks?" -> "Independent?" [label="2+ tasks"];
    "Independent?" -> "grove-multi-agent" [label="yes"];
    "Independent?" -> "Sequential execution" [label="no - shared state"];
}

Use grove-multi-agent only when tasks are truly independent: no shared file modifications, no ordering dependencies between them.

Workflow

Step 1: Receive tasks

Accept a list of independent tasks. Tasks may come from a decomposed plan, directly from the user, or from a dispatching agent (e.g., superpowers:dispatching-parallel-agents). Each task must be a self-contained unit of work.

Step 2: Validate independence

Before creating any workspaces, review the task list for overlapping file scope. If two tasks would modify the same file or directory, they are not truly independent.

• If overlap is detected: warn the user, identify the conflicting tasks, and ask whether to proceed (by serializing those tasks) or restructure the plan.
• If no overlap: continue.

Step 3: Determine branch prefix

Use the current branch name as the prefix, or ask the user for one. Workspace branches will follow the pattern:

agent/<prefix>/<task-slug>

Example: if the prefix is feature/auth-overhaul and the task is "Add OAuth login", the branch becomes agent/feature-auth-overhaul/add-oauth-login.