openspec-explore

To clarify requirements and explore problems, you need a thinking partner that engages in interactive dialogue. This approach surfaces potential risks and unknowns by mapping existing codebases and visualizing trade-offs between potential solutions.

Investigating an existing codebase before an architectural change requires analyzing and mapping relevant code components. This helps ground your discussions, compare architectural patterns, and explore implications through clarifying questions and visualizations.

Comparing potential solutions during design thinking involves brainstorming and visualizing trade-offs between different approaches. By identifying risks and exploring implications through adaptive exploration, you can evaluate options before committing to implementation.

Yes, interactive dialogue can effectively map codebase analysis to identify risks. By engaging in curious, open-ended conversations, you can surface unknowns, clarify requirements, and ground your investigation in the current state of the codebase.

You should avoid deep exploration for problem solving when implementation details are already fully defined and no architectural ambiguity exists. It is designed for pre-implementation thinking and requirement clarification, not for straightforward coding tasks.

Openspec-explore supports requirements gathering by acting as a deep thinking partner to explore problems like adding real-time collaboration. It facilitates this through interactive dialogue, codebase investigation, and option comparison before implementation begins.