openspec-explore

To explore architectural options before implementation, you can use an exploratory thinking partner to compare approaches, visualize concepts, and sketch tradeoffs without writing any code. This helps clarify requirements and surface complexity early.

Mapping integration points in an existing codebase is best handled by investigating the architecture as an exploratory exercise. This approach surfaces underlying complexity and identifies integration points through open-ended conversation and visualization.

Yes, you can use it to brainstorm and compare design tradeoffs for new features. It helps build comparison tables and sketch out architectural implications, ensuring you understand the impact of potential solutions before making a decision.

You clarify project requirements through open-ended exploration by engaging with a thinking partner that facilitates deep thinking and visualization. This adaptive stance encourages curiosity to help uncover hidden problems and define exact specifications.

No, this approach does not modify your codebase during the design exploration phase. It operates strictly as a thinking partner to facilitate investigation and clarify requirements before or during code changes, without implementing them.