openspec-explore

To clarify requirements and explore ideas before implementing code, use a thinking partner that asks clarifying questions and challenges assumptions. This approach helps surface hidden complexity and map the problem space before development begins.

The best way to investigate a codebase for complex problems is to map existing architecture, identify integration points, and surface hidden dependencies. This adaptive exploration clarifies the problem space and highlights architectural constraints before making changes.

To compare different architectural options for a new software feature, facilitate a brainstorming session to sketch tradeoffs and visualize potential approaches. This helps you evaluate different facets like coordination and synchronization before committing to an implementation.

Yes, you can use design thinking to break down vague software ideas into actionable requirements by engaging in an adaptive exploration process. This involves asking targeted questions and visualizing concepts to transform abstract ideas into clear, documented decisions.

No specific dependencies or environments are required for this requirements clarification process. It operates through natural language interaction and integrates with the OpenSpec system to capture insights, requiring only your problem description to begin.