flow-debuglisted

## When to use this Unexpected behavior where you do not yet have a failing test, type error, or clear error message to hand to `/flow-fix`. The goal is to identify root cause and produce a handoff artifact. This command does not fix anything. Use `/flow-fix` instead when you already have a failing signal and know roughly which file is responsible. Use `/flow-plan` instead when root cause is already understood but the fix is structural. ## Procedure 0. Resolve external context per `rules/external-context.md`, using the debugger agent for lookups. Extract observed behavior, expected behavior, entry point, and repro steps from what comes back. If no connected tool matches the URL's domain, say so and ask for the content pasted inline instead. 1. From the resolved arguments, confirm: observed behavior, expected behavior, entry point (route, function, event), any reproduction steps already known. If the observed vs expected distinction is still absent after step 0, stop and ask before proceeding. 2. Delegate fault localization to the debugger agent (Agent tool, subagent_type: debugger, foreground). Constraint on the caller: the debugger has no MCP tools by design, so its prompt must carry fully resolved plain text - never a link. Prompt: the resolved context plus this procedure for it to follow: - Reproduce: run the narrowest command or interaction that triggers the behavior; confirm it reproduces consistently, attempting 3 times before concluding non-deterministic. -