openspec-explore

To clarify ambiguous software requirements before implementation, you can use an exploration-first approach that maps architecture and surfaces tradeoffs. This method enforces an exploration-only stance, permitting codebase analysis while strictly prohibiting feature implementation.

The best way to investigate a codebase for hidden complexity is through active problem-space exploration. This process allows you to map architecture and find integration points to ground your thinking, ensuring you thoroughly understand the system before any changes begin.

Yes, you can compare multiple solution options and visualize tradeoffs during requirement exploration. This approach supports brainstorming multiple approaches and expressing them with diagrams and comparison tables to help you evaluate decisions.

Requirement exploration does not force you to create OpenSpec artifacts. The process requires optional OpenSpec artifact creation only when explicitly requested, keeping the focus strictly on reading and analysis rather than documentation overhead.

You should use an exploration-only stance for software changes during early ideation, active investigation, and mid-change ambiguity resolution. It is essential when tradeoffs and unknowns must be surfaced before committing to any feature implementation.

Requirement exploration prohibits writing code and implementing features to prevent accidentally jumping into implementation before design is clear. This constraint ensures you safely think through ambiguous requirements, investigate the codebase, and clarify tradeoffs without distraction.