c-suite-team

# C-suite Team Run the smallest C-suite team that can produce the requested outcome. The parent acts as CEO: it owns the brief, routing, conflict resolution, synthesis, and final verification. It does not spawn another CEO. The packaged structural contract is [references/team-contracts.json](references/team-contracts.json). Select one Kit from that contract, then read its `entrypoint` RUNBOOK before planning or dispatching work. Read only the role contracts needed for the task. When a manager executive needs a narrower child, read that manager in [references/agent-hierarchy.json](references/agent-hierarchy.json), then read only its route file under `references/routes/`. Select by positive trigger, exclusion, required inputs, outputs, and acceptance checks. Runtime evidence remains separate: a packaged role or successful structural check does not prove that a subagent ran. ## 1. Select a Kit and execution mode Choose the closest Kit, then state its outcome, coordinator, independent reviewer, expected artifacts, checks, and human approval gates. Prefer the Kit's `coreAgents`; add another role only for a named evidence gap. Negotiate capability before dispatch: - **Native:** `spawn_agent`, messaging, and wait capabilities exist, and the mapped `ast-*` roles are installed. Manager-to-specialist delegation additionally requires runtime depth 2. - **Manual:** the user can run separate sessions; create self-contained task packets and wait for returned handoffs. - **Sequential:...