openspec-explore

To clarify requirements before implementation, use a guided thinking partner to explore problem framing, surface risks, and map constraints without writing executable code. This approach ensures team alignment on user needs and success criteria during early design sessions.

Yes, you can visualize ideas and map problem spaces using ASCII diagrams during freeform thinking sessions. This exploration mode helps articulate multiple directions and constraints while deliberately keeping the conversation non-implementation focused.

The best way to frame problems and surface risks is through structured exploration guidance that highlights open questions and potential artifacts to capture later. This method maps user needs and success criteria before committing to concrete work.

To transition from exploring requirements to concrete work, exit explore mode using a designated command like "/opsx:new" or "/opsx:ff". This shifts the session from freeform requirement framing to actionable implementation tasks.

Yes, this approach works for team codebase reviews by providing structured exploration guidance and non-implementation thinking prompts. It helps teams investigate problems, visualize options with ASCII diagrams, and capture open questions collaboratively.

The limitation of a non-implementation thinking partner is that it does not produce executable code. It focuses purely on requirement clarification, problem framing, and visualizing options, requiring a mode transition to begin actual development work.