Agent skill

Vibe Parallel Task Decomposition

by ash1794 in ash1794/vibe-engineering

Analyzes large tasks for independent subtasks that can be safely parallelized.

MITAuto-check passedAgent Workflows

Install Vibe Parallel Task Decomposition

skills CLI
$ npx skills add ash1794/vibe-engineering --skill vibe-parallel-task-decomposition -a claude-code

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

GitHub CLI
$ gh skill install ash1794/vibe-engineering vibe-parallel-task-decomposition --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/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-parallel-task-decomposition .claude/skills/vibe-parallel-task-decomposition && 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/

Facts

Skill name
vibe-parallel-task-decomposition
GitHub stars
163
Token cost
~717 tokens
SKILL.md length
328 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Analyzes large tasks for independent subtasks that can be safely parallelized.

  • Works in 6 steps: List all subtasks from the plan or… → Build dependency graph — For each pair… → Group into batches → …
  • A task has 5+ subtasks touching independent files
  • SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Steps and Output Format
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vibe Parallel Task Decomposition is an agent skill from ash1794/vibe-engineering. Analyzes large tasks for independent subtasks that can be safely parallelized. Produces a DAG-based dispatch plan with dependency ordering and maximum parallelism. Use when a task has 5+ subtasks touching independent files, or the user asks to speed up or parallelize the work.

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

It sits in Agent Workflows, covering Task breakdown. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.

When your agent uses it

  • A task has 5+ subtasks touching independent files
  • The user asks to speed up
  • Parallelize the work

Example prompts

  • “Use the vibe-parallel-task-decomposition skill to analyz large tasks for independent subtasks that can be safely parallelized”
  • “/vibe-parallel-task-decomposition”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. List all subtasks from the plan or requirements
  2. Build dependency graph — For each pair of tasks, ask
  3. Group into batches
  4. Set parallelism limit — Use the harness's native parallelism (subagents, background tasks, workflows, or cloud tasks) and respect its…
  5. Isolate — Give each parallel stream its own worktree or branch if the harness supports isolation, so streams can't overwrite each other's…
  6. Create dispatch plan

What it can do on your machine

Read from SKILL.md and the folder at commit 8f1d71b. 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.

    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

