openspec-explore

Problem framing is the process of defining the exact issue before solving it. This thinking partner helps with problem framing by asking clarifying questions and mapping exploration paths during early-stage ideation without enforcing firm implementation.

Yes, you can use visual thinking to map requirements during discovery. The skill encourages open-ended reasoning and uses ASCII diagrams to visualize concepts, helping individuals or teams surface risks and directions before design decisions.

No, this design-thinking partner does not generate code. It intentionally avoids code generation to focus entirely on open-ended reasoning, requirement discovery, and problem framing during exploratory discussions.

The best way to clarify requirements before design decisions is through stance-based exploration. This method uses a curiosity-driven thinking partner to surface risks, questions, and directions without enforcing a firm implementation.

You need an exploration-driven workflow for ideation when starting a new feature or project. It supports early-stage requirement discovery by encouraging open-ended reasoning and posing clarifying questions to investigate problems.