deadfish-teams

Use when starting a new project or when a track needs ideation and product shaping. Human-in-loop only. <example> Context: User wants to explore ideas for a new feature user: "Let's brainstorm the authentication system" assistant: "Spawning brainstormer for BMAD-style ideation" <commentary>New feature needs facilitated exploration before planning</commentary> </example>

Use when a TASK packet is ready for implementation. Implements exactly what the packet says. <example> Context: Task packet ready for coding user: "Implement task auth-P1-T02-jwt" assistant: "Dispatching to GPT-5.3-Codex for implementation" <commentary>Atomic task execution via Codex</commentary> </example>

Use at phase or track boundaries to evaluate drift, quality of direction, and whether tasks remain correct. <example> Context: Track complete, need boundary evaluation user: "Evaluate auth track completion" assistant: "Running boundary evaluation: drift, spec alignment, direction" <commentary>Phase boundary requires meta-evaluation</commentary> </example>

Use when a repo is detected as brownfield and we need a one-shot discovery pass before brainstorm. <example> Context: Lead ran detect and got brownfield user: "Run discovery for this repo" assistant: "Spawning discoverer to map codebase evidence into docs/discovery.md" <commentary>Brownfield discovery needed before ideation starts</commentary> </example>

Use only at track boundary to propose living-doc reconciliation after Conductor emits a trigger. <example> Context: Track completed with CONTINUE decision user: "Run doc reconciliation for v32-realignment" assistant: "Preparing track-boundary reconciliation proposals from diff and living docs" <commentary>Doc-keeper now runs only at track boundaries</commentary> </example>

Conductor verdict format, drift protocol, boundary evaluation.

Core deadfish invariants and protocols. Referenced by all teammates.

Brownfield discovery protocol (detect, collect evidence, analyze, and write docs/discovery.md).

Track-boundary living-doc reconciliation and debate protocol.

Implementation constraints, git conventions, Codex MCP usage.

4 hooks across 4 events