openspec-explore

To explore a codebase before making changes, you can inspect existing architecture, trace relevant code paths, and map integration points to ground your approach in reality. This process clarifies ambiguities and uncovers hidden complexity in the repository.

Analyzing architecture tradeoffs involves weighing multiple implementation approaches, highlighting specific risks, and comparing alternatives before committing to a direction. This ensures you validate constraints and choose the most suitable solution for your system.

Clarifying ambiguous codebase requirements requires turning vague ideas into sharper questions and defined constraint sets. By investigating existing patterns and dependencies, you can map the current system and identify unknowns.

Yes, you can compare implementation options without writing code by reading files, tracing logic, and recording insights for later use. This pre-change discovery phase focuses on option comparison and requirement clarification rather than actual implementation.

You need to trace code paths in a software repository when you are unsure how to add a new capability and must map the current system. This investigation identifies integration points, dependencies, and hidden complexity before you commit to changes.