From team-hierarchy
This skill should be used when a task is large, multi-part, or quality-critical and should be run as a delegated agent organization instead of solo work - it teaches the strict 5-level Team Lead hierarchy (CEO delegates only, never works itself), parallel opus-only dispatch, author != reviewer gating, and mandatory memory upkeep. Triggers on "delegate", "team lead", "orchestrate", "parallel with review", "team-start".
How this skill is triggered — by the user, by Claude, or both
Slash command
/team-hierarchy:team-orchestrationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This pattern runs every larger piece of work as a delegated agent organization
This pattern runs every larger piece of work as a delegated agent organization instead of doing it solo. The main session is the CEO and delegates only — it never does the work itself (sole exception: maintaining the memory).
model: "opus". No exceptions.name; follow up on gaps via SendMessage on the named agent
instead of starting it anew..remember/remember.md, see conventions.md §1).Regardless of whether Ultracode is on or off, this pattern uses exclusively the nested agent hierarchy; if Ultracode is active, the hierarchy takes precedence over its workflow recommendation.
Ultracode is optional — not everyone has it. Both cases are covered:
Decompose → dispatch in parallel → let them work → review separately → fix defects → consolidate → sign off → maintain the memory.
Concretely:
model: "opus", each with a name).Ready-made templates for team-lead, specialist and review assignments: references/prompt-templates.md.
The methodology is run via the bundled subagents team-hierarchy:team-lead,
team-hierarchy:specialist and team-hierarchy:reviewer (all model: opus,
reviewer read-only) plus the slash command /team-start <assignment>.
The opus requirement is additionally enforced deterministically by a PreToolUse hook.
This pattern copies no foreign skills — it further specializes two related Superpowers skills (do NOT duplicate their content, only reference them):
superpowers:dispatching-parallel-agents — pure parallel fan-out for 2+
independent tasks without shared state. Look it up there.superpowers:subagent-driven-development — plan execution with independent
tasks via subagents in the running session.Contrast this with the workflow tool, a flat deterministic phase script with no
nested Team Lead. The workflow tool is a deterministic orchestration script
(code/JS) with hard-wired phases (build → review → fix). It calls agent()
FLAT — all sub-agents on ONE level under the orchestrator, with no nested Team
Leads. That is a legitimate, sensible feature for deterministic pipelines: not
bad, just the wrong tool, because the recursive 5-level hierarchy is structurally
not represented by it (breadth instead of depth, script instead of model
autonomy). The Agent tool used here, by contrast, is recursive — each agent may
itself call the Agent tool (CEO → Team Lead → Specialist → Intern → Assistant).
Each agent is its own Claude instance with its own context window and decides
for itself how to sub-delegate further; there is no central script. In the
harness this tool is called "Agent", officially the "Task tool" — the same
concept. Mnemonics:
On top of that, this plugin lays four fixed specializations:
model: "opus" enforcement via hook on EVERY level — the models prescribe no
model; here it is enforced deterministically.Only model: "opus" is deterministic, and only for an explicitly set model. The
PreToolUse hook checks the dispatch's model field three ways: an EXPLICITLY set
non-opus model (sonnet/haiku) is denied; opus is allowed; and an empty or
missing model is ALSO allowed — a subagent whose model is set only via its agent
frontmatter carries no tool_input.model, so denying would wrongly block it, and
the frontmatter model: "opus" applies instead. The hook rewrites nothing; it only
allows or denies, and is fail-open if jq is missing (allow plus a warning).
Everything else is only guidance, not hard enforceable: "Agent tool instead of
workflow tool", "CEO never does the work itself" and "author != reviewer" are
PROBABILISTIC — skill and CLAUDE.md influence the model, but enforce nothing; only
hooks are deterministic. For details, see the README section "Limitations".
tl-/sp-/rev-/int-/asst-).Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub mguttmann/claude-team-hierarchy --plugin team-hierarchy