openspec-explore

To clarify requirements for a vague feature idea, you need a deep thinking partner that asks open-ended questions and challenges assumptions. This skill facilitates that exploration by investigating the problem space and brainstorming potential solutions before you commit to an implementation path.

You can analyze your codebase to map architecture and find integration points by using an exploration skill. It reads the code to identify structural patterns and integration locations, surfacing insights into design artifacts without directly modifying the codebase.

The best way to compare solution options and sketch tradeoffs is through structured option comparison. This skill helps you brainstorm approaches, build comparison tables, and identify potential risks or unknowns across different architectural paths within the OpenSpec framework.

To identify potential risks and unknowns when planning a platform change, engage in deep problem exploration. This skill acts as a thinking partner to surface hidden risks, investigate implications, and capture the resulting analysis into formal design artifacts.

This requirements exploration tool does not generate code or modify the codebase directly. It operates strictly as an investigative thinking partner to analyze architecture and capture insights, ensuring you understand the problem space before any implementation begins.

You need to use design thinking for problem solving when you have a vague idea and must understand the implications before committing to a specific path. This skill facilitates that ideation by clarifying requirements and capturing insights into proposals.