explore-workflowlisted

# explore-workflow (Dynamic Workflow asset) A Dynamic Workflow asset (see `CLAUDE.md` -> "Dynamic Workflow Assets"; `review-workflow` is the reference example). `explore.workflow.js` is executed by the `Workflow` tool, invoked from `/lets:explore`'s Workflow Mode via: ``` Workflow({ scriptPath: "${CLAUDE_PLUGIN_ROOT}/skills/explore-workflow/explore.workflow.js", args }) ``` `${CLAUDE_PLUGIN_ROOT}` is substituted at command-load time, so `explore.md` carries the literal absolute path. Treat `explore.workflow.js` as a template the command points at, not a script to reproduce inline. ## Why this is a transparent performance lever (not autonomous) `/lets:explore --workflow` produces the SAME result as the standard Task path - only the per-agent idea dumps stay off-context. The scout (Step 2) and the signal-driven agent selection (Step 3) stay IN-CONTEXT in `explore.md` (the selection mirrors review/opinion, which also select from context the orchestrator already has); the web-research stage (current community standards), the ideate fan-out, and the cluster all move into the workflow (off-context). The interactive dialog stays in-context after the aggregate returns. (The standard Task path gathers the equivalent web brief in-context via the orchestrator - see `explore.md` - so the two paths stay equivalent.) So `--workflow` is a context-savings lever on a large fan-out, not an added methodology (there is no verify/judge stage - cluster is a SEMANTIC dedupe + impact-sort, an o