openspec-explore

To explore and clarify requirements before implementation, use a structured thinking partner to brainstorm, map options, and investigate problems. This approach surfaces unknowns and visualizes scenarios without forcing a workflow or committing to code.

The best way to investigate a codebase during early design is to use an exploratory thinking mode that reads files and searches code. This surfaces risks and contextual questions, helping you frame the problem deeply before starting actual development.

Yes, you can generate diagrams while brainstorming technical scenarios. The exploration process emphasizes visual thinking, mapping out questions and options visually to help clarify complex requirements and design pathways.

To map out OpenSpec artifacts and change proposals, engage in a guided exploration session. The thinking partner surfaces avenues for these artifacts during your investigation, ensuring non-implementation exploration aligns with your project's specification needs.

Yes, exploratory thinking works without forcing a rigid workflow. The process satisfies non-implementation exploration needs by acting as a curious, non-prescriptive partner, allowing you to frame problems naturally without committing to specific steps.

Use a thinking partner for problem framing when you need to surface risks, unknowns, and clarify requirements before writing code. It is ideal for early design discussions and codebase analysis where deep scenario exploration is required.