Agent skill

Parallel Execution

A skill your agent uses when facing 2+ tasks that share no state and have no sequential dependencies - enables concurrent investigation or implementation by dispatching one agent per isolated…

MITAuto-check passed

Install Parallel Execution

skills CLI

$ npx skills add NoobyGains/godmode --skill parallel-execution -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode parallel-execution --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/parallel-execution .claude/skills/parallel-execution && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "parallel-execution" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/parallel-execution into .claude/skills/parallel-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-execution", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/NoobyGains/godmode/tree/master/skills/parallel-execution

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add NoobyGains/godmode --skill parallel-execution -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode parallel-execution --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/parallel-execution .agents/skills/parallel-execution && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "parallel-execution" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/parallel-execution into .agents/skills/parallel-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-execution", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NoobyGains/godmode --skill parallel-execution -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode parallel-execution --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/parallel-execution .cursor/skills/parallel-execution && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "parallel-execution" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/parallel-execution into .cursor/skills/parallel-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-execution", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/NoobyGains/godmode.git --path skills/parallel-execution

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NoobyGains/godmode --skill parallel-execution -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode parallel-execution --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/parallel-execution .gemini/skills/parallel-execution && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "parallel-execution" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/parallel-execution into .gemini/skills/parallel-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-execution", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install NoobyGains/godmode parallel-execution

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add NoobyGains/godmode --skill parallel-execution -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/parallel-execution .github/skills/parallel-execution && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "parallel-execution" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/parallel-execution into .github/skills/parallel-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-execution", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NoobyGains/godmode --skill parallel-execution -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NoobyGains/godmode parallel-execution --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NoobyGains/godmode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/parallel-execution .opencode/skills/parallel-execution && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "parallel-execution" agent skill from https://github.com/NoobyGains/godmode/tree/master/skills/parallel-execution into .opencode/skills/parallel-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "parallel-execution", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: parallel-execution
GitHub stars: 107
Token cost: ~2k tokens
SKILL.md length: 752 words
Files: 1
Skills in repo: 34
Repo updated: Mar 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when facing 2+ tasks that share no state and have no sequential dependencies - enables concurrent investigation or implementation by dispatching one agent per isolated…

Works in 4 steps: Map Independent Domains → Craft Focused Agent Briefs → Launch Concurrently → …
Facing 2+ tasks that share no state and have no sequential dependencies - enables concurrent investigation
SKILL.md covers Overview, Prime Directive, When to Use and The Approach, plus 9 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Parallel Execution is an agent skill from NoobyGains/godmode. Use when facing 2+ tasks that share no state and have no sequential dependencies - enables concurrent investigation or implementation by dispatching one agent per isolated problem domain

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The AI development framework that thinks before it builds. 36 composable skills for Claude Code, Cursor, Codex, and OpenCode. The licence is MIT.

When your agent uses it

Facing 2+ tasks that share no state and have no sequential dependencies - enables concurrent investigation
Implementation by dispatching one agent per isolated problem domain

Example prompts

“/parallel-execution”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Map Independent Domains
Craft Focused Agent Briefs
Launch Concurrently
Reconcile and Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 441103a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are dot and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Parallel Execution loads about 2k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 752 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~51
When it runs · the whole SKILL.md, loaded when a task matches: ~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NoobyGains/godmode at commit 441103a, republished under its MIT licence (© NoobyGains). 752 words, ~2,008 tokens.

