openspec-explore

Requirements exploration clarifies user needs by using a thinking partner to guide ideation, surface questions, and visualize dependencies before implementation. You describe your objective, and the partner iteratively surfaces tradeoffs and diagrams.

Evaluating a codebase during design discussions involves collaborative exploration where a thinking partner surfaces risks, unknowns, and architectural tradeoffs. This approach applies multi-direction thinking to clarify design options without writing implementation code.

Yes, a thinking partner facilitates deep exploratory thinking to investigate architecture problems while explicitly avoiding code implementation. It provides stance-based guidance and visualization to surface proposals and risk artifacts across discussions.

To surface unknowns and dependencies in feature design, apply guided questioning and visualization tooling during exploratory discussions. This multi-direction thinking approach clarifies tradeoffs and reveals hidden architectural risks before development.

Collaborative exploration works across discussions, designs, and architectures by acting as a patient thinking partner to clarify requirements iteratively. It meets activation rules to provide stance-based guidance for ongoing problem analysis.

You should not use a thinking partner for codebase exploration when you need actual code implementation or concrete programming solutions. This approach explicitly avoids writing code, focusing solely on ideation, risk surfacing, and requirement clarification.