openspec-explore

Requirement clarification and architecture exploration involve questioning assumptions and mapping integration points to surface multiple directions. This iterative discovery process prevents premature implementation by enforcing safety constraints that disallow code writing.

The best way to analyze tradeoffs for ambiguous change requests is by generating tradeoff tables and ASCII diagrams to visualize complexity. This investigation surfaces risks and unknowns to ensure safe, well-informed architectural decisions.

Investigating debugging options without modifying the codebase requires strict guardrails that disallow code writing and feature implementation. You can map existing patterns and find integration points safely by maintaining an explicit non-implementation stance.

Yes, you can visualize architecture mapping and integration points without writing feature code by using an explicit non-implementation stance. This approach promotes ASCII diagrams and option comparison to make complexity legible while enforcing safety constraints.

You should not use exploration mode for requirement analysis when you are ready to write code or implement features. If implementation is requested, you must exit explore mode first, as strict guardrails disallow code writing and unauthorized changes.