chore: add pi prompt shortcuts

.pi/prompts/pi-audit.md

@@ -0,0 +1,13 @@
+---
+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:
+
+$@
+
+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.
+

.pi/prompts/pi-metrics.md

@@ -0,0 +1,13 @@
+---
+description: Show Pi crew and usage metrics
+argument-hint: "[metric-filter]"
+---
+
+Show current Pi and pi-crew metrics for this project.
+
+Use `/team-metrics` for crew metrics, applying this filter if provided:
+
+$@
+
+Also summarize how to inspect token/cost/session reports with `npx @ccusage/pi@latest session`, and clearly separate inference time, crew task duration, and pause-inclusive conversation gaps.
+

.pi/prompts/pi-parity.md

@@ -0,0 +1,11 @@
+---
+description: Compare legacy Angular and React implementation parity
+argument-hint: "<feature>"
+---
+
+Use pi-crew with the `flights-web` team and the `angular-react-parity` workflow for this feature:
+
+$@
+
+Treat `ClientApp/` as the Angular reference and `src/` as the React implementation. Produce or update the business-logic spec, parity matrix, and verification report under `docs/parity/`. Use existing compare scripts and Playwright MCP where useful. Do not edit production code unless I explicitly ask for an implementation follow-up.
+

.pi/prompts/pi-review.md

@@ -0,0 +1,13 @@
+---
+description: Run focused crew review of the current branch or diff
+argument-hint: "[scope]"
+---
+
+Use pi-crew with the `flights-web` team and the `review-only` workflow.
+
+Scope:
+
+$@
+
+Review the current branch or diff for correctness, regressions, test gaps, unnecessary complexity, docs drift, and GitOps readiness. Do not edit files unless a clearly safe documentation or config fix is required and you report it explicitly.
+

.pi/prompts/pi-spec.md

@@ -0,0 +1,11 @@
+---
+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:
+
+$@
+
+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.
+

.pi/prompts/pi-tdd.md

@@ -0,0 +1,11 @@
+---
+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:
+
+$@
+
+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.
+