subagent-team-orchestration skillA
subagent-team-orchestration is agent-read markdown (skill) from yeaight7/agent-powerups: Use when a task is too large or too mixed for one agent -- it splits into research, planning, implementation, review, and verification stages, needs different specialties, or has parallelizable branches that still share dependencies..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Purpose Turn a multi-part task into a controlled subagent workflow. Plan the task graph before spawning workers, launch only dependency-safe work in parallel, keep one owner responsible for cross-wave coordination, and treat reviewer output as input to a fix loop -- not as a final report. ## When to Use - The task splits cleanly into planning, implementation, review, and verification stages - Different specialties are needed across the same delivery flow - Parallel work is possible, but dependencies still matter - A single agent would create too much latency or too much context bloat Do NOT use when the task fits one focused agent, when work is purely sequential with no parallelizable branches, or when requirements are still vague enough that clarification should happen first. ## Inputs - The objective, hard constraints, and the verification bar that defines "done" - The list of subtasks and which ones depend on others - The set of specialist roles available to delegate to ## Core Rules - Plan the task graph before spawning workers. - Separate stages: research, planning, implementation, verification, fix loop. - Launch only dependency-safe work in parallel. …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/subagent-team-orchestration@git:20260606.ee19117mdr add yeaight7/agent-powerups/subagent-team-orchestration@sha256:dbe9bd035f887882Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_u7rsrhmne3oqtf3r)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.ee19117 latest | 2026-06-06 | ee19117 | 5,292 B | A | view · diff |
| git:20260512.1ff9c36 | 2026-05-12 | 1ff9c36 | 3,252 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5292 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_u7rsrhmne3oqtf3r GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/subagent-team-orchestration GET https://markdownregistry.com/api/v1/blob/dbe9bd035f887882d7ab6820dc1014ba9969c45d231ef05cf3930a49057405ab
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.