dev-teamlisted

# Dev Team ## Overview Orchestrate an agent team that works like a thin, evidence-driven loop: **clarify → draft → plan → fan out candidates → refine on profiling evidence → report best + alternatives**. The lead (you, the current session) is the only agent that spawns or stops teammates; it coordinates specialized workers and groups — researchers, implementers, reviewers, builder, profiler, and testers — through eight phases (Phase 0–7): clarify, startup, draft-and-plan, the candidate fan-out/refine loop, QA, verification, reporting, and post-mortem. The defining shape: instead of producing one implementation, the team explores **2–3 distinct candidate implementations in parallel**, each in its own git worktree, then **refines the leading candidate(s) using the profiler's ranked optimization directions** until one meets the task contract's promotion criteria. The final report presents the promoted candidate *and* the alternatives, with QA and profiling evidence for each. **Core principles:** - **The lead owns lifecycle; teammates own the message bus.** Only the lead can spawn or stop a teammate (a teammate has no Agent tool and cannot spawn anything). Results flow peer-to-peer — teammates hand their output directly to whoever needs it, not back through the lead. - **Spawn on demand, stop on delivery.** The lead spawns a worker or group only when its work exists and stops it once it has delivered, keeping the number of live teammates small. A crowd of idle team