openspec-explore

To explore a codebase and clarify requirements, use a thinking partner that asks clarifying questions, surfaces assumptions, and maps dependencies visually using ASCII diagrams. This approach reduces ambiguity and accelerates understanding before any code changes are made.

Problem space exploration is the process of reasoning through a problem by gathering context and asking clarifying questions. Visual reasoning enhances this by creating ASCII diagrams to map ideas and dependencies, making complex relationships easier to understand and scope.

You can visualize codebase dependencies and ideas by entering an explore mode that acts as a thinking partner. It generates ASCII diagrams to map out structural relationships and guides you through questions to ensure your mental model matches the actual architecture.

Yes, you can use this thinking partner to investigate a bug without writing code. It maintains a non-implementation stance, providing thinking artifacts and guiding questions to help you reason through the issue and clarify the root cause before deployment.

No, this guided thinking tool does not deploy code changes or modify your codebase. It strictly provides non-implementation guidance, focusing on reasoning, clarifying questions, and visual artifacts to help you understand the problem space.