openspec-explore

Codebase exploration involves reading context and mapping dependencies to surface questions and risks early. It visualizes architecture using ASCII diagrams and narrative explanations, allowing you to understand impacts before writing any code.

Yes, you can visualize architecture and dependencies without writing implementation code by generating ASCII diagrams and narrative explanations. This method enforces safe exploration by refusing implementation tasks while mapping structural relationships.

The best way to explore ideas for codebase modifications is to think aloud, map options, and surface questions. By reading existing context and diagramming relationships, you identify potential risks and unknowns to guide your planning.

No, this exploration approach does not write code or modify files during analysis. It enforces safe exploration by refusing implementation tasks, focusing solely on reading context, diagramming relationships, and surfacing risks.

You need to use exploration artifacts for codebase risk management when planning changes requires understanding unknowns and dependencies. These artifacts surface risks and map architecture visually, informing planning before any implementation begins.