openspec-explore

To clarify project requirements before writing code, you can use an exploration mode that facilitates structured thinking and scenario exploration without implementing changes. It acts as a thinking partner to illuminate options during problem framing.

Exploring a codebase for ideation without making changes involves using a non-implementation stance that reads relevant files and reasons through the problem. This approach prevents code-writing or feature changes while you visualize potential approaches to the problem.

Yes, you can generate OpenSpec artifacts during the requirement exploration phase. While the exploration mode avoids writing code or implementing changes, it can propose OpenSpec artifacts explicitly upon your request.

Requirement exploration mode works for framing complex problems across projects by facilitating structured thinking and scenario exploration. It applies to ideation, problem framing, and requirement clarification across codebases without executing code.

You should avoid code implementation during problem framing to remain in a thinking mode that helps clarify requirements without committing to actions. This non-implementation stance ensures you surface potential directions before making feature changes.