openspec-explore

To map project risks during exploration, you read existing codebases and documentation to surface questions and constraints. This process helps articulate potential issues and outline alternative approaches before any changes are made.

Yes, you can generate OpenSpec artifacts like proposals, designs, and task lists without writing or applying code. The process focuses on documenting insights and planning changes while strictly avoiding any execution or implementation tasks.

To transition from exploring ideas to implementing changes, you must first exit explore mode by initiating a new change request. Once the exploration phase is complete, you can proceed with the actual coding and execution tasks.

A key limitation is that a thinking partner will never write, execute, or apply code. It is restricted to reading files, discussing ideas, and generating planning artifacts, meaning you must switch contexts to perform actual implementation.