openspec-explore

To clarify complex codebase requirements, you can use guided exploration to read files, search code, and investigate the repository. This approach maps options and surfaces questions through open-ended reasoning without writing code.

Visualizing design decisions is achieved by creating ASCII diagrams to clarify flows and surface risks. This maps the problem space visually, allowing you to explore ideas and verify requirements structurally before committing.

Navigating your codebase without modifying files is supported through non-implementation guardrails. You can safely read files and search code to investigate problems while the system prevents unintended code changes.

To verify requirements and surface risks during design exploration, you engage in open-ended reasoning. This guided thinking process helps map available options, highlight potential issues, and propose artifacts if needed.

You should use a thinking partner for open exploration when you want to think through something before or during a change. It supports problem-space investigation and design decisions while strictly avoiding actual implementation.