openspec-explore

To investigate existing codebase architecture for a new feature, you can read files, map integration points, and uncover hidden complexity without modifying application code. This process identifies key risks and open questions before you proceed.

The best way to compare design options and identify risks is to analyze approaches, visualize tradeoffs, and capture decisions in OpenSpec artifacts. This allows you to evaluate implementation paths against the current architecture systematically.

No, the openspec-explore skill does not modify application code during analysis. It explicitly prohibits application code implementation, permitting only repository reading and artifact creation to ensure a safe, read-only investigation of your architecture.

You need the OpenSpec CLI installed if you plan to check active changes during requirements exploration. The CLI is specifically required for managing and interacting with active OpenSpec change planning workflows.

You should not use codebase exploration for software design analysis when you are ready to write or modify application code. This approach is strictly for clarifying ideas, comparing options, and planning changes rather than implementing the actual solution.