openspec-explore

Codebase investigation for architecture discovery involves reading repository files, mapping integration points, and surfacing hidden complexity while strictly enforcing a no-implementation constraint to prevent code changes. You generate diagrams and spec drafts to capture findings without writing code.

Exploratory reasoning for software design is an interactive process to validate ideas, challenge assumptions, and surface tradeoffs during early-stage development. Use it for idea validation, architecture discovery, and design tradeoff analysis before committing to implementation.

Drafting design specs and proposals while preventing implementation requires a guided exploratory mode that captures decision notes and artifacts on request. This enforces a strict non-implementation stance, ensuring design exploration remains separate from code changes.

Yes, you can investigate repository files and map integration points without writing code by using a non-implementation exploratory mode. This allows you to read the codebase, identify architectural relationships, and surface hidden complexity relevant to the design discussion.

OpenSpec exploration operates with no external dependencies or components. It functions as a standalone exploratory reasoning partner that integrates with OpenSpec commands when available, but requires no specific environment setup to begin investigating designs.