subagent-coordination

Name: subagent-coordination
Author: omnigentx

31stars13forks

How to install subagent-coordination?

omnigentx/jarvis/subagent-coordination

$npx -y skills add omnigentx/jarvis --skill subagent-coordination

Installs into the current project.

Summary

Patterns for coordinating work delegation in multi-agent teams. Covers sequential and parallel task dispatch, review checkpoints, and quality gates.

Files · 1

View on GitHub

SKILL.md

1	# Subagent Coordination
2
3	Inspired by [NeoLabHQ/subagent-driven-development](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/sadd/skills/subagent-driven-development).
4
5	Patterns for effectively coordinating multi-agent task execution.
6
7	## Core Principle
8
9	Fresh context per task + review between tasks = high quality, fast iteration.
10
11	## Execution Patterns
12
13	### Sequential (Tightly Coupled Tasks)
14	When tasks depend on each other:
15	1. Dispatch one task at a time
16	2. Review output after each task
17	3. Only proceed when current task passes review
18	4. Fix issues before moving to next task
19
20	### Parallel (Independent Tasks)
21	When tasks are independent:
22	1. Group tasks by domain (different files, subsystems)
23	2. Dispatch one agent per domain
24	3. Review all outputs together after completion
25	4. Check for conflicts between parallel changes
26
27	## Task Dispatch Best Practices
28
29	### Good Task Prompts
30	- Focused — One clear problem domain
31	- Self-contained — All context needed is included
32	- Specific about output — What should the agent return?
33	- Constrained — "Don't change files outside of X"
34
35	### Bad Task Prompts
36	- ❌ Too broad: "Fix all the tests"
37	- ❌ No context: "Fix the race condition"
38	- ❌ No constraints: Agent might refactor everything
39	- ❌ Vague output: "Fix it"
40
41	## Review Checkpoints
42
43	After each task or batch:
44	1. Read summary — Understand what changed
45	2. Check for conflicts — Did agents edit the same code?
46	3. Run verification — Tests, lint, build
47	4. Spot check — Review critical changes manually
48
49	## In Meeting Context
50
51	As PM in a meeting:
52	- Assign clear tasks to DEV: "Implement X in file Y"
53	- Ask QE to review after DEV completes
54	- If FAIL verdict, direct DEV to fix specific issues
55	- Track progress across turns

People who liked this also viewed

6 picks

Type

paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026157k5
subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026154k259k
dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026143k259k
browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 202685k4.6k
wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 202675k182k
wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 202666k137

subagent-coordination

31stars13forks

View on GitHub

How to install subagent-coordination?

omnigentx/jarvis/subagent-coordination

$npx -y skills add omnigentx/jarvis --skill subagent-coordination

Installs into the current project.

Summary

Patterns for coordinating work delegation in multi-agent teams. Covers sequential and parallel task dispatch, review checkpoints, and quality gates.

Files · 1

View on GitHub

SKILL.md

1	# Subagent Coordination
2
3	Inspired by [NeoLabHQ/subagent-driven-development](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/sadd/skills/subagent-driven-development).
4
5	Patterns for effectively coordinating multi-agent task execution.
6
7	## Core Principle
8
9	Fresh context per task + review between tasks = high quality, fast iteration.
10
11	## Execution Patterns
12
13	### Sequential (Tightly Coupled Tasks)
14	When tasks depend on each other:
15	1. Dispatch one task at a time
16	2. Review output after each task
17	3. Only proceed when current task passes review
18	4. Fix issues before moving to next task
19
20	### Parallel (Independent Tasks)
21	When tasks are independent:
22	1. Group tasks by domain (different files, subsystems)
23	2. Dispatch one agent per domain
24	3. Review all outputs together after completion
25	4. Check for conflicts between parallel changes
26
27	## Task Dispatch Best Practices
28
29	### Good Task Prompts
30	- Focused — One clear problem domain
31	- Self-contained — All context needed is included
32	- Specific about output — What should the agent return?
33	- Constrained — "Don't change files outside of X"
34
35	### Bad Task Prompts
36	- ❌ Too broad: "Fix all the tests"
37	- ❌ No context: "Fix the race condition"
38	- ❌ No constraints: Agent might refactor everything
39	- ❌ Vague output: "Fix it"
40
41	## Review Checkpoints
42
43	After each task or batch:
44	1. Read summary — Understand what changed
45	2. Check for conflicts — Did agents edit the same code?
46	3. Run verification — Tests, lint, build
47	4. Spot check — Review critical changes manually
48
49	## In Meeting Context
50
51	As PM in a meeting:
52	- Assign clear tasks to DEV: "Implement X in file Y"
53	- Ask QE to review after DEV completes
54	- If FAIL verdict, direct DEV to fix specific issues
55	- Track progress across turns

People who liked this also viewed

6 picks

Type