openspec-explore

To clarify requirements and explore ideas without writing code, use a thinking partner that maps architecture, surfaces risks, and captures insights through disciplined questioning and ASCII diagrams. This mode focuses on problem framing and design ideation across software and product domains.

The best way to map codebase architecture and identify integration points is by exploring the codebase with a thinking partner that reads files, examines patterns, and generates ASCII diagrams to surface questions and open design directions.

Yes, you can generate ASCII diagrams for software design and thought experiments. The exploration process sketches multiple directions, surfaces unknowns, and visually maps architecture to help teams frame problems and capture insights.

Yes, this requirements discovery approach supports data and product domains. It applies during early-stage problem framing across software, data, and product contexts, asking clarifying questions and challenging assumptions to surface design directions.

You should not use a thinking partner for problem framing when you need to implement code rather than explore ideas. This approach is strictly for requirements discovery, design ideation, and surfacing risks without writing any implementation code.