openspec-explore

To clarify vague product requirements, you need a thinking partner to explore ideas, map user flows, and identify technical challenges. This approach focuses on clarifying thought processes through open-ended conversation rather than pushing for immediate implementation.

Investigating an unfamiliar codebase requires mapping its architecture, finding integration points, and surfacing complexity. This exploration process helps you understand the existing structure and technical challenges before committing to a new development path.

Comparing technical approaches involves brainstorming options, building comparison tables, and sketching tradeoffs. You can visualize concepts through ASCII diagrams to ground your design thinking and make informed problem-solving decisions.

Yes, you can explore product ideas in a non-prescriptive and adaptive manner. This method acts as a deep thinking partner to help you investigate problems and clarify requirements without the pressure of immediate implementation.

To identify technical challenges for features like real-time collaboration, use a deep exploration process to think through implications. This grounded investigation surfaces architectural complexities and integration points before development starts.

You should avoid exploratory problem-solving when you need immediate implementation or prescriptive solutions. This method is designed for open-ended requirements clarification and deep thinking, not for generating final production code directly.