openspec-explore

Exploring architectural tradeoffs involves mapping integration points and surfacing unknowns through read-only codebase investigation. This skill analyzes repository artifacts and sketches non-implementing designs to clarify requirements before proposing actual code changes.

Investigating codebase constraints requires inspecting repository artifacts to map relevant files and identify complexity hotspots. This skill enables exploratory analysis to surface risks and integration points without modifying existing code.

Yes, the OpenSpec CLI is required to inspect artifacts and optionally generate proposals, specs, or design notes. It provides the structured environment needed to crystallize discoveries from exploratory conversations into non-implementing artifacts.

Yes, you can draft specifications for real-time collaboration by mapping architectures, listing risks, and capturing decisions. It helps product managers and engineers explore tradeoffs and produce non-implementing proposals before development begins.

The main limitation is that exploratory analysis produces non-implementing artifacts only; it does not generate executable code. It is designed for early discovery and requirement clarification rather than direct software implementation or repository modification.