openspec-explore

To explore design tradeoffs and map requirements before writing code, use an explore mode thinking partner that identifies problems, proposes directions, and surfaces constraints. It clarifies early-stage product decisions using visual diagrams.

Framing early-stage problems across a codebase involves surfacing questions, risks, and unknowns through open-ended exploration. A thinking partner maps options using visual diagrams to clarify concepts before committing to a specific direction.

Yes, a thinking partner skill can provide OpenSpec artifacts such as proposals, designs, and specs on demand. It surfaces choices and constraints during exploration but never performs changes or executes actual code.

Yes, requirements exploration works entirely without executing or writing code. The process maps potential directions, asks natural questions, and uses ASCII diagrams to ground the investigation while strictly avoiding code generation.

You should not use an explore mode thinking partner when you need to directly write, execute, or generate code changes. It is designed strictly for early-stage problem framing and mapping options, not for implementing software modifications.