openspec-explore

To clarify requirements before implementation, you can use early-stage exploration to turn vague ideas into clear questions, map architecture, and surface assumptions. This read-only investigation helps you reason through the problem before committing to code changes.

The best way to investigate a codebase when the design is unclear is to read files, trace patterns, and map architecture relevant to the discussion. This allows you to understand how existing components fit together before making a decision.

To perform a tradeoff analysis for architectural approaches, you compare options, surface risks, and reason about scope. This process helps evaluate different design paths and clarify the next decision without writing application code.

Yes, you can brainstorm ideas and draft artifacts without writing application code by using read-only investigation and natural-language reasoning. This allows you to scope discussions and generate preliminary designs independently of implementation.

You should not use codebase exploration when requirements are already clear and you are ready to write application code. This approach is designed for early-stage scoping and tradeoff analysis, not for executing implementation changes.