openspec-explore

To clarify requirements before implementation, you need a structured thinking partner to investigate problems and brainstorm solutions. This skill facilitates non-implementation exploration using adaptive questioning and visual aids to map the problem space.

The best way to investigate a codebase for new features is mapping architecture and surfacing complexity. This skill acts as a thinking partner to find integration points and analyze implications without writing implementation code.

To visualize tradeoffs during design brainstorming, you map out approaches and sketch comparisons. This skill supports option evaluation by brainstorming approaches and generating visual comparisons to clarify decision-making.

Yes, the requirements clarification process integrates with the OpenSpec system. It references existing changes and captures exploration insights directly into proposals or designs when appropriate.

Yes, you can use this exploration tool with a high-level idea. It engages in curious, adaptive deep thinking to help you investigate topics, clarify requirements, and build structure around initial concepts.

You should avoid using a thinking partner for codebase analysis when you need actual code implementation or automated refactoring, as this skill focuses strictly on non-implementation exploration, problem investigation, and requirements clarification.