openspec-explore

Clarifying ambiguous product requirements involves investigating repository artifacts to map integration points and hidden complexity. By asking clarifying questions and challenging assumptions, teams surface risks and reframe problems before committing to implementation.

The best way to map architecture and surface risks is by reading repository artifacts to identify integration points and hidden complexity. This investigation allows teams to explore multiple directions and reframe problems without forcing a single solution.

To draft OpenSpec proposals and designs from exploratory discussions, generate capture-ready suggestions for proposals and tasks while maintaining a strict non-implementation stance. This ensures designs are documented without writing actual code during the exploration phase.

This requirements exploration approach does not write or modify code, enforcing a strict non-implementation stance. It focuses entirely on analyzing options, mapping architecture, and drafting design proposals to clarify requirements before any development begins.

You need exploratory thinking for product discovery when facing ambiguous goals or constraints. It applies when teams must investigate options, analyze documentation, or reframe requirements before making final design and implementation decisions.