dispatching-parallel-agents
Use when 2 or more tasks are independent enough to investigate or implement in parallel
Skill by tenecsson
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/tenecsson-dispatching-parallel-agents
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/dispatching-parallel-agents
What's inside
- Skill name
dispatching-parallel-agents- Description
- Use when 2 or more tasks are independent enough to investigate or implement in parallel
- License
- MIT
- Instructions
- 26 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
Use one agent per independent problem domain. Keep related failures together. Use this when: - multiple failures have different root causes - tasks touch different files or subsystems - each task can be understood without the others Do not use this when: - failures may share a root cause - the work is still exploratory and not yet partitioned - agents would edit the same files or rely on shared state Workflow: 1. Group work by root cause, owned files, or subsystem. 2. Split only the work that is truly independent. 3. Give each agent a narrow, self-contained brief: exact scope, relevant errors or context, constraints, and expected report. 4. Run them in parallel. 5. Review every result, check for overlap or conflicts, then run the combined verification. Prompt rules: - Focus on one file, subsystem, or failure cluster. - Include the concrete symptoms and success condition. - State what the agent must return. - Never say "fix everything."
From tenecsson/playbooks, MIT.
More from tenecsson/playbooks
- 0.529score
human-editor
tenecsson
Use when editing or reviewing existing prose for LLM writing habits, rhetorical padding, or fidelity to an author's voice.
SkillBFreshness: BClaude Code +9 - 0.524score
writing-skills
tenecsson
Use when creating, editing, or validating a reusable skill and you need to keep it concise, discoverable, and behavior-changing
SkillBFreshness: BClaude Code +9 - 0.524score
using-git-worktrees
tenecsson
Use when the user requests a worktree or parallel, experimental, or high-risk work needs isolation from the current checkout
SkillBFreshness: BClaude Code +9 - 0.523score
implementation-quality
tenecsson
Use when implementing or reviewing code changes that need judgment about proportionate testing and verification
SkillBFreshness: BClaude Code +9 - 0.519score
code-review
tenecsson
Use when the user requests code review, review feedback must be evaluated, or a high-risk change warrants an independent technical pass
SkillBFreshness: BClaude Code +9 - 0.518score
brainstorming
tenecsson
Use when a request has material product, behavior, or architecture choices that must be resolved before implementation
SkillBFreshness: BClaude Code +9 - 0.518score
planning-and-execution
tenecsson
Use when a multi-step implementation needs a durable plan or an existing approved plan needs coordinated execution
SkillBFreshness: BClaude Code +9 - 0.518score
systematic-debugging
tenecsson
Use when any bug, failing test, build break, or unexpected behavior needs root-cause analysis before fixes
SkillBFreshness: BClaude Code +9 - 0.498score
supervised-subagent
tenecsson
Use when the user asks to delegate implementation to a subagent
SkillBFreshness: BClaude Code +9 - 0.493score
improve-coverage
tenecsson
Use when the user asks to improve test coverage or uncovered behavior needs a focused coverage pass
SkillBFreshness: BClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Apr 5, 2026 (6 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/tenecsson/playbooks
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from tenecsson
- 0.529score
human-editor
tenecsson
Use when editing or reviewing existing prose for LLM writing habits, rhetorical padding, or fidelity to an author's voice.
SkillBFreshness: BClaude Code +9 - 0.524score
writing-skills
tenecsson
Use when creating, editing, or validating a reusable skill and you need to keep it concise, discoverable, and behavior-changing
SkillBFreshness: BClaude Code +9 - 0.524score
using-git-worktrees
tenecsson
Use when the user requests a worktree or parallel, experimental, or high-risk work needs isolation from the current checkout
SkillBFreshness: BClaude Code +9 - 0.523score
implementation-quality
tenecsson
Use when implementing or reviewing code changes that need judgment about proportionate testing and verification
SkillBFreshness: BClaude Code +9 - 0.519score
code-review
tenecsson
Use when the user requests code review, review feedback must be evaluated, or a high-risk change warrants an independent technical pass
SkillBFreshness: BClaude Code +9 - 0.518score
brainstorming
tenecsson
Use when a request has material product, behavior, or architecture choices that must be resolved before implementation
SkillBFreshness: BClaude Code +9
Cite this page
dispatching-parallel-agents skill. Agent Mart. https://agentmart.dev/skills/tenecsson-dispatching-parallel-agents (last updated 2026-10-24)