openspec-explore

To explore ideas and clarify requirements before codebase changes, you need a dedicated problem framing session to surface thinking directions, questions, and risks. This approach visualizes systems with ASCII diagrams to inform decisions before implementation begins.

Yes, you can visualize system data flows and codebase investigations using ASCII diagrams and lightweight sketches. This visual reasoning method surfaces unknowns and next steps to guide design discussions without writing any actual implementation code.

The best way to frame problems and surface risks during a design discussion is using an explore-mode companion. It guides deep thinking, highlights multiple directions, and clarifies requirements, potentially generating OpenSpec artifacts or designs when requested.

This codebase analysis approach does not write features or implement code. It focuses entirely on problem framing and visual reasoning, though it may generate OpenSpec artifacts or designs to document the exploration when explicitly asked.

To start a problem framing session for a new software idea, simply describe your problem or idea. The guided explore partner will then help surface directions, questions, and exploration paths to clarify your requirements and inform decisions.

You should not use visual reasoning and ASCII diagrams for requirement clarification when you are ready to implement features or write code. This method is strictly for pre-implementation exploration, problem framing, and design discussions.