openspec-explore

To explore ideas and clarify requirements, you describe your core problem, constraints, and scenarios to a thinking partner that surfaces questions, options, and ASCII diagrams for structured discovery without writing code.

A thinking partner for framing problems is a non-implementation exploration tool that helps teams brainstorm options, surface unknowns, and map tradeoffs using structured prompts and ASCII diagrams before committing to work.

You visualize ideas and exploration paths by providing your problem context and constraints, which triggers the system to generate ASCII diagrams and structured prompts that map tradeoffs and surface relevant questions.

Yes, you can use exploration mode to support change proposals by surfacing risks, unknowns, and tradeoffs through structured discovery questions, helping clarify requirements before any implementation begins.

No, this requirements discovery process requires no specific dependencies or components; you simply provide your problem description, context, and constraints to start the structured exploration.

You should not use a non-implementation thinking partner when your project requires actual code execution or deployment, as this tool focuses purely on structured idea exploration, requirement clarification, and visual mapping without implementation.