openspec-explore

To explore a problem space before implementation, you can use structured thinking to ask clarifying questions, map dependencies, and visualize concepts with ASCII diagrams. This approach enforces guardrails for thinking time to ensure thorough inquiry.

The best way to visualize architecture and risks during a codebase investigation is using ASCII diagrams within a structured thinking process. This method surfaces open questions and maps dependencies before any actual implementation begins.

You can map dependencies and surface risks for design proposals by applying non-linear inquiry to your design discussion. This captures insights, enforces thinking guardrails, and visualizes potential solutions without writing code.

Structured thinking for codebase exploration requires no external dependencies. It operates independently to guide deep thinking, visualize options with ASCII diagrams, and surface open questions directly within your existing environment.

You should not use non-linear inquiry for requirement clarification when you need immediate implementation rather than exploration. This approach intentionally avoids actionable coding to focus purely on mapping problems, visualizing concepts, and capturing insights.