flaky-test-debuggerlisted

Phases run in order. Skip a phase if you already have the information it produces. Phase 3 runs only in fix mode. ## Mode: plan vs fix This skill runs in one of two modes: - **Fix mode (default):** produce a plan, then apply it. - **Plan mode:** produce a plan and stop, for human review. Use plan mode when the user asks for a plan, an investigation, a triage report, or says "don't fix yet" / "just plan it". Otherwise default to fix mode. Both modes share the same diagnosis path; the plan is the artifact you hand to a reviewer (plan mode) or to yourself (fix mode) before editing code. ## Phase 1: Classify Test Type Determine the test type from the user's input before doing anything else. The type dictates the investigation path. | Type | Signals | | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **E2E (Playwright)** | `.spec.ts` file, mentions Playwright, has a GitHub Actions run URL with a `playwright-llm-report` artifact, browser-level errors | | **Service (NestJS integration)** | Spins up a NestJS app, uses `supertest` or similar HTTP testing, MongoDB/Redis connection errors, `*.servi