openspec-explore

To clarify requirements, you need a structured brainstorming session that surfaces questions, maps assumptions, and identifies unknowns. This approach outlines multiple directions to explore, ensuring you understand the problem space thoroughly before making product or code changes.

Exploring a problem space involves open-ended inquiry to investigate the core issues and surface hidden risks. This process highlights multiple options and visualizes ideas, helping you map out unknowns and evaluate different directions before committing to a solution.

Yes, visual thinking with ASCII diagrams and lightweight sketches supports brainstorming product decisions. It provides a non-prescriptive way to map out ideas and investigate problems visually, helping you see relationships and structures before implementation.

You can brainstorm options through a guided thinking partner that investigates the problem and surfaces risks without implementing code. This non-prescriptive exploration clarifies requirements and maps out multiple directions, keeping the focus on design thinking rather than immediate execution.

Yes, this exploration approach applies to brainstorming and requirements clarification across both product and code design decisions. It supports open-ended inquiry and visual thinking to ensure all aspects of the problem space are investigated before changes are made.

The limitation is that this exploration mode is strictly non-prescriptive and does not implement code. It focuses on surfacing questions, assumptions, and risks to clarify requirements, meaning you will need a separate execution step to build the actual solution.