Vibe Parallel Task Decomposition loads about 717 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 328 words of instructions outside code blocks.

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

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 ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 328 words, ~717 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-parallel-task-decomposition/SKILL.md (or your agent's skills folder).
name
vibe-parallel-task-decomposition
description
Analyzes large tasks for independent subtasks that can be safely parallelized. Produces a DAG-based dispatch plan with dependency ordering and maximum parallelism. Use when a task has 5+ subtasks touching independent files, or the user asks to speed up or parallelize the work.
user-invocable
true

vibe-parallel-task-decomposition

Large tasks are often collections of independent subtasks hiding behind a sequential mental model. Find the parallelism.

When to Use This Skill

  • Facing a task with 5+ subtasks
  • Multiple files need changes that don't depend on each other
  • Implementation plan has steps that could run concurrently
  • User asks to "speed this up" or "parallelize"

When NOT to Use This Skill

  • Tasks with fewer than 3 subtasks
  • All subtasks depend on each other sequentially
  • Changes are all in the same file
  • The overhead of coordination exceeds the benefit
  • Long-running, multi-phase work with follow-ups (use vibe-workstream-orchestration)

Steps

  1. List all subtasks from the plan or requirements

  2. Build dependency graph — For each pair of tasks, ask:

    • Do they modify the same file? → dependent
    • Does task B need output from task A? → dependent
    • Do they share mutable state? → dependent
    • Otherwise → independent (can parallelize)
  3. Group into batches:

    • Batch 0: Tasks with no dependencies (run first, in parallel)
    • Batch 1: Tasks that depend only on Batch 0 (run after Batch 0, in parallel)
    • Batch N: Continue until all tasks assigned
  4. Set parallelism limit — Use the harness's native parallelism (subagents, background tasks, workflows, or cloud tasks) and respect its concurrency limits. Past a handful of concurrent streams, the integration and review cost usually outweighs the speedup, so 3–5 is a sensible default unless the tasks are trivially independent.

  5. Isolate — Give each parallel stream its own worktree or branch if the harness supports isolation, so streams can't overwrite each other's files. Integrate afterwards with vibe-cherry-pick-integration.

  6. Create dispatch plan:

Output Format

Parallel Task Decomposition

Total Tasks: X Batches: Y Max Parallelism: Z agents Estimated Speedup: ~Nx vs sequential

Dependency Graph
Task A ──→ Task D
Task B ──→ Task D
Task C (independent)
Task D ──→ Task F
Task E (independent)
Dispatch Plan
BatchTasksParallelismDependencies
0A, B, C, E4None
1D1A, B
2F1D
Per-Task Assignments
  • Task A: [files], [description], [acceptance test]
  • Task B: [files], [description], [acceptance test]
Integration Order

After all batches complete, integrate in order: [A, B, C, E] → D → F

© ash1794, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/vibe-engineering/skills/vibe-parallel-task-decomposition of ash1794/vibe-engineering.

Open the folder on GitHubat commit 8f1d71b

Compare with similar skills

Vibe Parallel Task Decomposition 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.

Vibe Parallel Task Decomposition compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Parallel Task Decomposition this skillash1794/vibe-engineering163—~717Automated safety check: PassMIT
MemPalace Task HandoffMemPalace/mempalace59k—~1.9kAutomated safety check: PassMIT
Planning And Task Breakdownabashev/vfs-s31068 repos~1.9kAutomated safety check: PassApache-2.0
Incremental Implementationaddyosmani/agent-skills103k1 repos~2.3kAutomated safety check: PassMIT
ULW Plan Workflowcode-yeongyu/oh-my-openagent70k—~3.9kAutomated safety check: PassCustom licence
Implementation Plan Creatortailcallhq/forgecode7.6k1 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • MemPalace Task Handoff

    MemPalace/mempalace

    Creates, hands off, claims, executes and closes agent tasks through the MemPalace logstream, with approval of the exact task before it is recorded.

    59k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Breaks work into ordered tasks. An agent skill from abashev/vfs-s3.

    106 GitHub starsUsed in 8 repos~1.9k tokens
    Agent WorkflowsAuto-check passed
  • Incremental Implementation

    addyosmani/agent-skills

    Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.

    103k GitHub starsUsed in 1 repo~2.3k tokens
    Agent WorkflowsAuto-check passed
  • ULW Plan Workflow

    code-yeongyu/oh-my-openagent

    Explore-first planning that turns a vague or large request into one decision-complete work plan, written only after your approval and executed by a separate worker.

    70k GitHub stars~3.9k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Implementation Plan Creator

    tailcallhq/forgecode

    Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.

    7.6k GitHub starsUsed in 1 repo~1.1k tokens
    Agent WorkflowsAuto-check passed
  • Runs a whole project unattended on an agtx kanban board, decomposing the goal, starting tasks, unblocking workers and merging each result.

    1.7k GitHub stars~3.8k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed

More from ash1794/vibe-engineering

All 33 skills in this repo
  • Vibe Concurrent Test Safety

    ash1794/vibe-engineering

    Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.

    163 GitHub stars~665 tokensUpdated today
    Auto-check passed
  • Vibe Fuzz Parser Inputs

    ash1794/vibe-engineering

    Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).

    163 GitHub stars~722 tokensUpdated today
    Auto-check passed
  • Vibe Golden File Testing

    ash1794/vibe-engineering

    Implements snapshot/golden file tests with temporal normalization so tests don't break daily.

    163 GitHub stars~669 tokensUpdated today
    Auto-check passed
  • Vibe Slop Filter

    ash1794/vibe-engineering

    Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).

    163 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Vibe Spec Sync

    ash1794/vibe-engineering

    Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.

    163 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Vibe Adversarial Test Generation

    ash1794/vibe-engineering

    Generates edge case, failure mode, and spec-driven test cases.

    163 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Vibe Parallel Task Decomposition

What does Vibe Parallel Task Decomposition do?

Analyzes large tasks for independent subtasks that can be safely parallelized. Vibe Parallel Task Decomposition is an agent skill from ash1794/vibe-engineering. Analyzes large tasks for independent subtasks that can be safely parallelized.

When should I use Vibe Parallel Task Decomposition?

Vibe Parallel Task Decomposition fits situations like: A task has 5+ subtasks touching independent files; the user asks to speed up; parallelize the work.

How do I install Vibe Parallel Task Decomposition in Claude Code?

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

How do I install Vibe Parallel Task Decomposition in Codex?

Run `npx skills add ash1794/vibe-engineering --skill vibe-parallel-task-decomposition -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-parallel-task-decomposition in ash1794/vibe-engineering) into .agents/skills/vibe-parallel-task-decomposition in your project. Codex loads it when a task matches its description.

Can I use Vibe Parallel Task Decomposition 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 ash1794/vibe-engineering --skill vibe-parallel-task-decomposition -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-parallel-task-decomposition, .gemini/skills/vibe-parallel-task-decomposition, .github/skills/vibe-parallel-task-decomposition and .opencode/skills/vibe-parallel-task-decomposition in your project.

What does Vibe Parallel Task Decomposition need to run?

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

Does Vibe Parallel Task Decomposition 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 Vibe Parallel Task Decomposition 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 Vibe Parallel Task Decomposition use?

Vibe Parallel Task Decomposition 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 Vibe Parallel Task Decomposition use?

About 717 tokens (SKILL.md is roughly 2.9k 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 Vibe Parallel Task Decomposition?

Skills that share tags, products or a category with Vibe Parallel Task Decomposition: MemPalace Task Handoff (MemPalace/mempalace, 59k stars), Planning And Task Breakdown (abashev/vfs-s3, 106 stars), Incremental Implementation (addyosmani/agent-skills, 103k stars) and ULW Plan Workflow (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Parallel Task Decomposition?

ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.

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