openspec-explore

To clarify requirements and explore ideas, you can use a thinking partner that asks clarifying questions, challenges assumptions, and visualizes thoughts using ASCII diagrams to map the problem space before implementation.

The best way to investigate a codebase involves systematically mapping architecture and identifying patterns to find integration points, while also checking existing changes and capturing decisions within your project constraints.

To compare options for a new feature, you can brainstorm approaches, build comparison tables, and identify potential risk surfaces to recommend the most viable path forward for your implementation.

Yes, you need the openspec CLI installed as a prerequisite dependency, because the requirement exploration and visual thinking tools operate entirely within the constraints of the OpenSpec system boundaries.

Yes, you can use OpenSpec awareness to check for existing changes, read project artifacts, and capture decisions, ensuring your codebase investigation aligns with the current system context.

You should avoid using requirement exploration when you already have fully clarified specifications and mapped risk surfaces, as the deep thinking and problem space reframing tools target ambiguous problem domains.