openspec-explore

To clarify product requirements before coding, you need a thinking partner that enforces non-implementation exploration, surfaces hidden questions, and frames the problem accurately without generating source code.

The best way to frame a problem during early-stage product discovery is to explore multiple directions safely, visualize ideas with ASCII diagrams, and capture design artifacts to solidify abstract concepts before committing to a build.

Yes, you can use ASCII diagrams to visualize design discussions, allowing you to map out early-stage thinking, explore multiple directions, and structure your ideas visually without writing implementation code.

To capture requirements exploration as OpenSpec artifacts, you formalize your design discussions into proposals, designs, and specs once your initial non-implementation thinking and problem framing are complete.

Yes, this thinking partner approach works for early-stage design discussions by strictly enforcing non-implementation thinking, allowing you to safely explore ideas and clarify requirements without writing source code.

You should not use a guided exploration workflow for requirements clarification if your goal is to immediately generate, write, or implement code, as this process strictly enforces non-implementation thinking during early-stage discovery.