openspec-explore

Guided exploration clarifies requirements by posing questions, surfacing assumptions, and mapping the problem space. This thinking partner helps you investigate problems and frame tradeoffs across product, design, and engineering before implementation begins.

Analyzing tradeoffs and scoping requirements involves surfacing risks and building mental models. This exploration partner guides open-ended thinking, producing ASCII diagrams to clarify options and map the problem space without writing code.

Yes, OpenSpec artifacts can be proposed to capture your thinking during early-stage discussions. This exploration partner explicitly avoids writing code, focusing instead on framing problems, clarifying requirements, and documenting your decision process.

Mapping the problem space requires posing clarifying questions and surfacing hidden assumptions. This guided exploration partner facilitates open-ended thinking, visualizing options with ASCII diagrams to ensure teams align on requirements and tradeoffs.

No, this thinking partner explicitly avoids writing code and requires no code execution. It enforces a non-implementation stance to focus purely on exploring ideas, clarifying requirements, and proposing OpenSpec artifacts to capture thinking.

You should avoid guided exploration when you need immediate code implementation or script execution. This approach enforces a non-implementation stance with explicit exit prompts and guardrails, focusing solely on early-stage thinking and requirement clarification.