Parallel Orchestrate
ReviewAudited by ClawScan on May 13, 2026.
Overview
This is a clearly disclosed code-orchestration skill, but it can modify your git repository through parallel subagents and stores local run state and telemetry.
Install only if you want an agent to coordinate substantial git changes for you. Run it on a clean branch, approve the task plan carefully, verify the local gstack dependencies, and remember that orchestration state and analytics are written under ~/.gstack.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The skill may create commits, cherry-pick changes, run tests, and move work toward shipping without the user manually performing each step.
The skill can invoke subagents and git operations that modify the user's repository. This is expected for its stated purpose and includes approval and verification steps, but it is still high-impact repo mutation.
Dispatches each task as an `Agent` subagent with `isolation: "worktree"` ... Cherry-picks each successful task's commit onto your working branch ... Runs the full test suite at every wave boundary
Use it from a clean branch, review the task decomposition before approving, and inspect the resulting commits before relying on the final ship handoff.
Behavior may depend on the installed versions and trustworthiness of the local gstack tools and sibling skills.
The skill relies on external local tools and other skills that are not included in this artifact set. This is disclosed and purpose-aligned, but those dependencies determine part of the actual runtime behavior.
"requires": { "tools": ["jq", "git"], "siblingSkills": ["gstack/review", "gstack/ship"], "subSkills": ["superpowers:using-git-worktrees", "superpowers:dispatching-parallel-agents"] }Verify that the referenced gstack and superpowers skills are installed from sources you trust and are compatible with this workflow.
Project plans, branch names, task results, and orchestration history may remain on disk after the run.
The skill intentionally persists task plans, run state, and subagent results for resume and reporting. This is disclosed, but the files may contain project-specific implementation details.
Shared state directory: `~/.gstack/projects/<slug>/orchestrate/<branch>/` holds `TASKS.md`, `env.sh`, `state.jsonl`, `results/<TASK_ID>.json`.
Review or clean the ~/.gstack project state if the plan or task outputs contain sensitive information.
A subagent's reported commit SHA and result file influence what the orchestrator integrates into the main branch.
The orchestrator and subagents communicate through commits and shared result JSON files. This is a normal part of the design and includes worktree isolation, but it is still an inter-agent data boundary users should understand.
Subagents (`Agent` tool): one per task, each in its own isolated git worktree. Reads CLAUDE.md, implements scope, commits, writes a result JSON to a shared dir.
Keep the shared orchestration directory local and trusted, and review failed or unexpected subagent results before continuing.