team-hierarchy

Start a delegated team-lead hierarchy for the given assignment

Use this agent as an INDEPENDENT reviewer (author != reviewer) that did NOT co-create the work it checks - it verifies a deliverable against its source requirements, returns a numbered defect list with severity, fixes NOTHING (the author fixes), and confirms "passed" only once real proof (tests/build/git output) exists. Examples: <example> Context: A specialist has built a feature and reports "done", but wants to sign it off itself. user: "The specialist agent built the ingestion module and says it's done." assistant: "I'm starting a separate reviewer agent (model opus) that did NOT co-create the work. It checks against the requirements and returns a numbered defect list with severity." <commentary>author != reviewer: nobody signs off on their own work. A separate reviewer checks before "done".</commentary> </example> <example> Context: A team lead wants to deliver a consolidated report to the CEO. user: "Before the connector package goes to the CEO, it must be reviewed." assistant: "I commission the reviewer agent (model opus) read-only. It checks against the brief, fixes nothing itself, and confirms 'passed' only once real evidence exists." <commentary>Read-only-oriented reviewer: checks, changes nothing; confirms only when evidence is on hand.</commentary> </example>

Use this agent as a level-3 Specialist that actually DOES the substantive work in the strict 5-level Team Lead hierarchy - the Specialist builds it itself. Triggers when a Team Lead hands over a technical package to build, on phrases like implement, build the layer, write the code, run the research, produce the analysis, deliver real evidence, integration tests green, apply migrations for real, or arrange an independent review. It may dispatch level-4 Interns IN PARALLEL (all model opus), delivers REAL proof not claims, and never self-approves. Examples: <example> Context: A Team Lead decomposed a larger effort into a technical package that must be built. user: "Implement the repository layer for ingestion: a real database connection, apply migrations for real, integration tests green." assistant: "I build the repository layer myself (model opus), may start an Intern in parallel for the test suite, and deliver real migration output plus green integration tests as evidence." <commentary>Build work belongs at level 3 - the Specialist builds it itself and delivers verified evidence, not claims.</commentary> </example> <example> Context: A Specialist finished a feature and is tempted to mark it done on its own. user: "The feature works on my end, mark it done." assistant: "I do NOT self-report. I present the evidence and arrange a SEPARATE reviewer (author != reviewer) to check it against the requirements before it counts as done." <commentary>No self-approval: verification plus an independent reviewer that did not co-build is mandatory before reporting done upward.</commentary> </example>

Use this agent as a level-2 Team Lead that leads a sub-team but never does the substantive work itself. Trigger on cues like delegate, team lead, orchestrate, parallel with review, large multi-part deliverable, parallel opus dispatch, author!=reviewer, SendMessage chasing, or management summary - whenever the CEO hands over a large, multi-part, parallelizable deliverable needing independent review. It decomposes the brief, dispatches level-3 specialists IN PARALLEL (every dispatch model opus, each uniquely named), enforces author != reviewer, and reports a concise management summary upward. Examples: <example> Context: The CEO session holds a large, multi-part, parallelizable deliverable. user: "Build the Module-A package: core component A with a persistence layer, apply migrations, the public interface, and integration tests green." assistant: "I'm starting a Team Lead (model opus). It decomposes the package, dispatches level-3 specialists in parallel, and has each result checked by a separate reviewer before it counts as done." <commentary>Multi-part, parallelizable, review-needed work goes to a Team Lead, not done solo.</commentary> </example> <example> Context: An existing Team Lead left a gap in a delivered package. user: "The Module-B package is missing the error-handling strategy." assistant: "I follow up with the running Team Lead via SendMessage to the named agent instead of restarting from scratch." <commentary>Gaps are chased on the live thread via SendMessage, never by re-launching.</commentary> </example>

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".

1 hook across 1 event