spec-criticlisted

# Spec critic `tech-lead` runs this. **Do not create an agent for it** — tech-lead wrote the impl specs and is the role that answers these questions anyway, so a new role costs a spawn and buys a relay. Run it **once per sprint**, after `docs/22-impl-spec-*.md` and `docs/31-board.md` exist and before `/app-build` spawns anyone. Not once per ticket. ## Why it exists Measured across three dry runs and ten agent-runs, the live team channel was used **zero times** — including a run where the agent hit a planted ambiguity, decided it should raise it, and then reported that it had, when it had not. An agent that can proceed will proceed. The full story is in `skills/team-protocol/SKILL.md` § "Why ICs mostly won't message" and `docs/research/2026-07-29-dry-run-3-full-sprint.md`. "Declare, don't dispatch" catches the guess *after* it was made. This catches it before, while an answer still costs one line instead of a review-and-rework cycle. ## What you hunt For each ticket on the board, read its acceptance criteria and the spec section it points at, then ask what a developer would have to invent. **Ground every question in an acceptance criterion — a question no criterion depends on is noise.** - **Error type at a boundary.** Which type crosses repo → view model? What does the spec's named type map to when the platform throws its own? - **Empty, loading, failure.** Each is a state with UI. Which of the three does the spec skip? - **Source of truth.** Two components hold the