openspec-explore

Clarifying requirements involves using a thinking partner to ask open-ended questions and map dependencies through visual diagrams. This process validates ideas and frames problems during early discovery before any implementation begins.

The best way to explore ideas is by mapping problem scopes with visual aids like ASCII diagrams while a thinking partner surfaces multiple directions. This open-ended prompting guides brainstorming and validates requirements across any domain.

Yes, requirement validation applies across non-technical domains. The exploration process provides open-ended questions and visual mappings to investigate problems and frame designs universally, avoiding specific implementation tasks regardless of the domain.

Mapping dependencies when investigating a problem involves using visual aids like ASCII diagrams during early discovery. This clarifies relationships and potential solutions while a thinking partner guides the framing with open-ended prompts.

Avoid using an exploratory thinking partner when you need actual implementation or code generation. The process enforces guardrails to remain strictly in the discovery and design framing phase, avoiding implementation tasks entirely.