openspec-explore

To explore ideas without writing code, use a thinking partner that outlines the problem space, surfaces questions and risks, and visualizes options with ASCII diagrams. This keeps your exploration strictly at the ideation level without jumping to implementation.

The best way to brainstorm open-ended problems is to enter an exploration stance that offers varied directions and proposes exploratory questions. This method identifies uncertainties and risks, helping you investigate the problem space deeply before committing to artifacts.

To visualize options during early problem-solving, use a guided thinking partner that generates ASCII diagrams. This approach maps multiple directions and possibilities visually, clarifying relationships within the problem space without requiring technical implementation.

No, this requirements exploration tool does not write code or implement features. It maintains a strict non-implementation stance, focusing entirely on thinking at the ideation level, surfacing questions, and proposing artifacts only if needed for further clarification.

You should use a thinking partner when you need to clarify requirements, investigate problems, or brainstorm ideas before coding. It is essential for open-ended exploration where identifying risks, surfacing unknowns, and visualizing varied directions prevent premature implementation decisions.

Yes, you can use ASCII diagrams to map out risks and multiple directions. The exploration process visualizes possibilities and outlines the problem space directly, ensuring you can see varied directions and surface uncertainties clearly before proposing any artifacts.