openspec-explore

To clarify requirements before implementation, use a thinking partner to surface assumptions and explore multiple directions safely. This enforces a thinking-only stance to analyze trade-offs and improve decision quality without writing code.

The best way to explore ideas for design discussions is using guided thinking prompts that frame problems and clarify requirements. Visual support like ASCII diagrams helps communicate ideas while avoiding premature implementation.

Start problem framing for codebase investigations by activating explore mode and describing the challenge. State the problem and desired outcome, then ask for questions, options, and potential next steps.

Yes, you can use visual diagrams to communicate ideas without writing code. Visual thinking support includes ASCII diagrams and narrative sketches to express concepts during ideation and requirement discovery.

You should avoid direct implementation during requirement discovery when you need to surface questions, risks, and alternative directions first. Safe exploration prevents premature coding, enabling better decisions and trade-off analysis.