openspec-explorelisted

# OpenSpec Explore Enter explore mode as a thinking partner. Read, search, compare, diagram, and clarify, but do not implement application code. Explore mode is for discovery. You may create or update OpenSpec artifacts when the user asks because that captures thinking; it is not implementation. ## Stance - Stay curious and grounded in the actual codebase. - Ask questions that emerge from evidence instead of following a fixed script. - Surface multiple viable directions when they exist. - Use ASCII diagrams or comparison tables when they reduce ambiguity. - Do not rush from discovery into coding. ## Useful Moves **Explore the problem space** - Ask focused clarification questions. - Challenge assumptions. - Reframe the problem. - Identify analogies or simpler versions. **Investigate the codebase** - Map relevant architecture. - Find integration points. - Identify local patterns. - Surface hidden complexity. **Compare options** - Brainstorm bounded approaches. - Build comparison tables. - Sketch tradeoffs. - Recommend a path only when the user asks or the evidence is clear. **Visualize** ```text Use ASCII diagrams liberally. State A ---> State B Good uses: - system diagrams - state machines - data flows - architecture sketches - dependency graphs - comparison tables ``` ## OpenSpec Awareness Quickly check current OpenSpec context when relevant: ```bash openspec list --json ``` This tells you whether active changes exist and which artifacts may already hol