openspec-explore

To clarify project requirements and frame open-ended problems, you can use an exploration partner that asks probing questions, references your current codebase, and suggests visualizations to map decisions.

Yes, you can visualize codebase analysis and design decisions using ASCII diagrams, which help align team thinking by providing clear mental models during early problem framing and exploration.

The best way to brainstorm and explore options is to ground the conversation in your current project context, allowing a thinking partner to read along and surface relevant questions that dynamic exploration requires.

No, this thinking partner approach does not execute code or generate implementation files, as it operates under strict guardrails designed specifically to facilitate open-ended thinking and requirement clarification.

You need an exploration partner for requirement clarification when you are starting early problem framing, having design conversations, or analyzing a codebase to surface hidden questions and map decisions.

No specific technical prerequisites are required to use this open-ended thinking partner during codebase analysis, other than describing your goal and providing the current project context you want to explore.