openspec-explore

To explore design ideas, use a thinking partner that reads relevant files and references to surface questions. It guides open-ended sessions to clarify requirements, map risks, and investigate alternative approaches before you commit code changes.

The best way to visualize architecture is by generating ASCII diagrams and structured thought traces. This illuminates dependencies and trade-offs during early design discussions, providing clear visual references without requiring actual code generation.

Yes, you can scope problems across software projects by running an exploratory session. The thinking partner guides open-ended discussions to investigate problems and surface considerations, reducing ambiguity and rework before development.

This thinking partner only helps with requirements clarification and does not generate code. It focuses on exploring ideas, proposing questions, and guiding open-ended thinking sessions to ensure your design specs are solid before implementation.

To start an exploratory session, simply describe your problem. The thinking partner reads relevant files, maps questions, visualizes options with ASCII diagrams, and surfaces key considerations to help you investigate codebase problems.

You should not use an exploratory thinking session when you need actual code generation or immediate implementation. It is designed specifically for early design discussions, requirements clarifications, and problem scoping rather than writing code.