sdd-explore

Spec-driven development exploration clarifies requirements by investigating code, analyzing architecture, and comparing implementation strategies before coding. It identifies affected files and outlines pros, cons, and complexity to prevent wasted development effort.

Comparing implementation options involves analyzing different strategies for your feature, outlining the pros, cons, and complexity of each. This process yields a clear recommendation with identified risks to guide your development approach.

The best way to identify affected files during codebase exploration is by analyzing current architecture and tracing the impact of potential changes. This investigation highlights specific code areas requiring modification and evaluates associated risks.

Yes, you can persist exploration artifacts when using spec-driven development by saving analysis outputs to Engram or openspec. This preserves your architecture investigation and options analysis for future reference.

Spec-driven development exploration works without external dependencies, operating based on provided context and detail levels. Optional artifact persistence to Engram or openspec is available but not required for core analysis.

You should avoid codebase investigation when the implementation path is already well-defined and risks are minimal. If the feature requires no architectural clarification or options comparison, preliminary exploration adds unnecessary overhead.