openspec-explore

To explore a codebase before implementation, you can use a guided thinking partner that reads files, searches code, and articulates uncertainties to align understanding. This approach surfaces constraints and trade-offs without writing any code.

Visualizing requirements during planning involves generating ASCII diagrams and open threads to surface risks and unknowns. This technique helps map alternatives and structure change proposals before committing to an implementation.

Yes, you can analyze requirements and produce design artifacts without modifying source code. This non-implementation workflow focuses on generating reasoning, questions, and proposal artifacts to support planning and alignment.

Surfacing unknowns and trade-offs in complex requirements requires applying exploration techniques across scenarios. This process produces reasoning and questions that clarify constraints and align team understanding before development begins.

Yes, this exploration approach supports building change proposals for an existing codebase. It acts as a collaboration tool to structure design artifacts and visualize ideas while investigating the codebase without implementing changes.

Use a thinking partner instead of directly writing code when scenarios require clarity and trade-off analysis before implementation. It helps you articulate uncertainties, map options, and align understanding prior to making any changes.