openspec-explore

To brainstorm architecture and clarify requirements without writing code, use an exploratory thinking partner that reads repository files and OpenSpec artifacts to surface tradeoffs and hidden assumptions before implementation begins.

Yes, you can review OpenSpec change artifacts and investigate your codebase through read-only access that enforces a strict prohibition on writing code, ensuring safe exploration of existing proposals without unintended modifications.

Exploring real-time collaboration design options is best handled by mapping tradeoffs and surfacing assumptions in an open-ended discussion, then deciding whether to open a formal change rather than committing prematurely to code.

No, this requirements discovery tool does not automatically write insights; it recommends where to record decisions in OpenSpec artifacts like proposals, designs, and tasks, leaving the actual creation of changes to you.

You should not use an exploratory thinking partner for codebase investigation when you need to perform implementations or make code changes, as it operates strictly in read-only mode and cannot write or modify files.

Awareness of the OpenSpec CLI context is required to properly compare architectural options and review change artifacts, as the exploration relies on understanding existing OpenSpec proposals and repository file structures.