---
description: Start a TDD-focused implementation pass
argument-hint: "<goal>"
---

Use the `tdd-tester`, `unit-tester`, and implementation roles from the `flights-web` crew for this goal:

$@

Execution safety:

- Prefer the Pi Crew `team` tool; do not continue as an uncoordinated parent Pi implementation session unless the user explicitly asks.
- Do not call unavailable abstract tools such as `glob`; use `rg --files`, `rg -n`, `find`, `sed`, `nl`, and `git grep`.
- Never repeat the same failed tool call or shell command more than once.
- If a command exits non-zero with no useful output, do not retry it unchanged; inspect source/tests or change the hypothesis first.
- If a focused test fails, use the failure location to inspect and fix code/tests; do not repeatedly grep test output for unrelated terms.
- After two failed verification attempts without a code or test change, stop and report the blocker, current hypothesis, and next concrete fix.
- If five consecutive tool calls add no new information, stop and summarize what is known.

Start by identifying the behavior contract and the smallest failing test. Then implement the minimal change, run focused tests, and ask critic/reviewer roles to check the result before GitOps.
