openspec-explore

Codebase investigation involves mapping architecture, finding integration points, and surfacing complexity to clarify requirements. A thinking partner skill facilitates this through adaptive conversations and ASCII diagrams, helping you understand impacts without writing implementation code.

Mapping authentication flows requires tracing integration points and sketching tradeoffs visually. You can brainstorm approaches and visualize different implementation options using ASCII diagrams during an adaptive conversation to identify potential conflicts in the system.

Comparing design options involves brainstorming approaches and visualizing tradeoffs within your codebase. An exploration skill supports this by grounding discussions in actual code and sketching options using ASCII diagrams to clarify potential impacts before implementation.

Yes, exploring ideas and clarifying requirements can optionally capture insights into OpenSpec artifacts. The exploration process focuses on adaptive conversation and problem solving, ensuring design thinking insights are recorded without proceeding to actual code implementation.

You should avoid using exploration tools when you need actual code implementation rather than design thinking. This approach is strictly for investigating problems, mapping architecture, and clarifying requirements, meaning it helps you think through impacts without writing the final code.