openspec-explore

To explore ideas and clarify requirements, you can use a thinking partner that reads context, asks guiding questions, and visualizes relationships without writing code. This helps formulate problems and surface assumptions early.

The best way to brainstorm design alternatives is using a structured exploration partner that applies non-implementation mode. It outlines stances, asks guiding questions, and generates ASCII diagrams to visualize options for decision making.

Yes, you can visualize relationships and assumptions without writing code. The exploration partner operates in a non-implementation mode, focusing on asking questions and generating ASCII diagrams to support thinking rather than coding.

To start brainstorming and think aloud about requirements, state your problem and switch the partner to explore mode. It will read your context, surface hidden assumptions, and guide you through the problem formulation.

Yes, this thinking partner works for early-stage problem formulation and design discussions. It specifically applies to phases where exploring alternatives and gathering requirements is valuable, avoiding immediate implementation changes.

You should avoid using an exploration partner when you need actual code implementation or direct changes to your project. It is designed for non-implementation exploration, focusing on questions and visual diagrams rather than writing code.