Download SKILL.mdSave it as .claude/skills/parallel-execution/SKILL.md (or your agent's skills folder).

name: parallel-execution
description: Use when facing 2+ tasks that share no state and have no sequential dependencies - enables concurrent investigation or implementation by dispatching one agent per isolated problem domain

Parallel Execution

Overview

When multiple distinct failures appear across separate subsystems, tackling them one after another wastes time. Each investigation is self-contained and can run simultaneously.

Core principle: Assign one agent per isolated problem domain. Let them operate concurrently.

Prime Directive

NO CONCURRENT DISPATCH WITHOUT CONFIRMING ISOLATION

No exceptions. No workarounds. No shortcuts.

When to Use

dot

digraph dispatch_decision {
    "Multiple problems?" [shape=diamond];
    "Are they isolated?" [shape=diamond];
    "Single agent handles all" [shape=box];
    "One agent per domain" [shape=box];
    "Can they run concurrently?" [shape=diamond];
    "Sequential agents" [shape=box];
    "Parallel dispatch" [shape=box];

    "Multiple problems?" -> "Are they isolated?" [label="yes"];
    "Are they isolated?" -> "Single agent handles all" [label="no - coupled"];
    "Are they isolated?" -> "Can they run concurrently?" [label="yes"];
    "Can they run concurrently?" -> "Parallel dispatch" [label="yes"];
    "Can they run concurrently?" -> "Sequential agents" [label="no - shared state"];
}

Appropriate when:

Three or more test files failing for distinct reasons
Multiple subsystems broken independently
Each issue can be understood without knowledge of the others
No shared mutable state between the work items

Not appropriate when:

Failures are connected (resolving one may resolve others)
Understanding requires a holistic system view
Agents would interfere with each other's work

The Approach

1. Map Independent Domains

Classify failures by root cause area:

Module X tests: Permission validation flow
Module Y tests: Queue drain behavior
Module Z tests: Cancellation handling

Each domain is self-contained — fixing permissions has no bearing on cancellation tests.

2. Craft Focused Agent Briefs

Each agent receives:

Defined scope: One test file or subsystem
Concrete objective: Get these tests green
Boundaries: Do not modify code outside your scope
Deliverable: Summary of root cause and changes made

3. Launch Concurrently

// Dispatch parallel agents using the Agent tool in Claude Code
Agent("Fix permission-validation.test.ts failures")
Agent("Fix queue-drain-behavior.test.ts failures")
Agent("Fix cancellation-handling.test.ts failures")
// All three execute at the same time

4. Reconcile and Verify

When agents complete:

Study each summary
Confirm changes do not overlap
Execute the full test suite
Integrate all results

Agent Brief Structure

Effective agent briefs share these qualities:

Narrow — One clear problem area
Self-sufficient — Everything needed to understand the issue is included
Output-specified — The agent knows exactly what to report

markdown

Resolve the 3 failing tests in src/workers/queue-drain.test.ts:

1. "should drain remaining items on shutdown" - expects empty queue, finds 2 items
2. "should handle mixed priorities during drain" - high-priority item processed last
3. "should report drain metrics accurately" - expects 3 metrics but receives 0

These stem from async drain ordering. Your assignment:

1. Read the test file and understand the intended behavior
2. Determine root cause - ordering bug or stale test assumptions?
3. Fix by:
   - Implementing deterministic drain ordering
   - Correcting production bugs if found
   - Updating test expectations if behavior legitimately changed

Do NOT just add delays or increase timeouts - identify the underlying issue.

Return: Root cause analysis and description of changes made.

Pitfalls

Too broad: "Fix all the tests" — the agent loses focus Focused: "Fix queue-drain.test.ts" — narrow scope

No context: "Fix the ordering bug" — the agent has no starting point Contextual: Paste error messages and failing test names

No boundaries: Agent may restructure unrelated code Bounded: "Do NOT modify production code outside src/workers/"

Vague output request: "Fix it" — you have no idea what changed Specific output request: "Return root cause summary and list of modified files"

Cognitive Traps

Rationalization	Truth
"They're probably isolated enough"	Confirm isolation explicitly or agents will collide.
"We'll reconcile conflicts later"	Merge conflicts from concurrent agents are harder than sequential work.
"More agents = faster delivery"	Agents editing shared files = wasted effort and broken merges.
"The scope is self-evident"	Vague briefs yield vague outcomes. Specify scope, boundaries, and output.
"One agent can handle everything"	An agent with too wide a scope gets lost. Divide by domain.

When NOT to Use

Coupled failures: Resolving one may cascade fixes to others — investigate holistically first Holistic understanding required: Comprehension demands seeing the full system Exploratory debugging: The problem space is unknown Shared resources: Agents would conflict (same files, same databases, same services)

Show full SKILL.md (311 more words)Show less

Worked Example

Situation: 8 test failures across 3 files after a major refactor

Failures:

permission-validation.test.ts: 3 failures (auth token issues)
queue-drain-behavior.test.ts: 3 failures (ordering bugs)
cancellation-handling.test.ts: 2 failures (incomplete cleanup)

Judgment: Isolated domains — auth validation, queue drain, and cancellation logic are unrelated

Dispatch:

Agent 1 -> Fix permission-validation.test.ts
Agent 2 -> Fix queue-drain-behavior.test.ts
Agent 3 -> Fix cancellation-handling.test.ts

Outcomes:

Agent 1: Replaced hardcoded tokens with dynamic fixtures
Agent 2: Fixed drain ordering to respect priority field
Agent 3: Added cleanup hooks for partial cancellation state

Reconciliation: All fixes touched separate files, zero conflicts, full suite green

Value: Three problems solved concurrently instead of sequentially

Advantages

Concurrency — Multiple investigations proceed at once
Concentration — Each agent manages a small context
Non-interference — Agents stay out of each other's way
Throughput — N problems solved in the time of one

Post-Dispatch Checks

After agents return:

Study each summary — Understand what changed and why
Detect overlaps — Did any agents touch the same code?
Run the full suite — Confirm all fixes coexist
Spot-check — Agents can introduce systematic errors
Finalize — REQUIRED SUB-SKILL: Use godmode:merge-protocol to land the work

Guardrails

Prohibited:

Dispatching concurrent agents without verifying task isolation
Allowing agents to modify the same files simultaneously
Integrating without reviewing agent summaries
Using parallel dispatch for exploratory diagnosis
Dispatching without defined scope, boundaries, and deliverables

Mandatory:

Confirm isolation before dispatching
Give each agent a narrow, explicit scope
Include error messages and test names in agent briefs
Review all agent summaries before integration
Execute full test suite after integrating all changes
Check for conflicts between agent outputs

Integration

godmode:team-orchestration:

Parallel execution is a foundational pattern for team-based work
Use team orchestration when agents have partial dependencies

godmode:delegated-execution:

Launch parallel agents for independent tasks within a development plan
Each agent owns one task from the plan

godmode:agent-messaging:

Agents dispatched in parallel should not need inter-agent communication
If they need to communicate, they are not isolated enough for parallel dispatch

Files

Just SKILL.md in skills/parallel-execution of NoobyGains/godmode.

Open the folder on GitHubat commit 441103a

Compare with similar skills

Parallel Execution next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Parallel Execution compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Parallel Execution this skillNoobyGains/godmode	107	—	~2k	Automated safety check: Pass	MIT	7 mo ago
ShareClickHouse/ClickHouse	50k	—	~558	Automated safety check: Notes	Apache-2.0	today
Parallels Discord Roundtripopenclaw/openclaw	392k	—	~788	Automated safety check: Pass	MIT	today
Openclaw Parallels Smokeopenclaw/openclaw	392k	—	~8.4k	Automated safety check: Notes	MIT	today
SharingBuilderIO/agent-native	7.1k	—	~3.4k	Automated safety check: Pass	None	today
Parallel Execution Optimizeraffaan-m/ECC	275k	1 repos	~712	Automated safety check: Pass	MIT	3 days ago

Similar skills

Share
ClickHouse/ClickHouse
Share a Claude Code session to pastila.nl and return a viewer link.
50k GitHub stars~558 tokensUpdated today
DatabasesAuto-check: notes
Parallels Discord Roundtrip
openclaw/openclaw
Run macOS Parallels smoke with Discord send, host verification, host reply, and guest readback proof.
392k GitHub stars~788 tokensUpdated today
Auto-check passed
Openclaw Parallels Smoke
openclaw/openclaw
Prepare, snapshot, run, rerun, debug, or interpret OpenClaw Parallels guest install, onboarding, gateway smoke, and upgrade checks across macOS, Windows, and Linux.
392k GitHub stars~8.4k tokensUpdated today
Auto-check: notes
Sharing
BuilderIO/agent-native
Framework-level sharing and privacy for user-authored resources (dashboards, documents, forms, decks, etc.).
7.1k GitHub stars~3.4k tokensUpdated today
Auto-check passed
Parallel Execution Optimizer
affaan-m/ECC
Speed up a task by turning it into a dependency graph of parallel lanes with a lane matrix, batched reads and checks, write surfaces isolated by file, worktree, branch, or service, and a final…
275k GitHub starsUsed in 1 repo~712 tokens
DevelopmentAuto-check passed
Parallel Automation
ComposioHQ/awesome-claude-skills
Automate Parallel tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
77k GitHub starsUsed in 3 repos~734 tokens
Productivity & AutomationAuto-check passed

Questions about Parallel Execution

What does Parallel Execution do?

A skill your agent uses when facing 2+ tasks that share no state and have no sequential dependencies - enables concurrent investigation or implementation by dispatching one agent per isolated…. Parallel Execution is an agent skill from NoobyGains/godmode.

When should I use Parallel Execution?

Parallel Execution fits situations like: facing 2+ tasks that share no state and have no sequential dependencies - enables concurrent investigation; implementation by dispatching one agent per isolated problem domain.

How do I install Parallel Execution in Claude Code?

Run `npx skills add NoobyGains/godmode --skill parallel-execution -a claude-code`. Or copy the skill folder (skills/parallel-execution in NoobyGains/godmode) into .claude/skills/parallel-execution in your project. Claude Code loads it when a task matches its description.

How do I install Parallel Execution in Codex?

Run `npx skills add NoobyGains/godmode --skill parallel-execution -a codex`. Or copy the skill folder (skills/parallel-execution in NoobyGains/godmode) into .agents/skills/parallel-execution in your project. Codex loads it when a task matches its description.

Can I use Parallel Execution in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NoobyGains/godmode --skill parallel-execution -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/parallel-execution, .gemini/skills/parallel-execution, .github/skills/parallel-execution and .opencode/skills/parallel-execution in your project.

What does Parallel Execution need to run?

SKILL.md names no scripts, command-line tools or credentials: Parallel Execution is instructions for the agent only.

Does Parallel Execution access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Parallel Execution safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Parallel Execution use?

Parallel Execution is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Parallel Execution use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Parallel Execution?

Skills that share tags, products or a category with Parallel Execution: Share (ClickHouse/ClickHouse, 50k stars), Parallels Discord Roundtrip (openclaw/openclaw, 392k stars), Openclaw Parallels Smoke (openclaw/openclaw, 392k stars) and Sharing (BuilderIO/agent-native, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Parallel Execution?

NoobyGains (a GitHub user) maintains it in NoobyGains/godmode, which has 107 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on March 9, 2026.

Source: NoobyGains/godmode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Parallel Execution

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Parallel Execution

Overview

Prime Directive

When to Use

The Approach

1. Map Independent Domains

2. Craft Focused Agent Briefs

3. Launch Concurrently

4. Reconcile and Verify

Agent Brief Structure

Pitfalls

Cognitive Traps

When NOT to Use

Worked Example

Advantages

Post-Dispatch Checks

Guardrails

Integration

Files

Compare with similar skills

Similar skills

More from NoobyGains/godmode

Questions about Parallel Execution