openspec-explore

To clarify requirements before implementation, use an exploratory mode that reads repository files and OpenSpec artifacts, asks open-ended questions, and surfaces tradeoffs without writing code. This grounds brainstorming in the actual codebase context.

The best way to map architecture during discovery is investigating the codebase by reading existing repository files and OpenSpec change artifacts. This approach surfaces integration points and references existing context to frame design decisions.

Yes, you can review OpenSpec artifacts and brainstorm design alternatives without modifying code. The exploration mode explicitly refuses to implement code, allowing you to safely investigate problems and surface constraints until you exit the mode.

To surface risks and frame architecture decisions, highlight potential unknowns, constraints, and integration points during your investigation. You can then capture these insights into proposals or design artifacts when requested.

Yes, exploring a codebase in this mode captures insights into proposals or design tasks. It identifies potential spikes and open questions during investigation, offering to document findings into design artifacts when you request them.

Exploratory thinking refuses to implement code to keep discovery and ideation separate from changes. This ensures you fully investigate problems, surface tradeoffs, and clarify requirements before committing to any architectural modifications.