openspec-explore

To clarify vague software requirements before implementation, you can explore ideas, surface hidden assumptions, and translate fuzzy requests into concrete problem statements. This investigation process maps architecture constraints to ensure your direction is grounded.

The best way to investigate an existing codebase for architecture tradeoffs is to read files, trace system behavior, and map flows. This exploration reveals how the system works today and highlights hidden complexity before you commit to a redesign.

To compare refactoring versus redesigning an integration, weigh multiple approaches, tradeoffs, and constraints. This option comparison reveals hidden complexity and helps you decide the best direction to explore next without writing application code.

Yes, you can review OpenSpec change proposals and trace related artifacts without writing code. The exploration process reads active changes, captures insights, and grounds your design proposals in the current work context.

Yes, codebase exploration supports capturing insights directly into specs and designs. It traces system behavior and maps architecture context to produce concrete proposals without generating application code.

You should focus on problem discovery instead of coding when the problem is still forming and you need a thoughtful partner. Use this approach to surface risks, investigate requirements, and clarify options before committing to implementation.