openspec-explore

Requirement clarification involves identifying assumptions and mapping integration points through read-only investigation. You can use a safe exploration mode to reframe problems and ground your thinking in reality by inspecting existing files without implementing features.

Option comparison for software changes is best handled by generating tradeoff tables and visual diagrams like state machines or data flows. This approach surfaces decision tradeoffs clearly, making it easier to choose an architecture path before proposing implementation.

Yes, you can map codebase architecture through read-only research that strictly prohibits writing code or implementing features. This safe thinking mode optionally captures insights into non-implementing artifacts only when explicitly requested, preventing premature auto-generation.

You need exploration mode for requirement discovery when facing complex ideas that require deep investigation to prevent writing code that misses the real problem. It helps surface hidden assumptions, compare architectural options, and align decisions before committing to actual implementation.

Yes, OpenSpec exploration supports recording investigated insights into proposals, designs, specs, or tasks. It offers to capture decisions into OpenSpec artifacts without auto-capturing, ensuring your requirement discovery and architecture mapping remain strictly read-only and implementation-free.