openspec-explore

To compare design approaches visually, you can use tradeoff tables and ASCII diagrams to map out integration points and make uncertainty visible, ensuring your decision support process accounts for varying architectural constraints.

You can investigate codebase architecture during requirement uncertainty by using a non-implementation thinking session that guides you to inspect relevant integration points and ground your design decisions in the existing reality of your codebase.

Yes, you can use exploration sessions to capture decisions as artifacts without modifying code, because the process enforces a guardrailed non-implementation stance that allows only thinking and optional artifact capture when decisions are made.

The best way to compare design approaches safely is to use tradeoff tables and ASCII diagrams within a guardraided thinking session, allowing you to visualize tradeoffs and reframe the problem space without risking unwanted code changes.

You should not use exploratory problem framing when your requirements are already fully clear and you are ready to implement, as the process explicitly prevents implementation and code changes, focusing solely on thinking and investigation.