openspec-explore

To clarify requirements before writing code, use a structured thinking partner to frame problems, prompt open-ended dialogue, and surface alternative paths. This approach investigates the problem space and documents potential paths without writing implementation code.

To visually map out a codebase problem space, apply exploration modes that generate ASCII diagrams. This method contextualizes the problem space, surfaces unknowns, and visualizes concepts to guide your decision-making process.

Yes, you can use design-thinking to investigate codebase risks without implementing changes. A thinking partner analyzes and documents potential paths while explicitly avoiding implementation or code-writing, ensuring safety by surfacing risks and unknowns first.

To frame a problem from a vague idea, enter an exploration mode that prompts structured thinking and open-ended dialogue. This surfaces questions, risks, and potential next steps to guide your decision-making before any changes are made.

No, this requirements exploration approach does not write or modify code. It ensures safety by explicitly avoiding implementation, focusing solely on analyzing the problem space, framing problems, and documenting potential paths for you to act on later.