openspec-explore

To explore architecture and requirements without writing code, use a thinking partner skill that reads files, searches code, and investigates problems to surface questions and visualize options. It guides open-ended thinking and clarifies design decisions while staying out of implementation.

The best way to visualize design options for complex software problems is by using an exploration thinking partner that surfaces multiple approaches and clarifies questions. It reads relevant files and diagrams to understand context, helping you map out decisions without modifying code.

Yes, you can use it to gather requirements and clarify design decisions for a new feature. It acts as a guided thinking partner that investigates problems, surfaces risks, and proposes design surfaces or spike tasks for future changes without implementing anything.

No, this exploration tool does not modify your codebase while analyzing files. It reads relevant files and diagrams to build context and understand the architecture, ensuring your code remains untouched while you investigate problems and surface design artifacts.

To start a design discussion and surface risks, initiate explore mode and ask the AI to think deeply about your project. It will read relevant files, ask clarifying questions, surface multiple approaches, and visualize options before any implementation begins.

You should not use a thinking partner for codebase exploration when you need to actually implement changes or write code. This skill is strictly for problem clarification, requirements gathering, and visualizing design options, not for executing code modifications.