openspec-explore

To clarify requirements and frame problems, you can use a guided exploration partner to surface questions, risks, and design implications. This approach investigates your codebase and decision space to support ideation without generating code or automated changes.

Exploring a codebase during ideation involves reading code, searching context, and visualizing dependencies with ASCII diagrams. This process creates a non-implementation thinking space to surface risks and design notes until a change proposal is warranted.

To start a guided exploration session, describe the challenge you are facing. The exploration will then begin surfacing open-ended questions, potential risks, and available options to support your decision-making workflow.

No, you cannot use this approach to generate code or apply automated changes. It serves strictly as a non-implementation thinking space that produces surface-only artifacts like questions, risks, and design notes for decision-making.

Yes, this thinking partner workflow supports open-ended ideation, requirements clarification, and problem framing sessions across projects. It applies to diverse decision spaces by surfacing relevant questions and design implications.