flow-explorelisted

## When to use this The ask is too thin or the codebase area too unfamiliar to shape a brief or a plan yet - a one-line request, a bare link to a ticket or doc with little inline description, or a task that touches a part of the codebase nobody here has mapped recently. The goal is a findings report surveying what the task likely needs and how it could be built, not a committed brief or plan. Use `/meta-feature` instead when the ask is already clear enough to shape into acceptance criteria without codebase research. Use `/flow-plan` instead when the task and a chosen approach are both already confirmed. ## Procedure 0. Resolve external context per `rules/external-context.md`. If no connected tool matches the URL's domain, say so and ask for the content pasted inline instead. 1. Do the following: 1. State the task in one sentence, your own words. 2. Run the requirements-clarity check from `/flow-plan` against it, checking whether the task statement is: - Testable - Unambiguous - Complete - Consistent 3. Unlike `/flow-plan`, do not stop on a flag here - explore's job is to investigate the gap, not block on it. 4. Carry every flag into the report. 2. Quick codebase skim: read project CLAUDE.md, grep for existing patterns that resemble the task, identify candidate modules or files. Keep this to a handful of tool calls - enough to name 2-4 plausible implementation directions, not the research itself. If nothing plausible turns up, say so a