openspec-explore

To explore codebase architecture and map requirements before writing code, you can enter a non-implementation mode that reads your codebase, surfaces unknowns, and visualizes options with ASCII diagrams. This provides a structured thinking session to clarify problem framing safely.

The best way to brainstorm ideas and investigate problems without generating code is using a thinking partner stance that enforces non-code generation. It allows reading and investigating codebases while providing visualization aids to map questions and explore directions safely.

Yes, you can use a thinking partner to discover requirements and visualize options for complex ideas. It facilitates deep exploration by mapping questions, gathering context from existing codebases, and providing ASCII visualization aids during problem framing sessions.

Yes, codebase discovery mode works specifically for deciding whether to start a change or refine requirements. It provides a safe space to investigate problems, gather context, and surface unknowns before any implementation begins, ensuring your thinking time precedes changes.

The primary limitation of this non-implementation exploration mode is that it strictly enforces non-code generation. While it allows reading and investigating codebases to gather context, it cannot be used to implement changes, write patches, or generate actual code solutions.