---
description: Run technical debt audit with file-cited findings
argument-hint: "[scope]"
---

Use pi-crew with the `flights-web` team and the `tech-debt-audit` workflow.

Scope:

$@

Execution safety:

- Call the Pi Crew `team` tool for this workflow.
- 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.
- After two failed verification attempts without new evidence, stop and report the blocker.
- If five consecutive tool calls add no new information, stop and summarize what is known.

Audit architecture, consistency, type contracts, test debt, dependency/config debt, performance, observability, security hygiene, and documentation drift. Prefer file:line-cited findings and a ranked remediation plan. Do not edit production code.
