openspec-explore

To explore software architecture, you can use an exploratory design mode that reads repository files, maps integration points, and surfaces hidden complexity without producing implementation code. It helps ground conversations in the actual codebase before committing to design decisions.

Comparing design tradeoffs is best handled by generating ASCII diagrams and decision summaries that surface risks and open questions. This approach reframes ambiguous problems and evaluates multiple directions while avoiding premature implementation.

Investigating a messy codebase subsystem involves mapping architecture, finding integration points, and surfacing hidden complexity relevant to a proposed change. You can troubleshoot subsystems like auth by reading repository files for context while avoiding direct code changes.

Yes, you can capture exploratory design proposals as OpenSpec artifacts on request while avoiding implementation code. This feature allows you to record designs, proposals, and task lists directly from the investigation mode.

Yes, this exploratory design mode works for early-stage feature discovery by asking questions, reframing problems, and clarifying requirements. It reduces premature implementation and helps map unknowns before committing to design or implementation decisions.

You should not use exploratory design when you need to produce implementation code, as this mode explicitly avoids generating code changes. It is intended for discovery, architecture mapping, and decision support rather than direct development tasks.