openspec-explore

To clarify ambiguous requirements before implementing codebase changes, use structured problem framing to recast vague ideas into specific decision points, investigate existing files, and map relevant architecture to uncover dependencies and constraints.

The best way to compare architecture options and surface tradeoffs is by performing structured analysis that evaluates different approaches, highlights inherent risks, and uses visual diagrams to explain the impact of each design direction.

You map existing architecture during codebase investigation by reading grounded files and searching the repository to understand the current system structure, enabling you to identify constraints and dependencies before modifying code.

No, you cannot implement features directly while exploring requirements, as this process strictly avoids feature implementation to focus entirely on capturing insights as OpenSpec artifacts and understanding the situation before committing to changes.

You need to use structured exploration for software engineering problems when you want to add a feature but are unsure about the scope, requiring you to uncover constraints, investigate dependencies, and clarify better design directions first.

Yes, openspec-explore supports capturing investigation insights by saving the clarified requirements, architecture mappings, and tradeoff comparisons as structured OpenSpec artifacts when explicitly requested by the user.