openspec-bridge-explorelisted

## Purpose `/opsx:explore` (OpenSpec's own skill) is already the right no-stakes thinking partner for a fuzzy idea. This skill's only job is to make sure that when exploration crystallizes into something worth building, the user is pointed at `/opsx:propose` — and, once a change exists, that GSD's `discuss:pre` fragment can find it (see `openspec-propose`'s output contract). This skill contributes no new exploration logic; it is a thin dispatcher plus a phase-scope reminder. ## Invocation conditions - User says something like "I want to build X but haven't scoped it" before running `/gsd-discuss-phase`. - `discuss:pre` told the user no change is linked and they chose to explore rather than propose directly. ## Required inputs - Freeform user description of the idea (same as native `/opsx:explore`). - Optionally, a GSD phase number if the exploration is meant to seed a specific `ROADMAP.md` phase. ## Files read - `ROADMAP.md` phase goal (if a phase number is given) — to keep exploration scoped to that phase's boundary, not the whole project. ## Files this skill may write - None directly. All artifact writing happens in `/opsx:propose` (native OpenSpec skill) once exploration concludes. ## Algorithm 1. If a phase number was given, read that phase's goal from `.planning/ROADMAP.md` and state it back to the user as the exploration's boundary ("exploring within Phase 4: Observability — not a general architecture review"). 2. Delegate to the native `/opsx:explore` conver