openspec-explore

To clarify codebase requirements, you can use a thinking partner to read files, search code, and surface questions. This exploration process maps dependencies and risks visually without writing any new code.

Yes, you can visualize code dependencies and risks with ASCII diagrams. This thinking partner maps relationships and decisions directly from codebase exploration to help you understand structural impacts.

You explore a codebase without writing code by entering an exploration mode that enforces a strict no-code stance. It reads context, investigates files, and surfaces clarifications rather than applying changes.

Yes, the thinking partner can generate OpenSpec proposals, designs, and specs on request. It creates these artifacts while staying in a no-code exploration mode to document your requirements.

The best way to analyze risks before modifying a codebase is to use a thinking partner that investigates your files and surfaces potential issues. It maps dependencies and decisions visually to highlight risks.

You should not use a thinking partner for codebase exploration when you need to directly implement, compile, or deploy code changes. It enforces a no-code stance and focuses solely on clarifying requirements and design.