openspec-explore

To clarify requirements and explore architecture options before writing code, use a conversational thinking partner that challenges assumptions and surfaces tradeoffs during early-stage design. It helps crystallize proposals, specs, and risks without implementing any automated changes.

You can investigate your codebase to map integration points and surface hidden complexity by reading repository artifacts and change documents. This analysis maps architecture and finds connections while enforcing guardrails against performing automated modifications.

The best way to run a discovery session for early-stage design is through exploratory dialogue that asks clarifying questions and surfaces alternative directions. This non-implementation workflow ensures options and risks are fully mapped before committing to formal changes.

This conversational analysis workflow supports reading OpenSpec change documents and repository artifacts to inform architecture reviews. It enforces guardrails to ensure the session remains a non-implementation analysis, preventing any code writing or automated changes.

You should not use an exploratory dialogue tool when you need to execute code, perform automated changes, or directly implement features. It is strictly a non-implementation analysis workflow designed for surfacing options, tradeoffs, and risks rather than writing code.

To capture insights and next steps from a codebase investigation, use a tool that helps crystallize proposals, designs, and risks into capture-ready formats. These findings can be optionally recorded as OpenSpec artifacts for future reference.