openspec-explore

To clarify requirements and investigate architecture before changing code, use an exploration-first approach that questions assumptions and maps the existing codebase. This guides deep thinking to reduce uncertainty without enabling implementation.

Analyzing trade-offs between solution directions involves brainstorming available options and surfacing their comparative strengths. This decision support process helps recommend directions while preventing premature commitment to code changes.

Troubleshooting an existing codebase without implementing features requires reading files, searching code, and mapping architecture. This grounds your investigation in reality and enforces constraints to prevent coding during the analysis.

Yes, you can use pre-change analysis to question assumptions and reshape unclear problems. It acts as a thinking partner during the investigation phase, ensuring you capture your reasoning and decisions before any implementation begins.

You should not use exploration-first guidance when you are ready to write code or execute feature work. It enforces strict constraints to prevent implementation, serving solely as a tool for thinking through changes and reducing uncertainty.