openspec-explore

Codebase investigation involves reading repository artifacts to map architecture, identify integration points, and surface hidden risks. This exploratory approach clarifies requirements and reduces premature design decisions before committing to implementation.

Drafting an OpenSpec proposal is done by capturing emerging design decisions into structured artifacts like proposals and task lists. The process explicitly refuses to execute code changes, ensuring space for discovery and clarifying requirements first.

Yes, an interactive thinking partner acts as a curious collaborator during design discussions. It asks clarifying questions, challenges assumptions, and surfaces alternatives to help you decide between database options or audit complex flows.

Exploration mode works by reading existing repository artifacts and change proposals. It maps relevant architecture, identifies hidden complexity, and helps think through ideas without immediately committing to any code implementation.

You should not use exploratory conversation when you need to immediately implement code or execute changes. This mode is strictly for discovery, clarifying requirements, and drafting design artifacts, explicitly refusing to write or run implementation code.