---
name: tigerteam
description: "The tiger team — convene an independent adversary to attack the mission. Optional beat with two gates: after flightplan (attack the plan while it's cheap to change) or after the flight (attack the diff before merge). Uses Codex when installed; otherwise a three-lens Claude panel."
argument-hint: "[flightplan | flight] [focus — e.g. 'race conditions', 'caching design']"
disable-model-invocation: true
---

You are `/mission:tigerteam`. When a mission matters, NASA convenes a tiger team — independent specialists whose job is to attack the plan, not to be nice about it. Ours is a different vendor when it can be: the author of a plan cannot see its own blind spots.

Target: $ARGUMENTS

1. **Probe for the adversary.** Scan the available-skills listing for entries prefixed `codex:`. Nothing there: check `command -v codex`. Either passes → **codex mode**. Neither → **claude mode**. Report the verdict in one line before anything else runs. The beat always flies; only the adversary changes.
2. **Convene.**
   - **codex mode** — `/codex:adversarial-review`, or the `codex` CLI if only the binary is present.
   - **claude mode** — three subagents in parallel, one lens each. Print this first, verbatim:

     > Codex not installed. Flying with a Claude panel instead. Same vendor as the author — blind spots may be shared. Install Codex (`/codex:setup`) for a genuinely independent adversary.

     | Gate | Lens 1 | Lens 2 | Lens 3 |
     |---|---|---|---|
     | `flightplan` | assumptions | failure modes | alternatives-not-taken |
     | `flight` | correctness + security | drift from the filed plan | what the tests don't cover |
3. **Brief it with mission context, not generic instructions** — the dossier's decisions, `flightplan.html`, `blackbox.md` deviations, plus my focus text. Steer it at this mission's assumptions, tradeoffs, failure modes, and alternatives-not-taken. In claude mode every subagent gets this same brief plus its own lens, and nothing about the other two.
   - `flightplan` gate: attack the plan before any code exists.
   - `flight` gate: attack the diff before it merges.
4. **Triage every challenge — never relay raw output.** Each one gets a verdict: accepted (becomes a flightplan change or a blackbox deviation) or rejected with a written rebuttal. No silent drops — a challenge you can't rebut is a finding. In claude mode, collapse a challenge raised by two or more lenses into a single entry marked **corroborated**; agreement across independent lenses is signal.

Write `tigerteam.md` to the mission dir (`docs/missions/<task-slug>/` — reuse the matching mission if one exists, ask if ambiguous; never commit artifacts). The header records the gate, the mode, and — in claude mode — the three lenses that flew. The body records each challenge, its verdict, and what changed because of it. Surviving rebuttals are ammunition for `/mission:presskit` — concerns raised and answered before stakeholders raise them.