openspec-explore

To explore codebase ideas and frame problems before writing code, use a thinking partner that reads your repository, searches code, and surfaces questions and risks to clarify requirements before any implementation begins.

Investigating requirements using your existing codebase is best handled by a thinking partner that reads files and searches the repository to inform discussions, grounding your design ideation in actual code artifacts rather than abstract concepts.

Yes, you can use OpenSpec exploration to map out design directions without implementing changes, as it strictly stays within exploration boundaries, avoids writing code, and suggests artifacts when appropriate for early discovery.

Visual thinking and ASCII diagrams help with software design ideation by encouraging sketches to communicate structure and flow, allowing teams to visualize freely and follow the conversation wherever it goes during early discovery.

The limitations of using a thinking partner for early discovery include staying strictly within exploration boundaries and avoiding writing or implementing code, meaning it cannot produce final implementations and must adhere to OpenSpec guardrails.