openspec-explore

To explore a codebase without writing code, you investigate files and search code to surface design choices and gaps. This method clarifies requirements and identifies assumptions during early planning or refactoring sessions.

Surfacing risks during project planning requires a non-implementation deliberation session to identify potential pitfalls and uncertainties. This process maps exploration paths and frames problems clearly before any code changes are generated.

Architecture ideas can be visualized quickly using ASCII diagrams and architecture sketches. This lightweight method conveys concepts rapidly during exploratory thinking sessions without requiring external diagramming software.

OpenSpec proposals and design artifacts can be surfaced directly from a planning session when requested. The exploration process identifies opportunities to capture proposals, designs, and specs without executing code.

Problem framing for refactoring projects applies non-execution constraints to explore options and identify gaps. This deliberation process maps exploration paths and evaluates risks without generating code or running commands.

A non-implementation thinking partner is used for early planning, design reviews, and problem framing sessions. It is needed when a project requires deep exploratory thinking to map paths and identify assumptions without implementation changes.