teamlisted

## Context (gather first) Run these and read the output before planning: ``` git branch --show-current git status --short ``` ## Pipeline ``` Read → Decompose → Plan → Gate 1 → Assign → Run → Gate 2 → Synthesize ``` The input — the text after `/team` (Claude Code) or `$team` (Codex) — is the user's natural-language goal. Run the pipeline. Don't ask permission for read-only work. Surface only when a gate fires. ## 0. Required reading (before Interpret) Blocking, in order: 1. **Always** read `references/SKILL.md` — the project doc index. Use it to identify which reference files are relevant to the goal. 2. **If the request requires building** (writing/editing code, creating files, scaffolding features), **also** read `references/development/conventions.md` before any Plan node that writes code. No code-writing agent is dispatched until this read has happened in the main thread. Cite both reads in the Gate 1 checklist as the first row(s). Skipping either is a planning failure — roll back to step 0. > **No `references/SKILL.md`?** The reference layer isn't set up here — skip this step and work > from the codebase itself. **Say so at the top of the run.** Don't invent a reference doc, > and don't halt over its absence. [`/setup`](../setup/SKILL.md) builds it, in either mode. ## 1. Interpret Extract: real intent · success shape (advice / fix / comparison / plan) · scope · destructive? State a one-line restatement so the user can interrupt: > *"Interpreting as: <X>. Disp