openspec-explore

You can safely explore codebase architecture using a read-only analysis mode that visualizes data flows and dependencies without writing code. This method enforces a strict read-only stance, ensuring files remain unaltered while surfacing architectural design decisions.

The best way to visualize dependencies for risk analysis is through guided exploration that surfaces tradeoffs and unknowns. By mapping data flows visually, you can identify architectural risks and align on design decisions without implementing any code changes.

Yes, you can use guided exploration to brainstorm design decisions and document tradeoffs. It surfaces questions and unknowns during codebase analysis, capturing decisions and risks to align team direction without altering code.

To start analyzing a codebase to surface unknowns, enter an explore mode and discuss diagrams and architecture with the assistant. This guides deep reasoning about data flows, surfacing tradeoffs and risks across contexts without implementation.

Yes, this exploration approach supports documentation alignment by capturing decisions, risks, and next steps for later use. It helps teams reason about requirements and codebases, ensuring discovery outputs are recorded without writing code.