openspec-explore

Clarifying ambiguous requirements involves surfacing hidden assumptions, open questions, and constraints through exploratory discussion before development begins. This approach ensures you fully understand the problem space and map relevant architecture prior to writing any application code.

Investigating codebase architecture safely requires read-only analysis of files and search patterns to map system behavior. This strict read-only approach prevents accidental application code changes while you diagnose problems and explore how the system behaves.

Analyzing tradeoffs requires comparing options, sketching alternatives, and identifying risks when a decision is not yet obvious. This process helps you evaluate different architectural paths and ground your exploration in the repository's current direction before committing.

Yes, OpenSpec proposals and specs provide context to keep exploration grounded in the repository's current direction. You can use existing proposals, specs, and tasks to guide architecture review and plan changes without modifying application code during the exploration phase.

Exploratory codebase analysis is not suitable when you need to immediately modify application code or implement changes. This approach strictly avoids code changes and focuses solely on read-only file analysis, problem diagnosis, and clarifying requirements before implementation begins.