openspec-explore

You can explore architecture tradeoffs without implementation by using investigative reasoning to surface assumptions, compare options, and visualize solutions. This approach inspects repository context to guide requirement clarification and solution-space discovery safely.

Requirement clarification before implementation involves reading and mapping relevant codebase parts to find real integration points. This thinking-first exploration reframes questions as understanding emerges, reducing wasted effort and rework.

Yes, you can use OpenSpec artifacts like proposals, designs, and tasks to maintain consistency during mid-implementation uncertainty. Reading these change-aware artifacts grounds your exploration in current repository work and existing patterns.

Generating comparison tables and tradeoff visualizations for architectural decisions involves mapping solution-space alternatives and their constraints. This supports assistant-driven discovery workflows by making complex discussions tractable through ASCII diagrams and structured comparisons.

Requirement exploration works for evaluating alternatives in an existing codebase by inspecting the repository context to identify real integration points. It enforces strict non-implementation constraints while supporting safe, comparative reasoning over grounded codebase investigation.