openspec-explore

Clarifying technical requirements before implementation involves investigating ambiguous problems, mapping the current architecture, and comparing options to identify risks. This structured exploration process breaks down vague concepts into concrete decision points and open questions before writing any code.

Codebase exploration for architecture review is the process of inspecting existing patterns and integration points to understand system constraints. You need it when a planned change touches real code, ensuring you map dependencies and surface risks before committing to an implementation approach.

Comparing technical tradeoffs requires analyzing different approaches to surface risks and weigh constraints for product or engineering decisions. This tradeoff analysis evaluates each option against current system patterns, helping you identify the next best question before development starts.

Yes, you can use read-only structured reasoning to investigate codebase changes without writing application code. This approach focuses on analyzing architecture, exploring integration points, and discussing requirements while keeping the exploration completely separate from the actual implementation phase.

The best way to break down vague product ideas is through idea exploration that maps possibilities and identifies decision points. This process aligns with existing design artifacts to compare approaches, weigh constraints, and clarify requirements before transitioning into actual implementation.