vibe-parallel
Skill7 starsChanged 13 days agoNo licenceView on GitHub
Parallel task execution using Claude Code subagents. Reads task files, builds dependency waves, detects file conflicts AND read-write conflicts, and spawns tasks as parallel subagents. Size-aware wave splitting unlocks downstream tasks early when large tasks are in the same wave as small ones. If vibe-graph is installed, each subagent gets a graph-derived focus block (blast-radius files + rationale) on top of a shared cached baseline — precise scoping without blind spots, cheap via prompt caching. Structured subagent reporting with [x]/[~]/[!] states. Diagnostic retry on failure. Live wave progress log at vibe/parallel/. Post-wave graph update. Wave cost annotation for vibe-cost. Triggers on "parallel:" prefix, "run tasks in parallel", "spawn subagents", "parallelise the build", "which tasks can run in parallel", "run independent tasks simultaneously". Invoked by vibe-mode's autonomous-execution block (which vibe-new-app, vibe-add-feature, and vibe-fix-bug hand off to when VIBE_MODE=autonomous), or directly when the user runs `parallel:`. In manual mode the build skills do not call it automatically — the user opts in.
In this repository26 other files it gives its agents.
- vibe-add-featureSkill
- vibe-agentSkill
- vibe-architectSkill
- vibe-brainstormSkill
- vibe-changelogSkill
- vibe-change-specSkill
- vibe-costSkill
- vibe-deploySkill
- vibe-design-mdSkill
- vibe-designSkill
- vibe-doctorSkill
- vibe-documentSkill
- vibe-e2eSkill
- vibe-fix-bugSkill
- vibe-goldfishSkill
- vibe-graphSkill
- vibe-handoffSkill
- vibe-initSkill
- vibe-ledgerSkill
- vibe-modeSkill
- vibe-new-appSkill
- vibe-perfSkill
- vibe-progressSkill
- vibe-reviewSkill
- vibe-spec-reviewSkill
- vibe-testSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
42 rules. About 0 are common, 17 are distinctive, and 25 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
25
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.