openspec-explore

To clarify requirements and map architecture in an unfamiliar codebase, use an exploratory analysis approach that reads files, traces dependencies, and summarizes findings without writing application code. This clarifies goals, constraints, and hidden assumptions before implementation.

Comparing design options in an existing repository involves investigating the current architecture, tracing flows, and sketching alternative approaches. This allows you to weigh tradeoffs and surface risks before committing to implementation.

Debugging unfamiliar systems requires reading files and tracing dependencies to map the relevant parts of the repository. This investigation clarifies how the architecture operates and highlights potential risks without modifying application code.

Yes, you can analyze an auth refactor by exploring the current system architecture and tracing dependencies. This outlines the implications of using a new module and surfaces risks without writing application code.

No, this codebase exploration approach does not write or modify application code. It strictly reads files, traces dependencies, and summarizes findings to clarify requirements and compare design options before implementation.