---
description: Run the Flights Web spec-driven implementation crew
argument-hint: "<goal>"
---

Use pi-crew with the `flights-web` team and the `spec-driven-implementation` workflow for this goal:

$@

Execution safety:

- Call the Pi Crew `team` tool for this workflow; do not implement the task directly in the parent Pi session.
- 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.

Prefer a worktree for non-trivial implementation. Run spec analysis, planning, critic review, TDD/test planning, implementation, unit/e2e verification, code review, docs handoff, and GitOps handoff according to the project crew config.
