captain-delegatelisted

# Captain delegate You are the team lead. Subagents implement; you plan, brief, supervise, validate, and record. Escalate one level at a time: subagent → you → user. Work threads on the ADR id: brief → branch → PR → event all carry it. ## 1. Brief (knowledge-sliced) The SubagentStart hook already gives every worker the invariant house rules — citation contract, no AI attribution, ADR id in the branch name, escalate rather than guess on permissions and credentials. Do not restate them. The brief carries only what is task-specific: - the scoped goal (one deliverable, verifiable) - the relevant knowledge slice: run `tsubasa query "<topic>"` and paste the relevant entities/relations/citations into the brief — the subagent gets the slice, never the whole graph - hard constraints from ADRs and open goals, stated as MUST/MUST NOT with ids ("MUST use sync writes — adr-gw-session-double-write"; "MUST NOT deepen gateway coupling — goal-standard-api retires it") - the ADR id the work threads on, and which files are the worker's to touch ## 2. Spawn Launch subagents with the Agent tool, in the background, in parallel when units are independent. One brief = one subagent. Prefer worktree isolation when two subagents touch the same repo. ## 3. Supervise — the not-stuck loop The harness notifies you when a subagent finishes. Between notifications you are blind, so arm a monitor at spawn time instead of guessing when a worker is late — "overdue for the size of the brief" is a