openspec-explore

Exploratory thinking for software requirements uses guided questioning and visual mapping to surface assumptions, clarify goals, and align scope before coding begins, reducing rework and preventing premature implementation.

To facilitate a brainstorming session without writing code, describe your goal and constraints to a guided thinking partner that enforces a strict no-implementation stance, uses open-ended prompts, and maps problems visually using ASCII diagrams.

Yes, you can use ASCII diagrams for design exploration during early product discovery to visually map problems and alternative directions, enabling teams to align on constraints and frame problems before committing to code.

The best way to frame problems and surface assumptions is engaging in structured, open-ended exploration that creates OpenSpec artifacts like proposals and designs while maintaining a thinking-only stance to ensure complete alignment.

No, this exploratory thinking approach enforces strict guardrails that prevent code generation, focusing entirely on creating OpenSpec artifacts such as designs and proposals to clarify requirements without executing or writing implementation logic.

You should avoid using an open-ended exploration partner when your project requires immediate code implementation, technical execution, or final technical specifications rather than early discovery, problem framing, and conceptual design alignment.