sdd-explore

Codebase architecture investigation defines an exploration report before committing resources to a change. It maps affected files, dependencies, and multiple approaches to ensure the orchestrator has precise findings.

An exploration report captures current architecture, affected areas, and strategies for ambiguous feature requests. It is needed for mid-to-large changes to reduce the risk of launching without a clear picture.

Store codebase analysis artifacts by following engram, openspec, hybrid, or none persistence strategies. This ensures later development phases have access to the same intelligence gathered during exploration.

Yes, sdd-explore works with engram and openspec persistence conventions. It supports these alongside hybrid and none strategies to store exploration artifacts for later development phases.

The best way to structure an exploration report for impacted files is a strict envelope containing status, executive summary, risks, and readiness, optionally creating an exploration.md file for named changes.

A limitation of using a sub-agent for codebase analysis is that it is applied specifically for mid-to-large changes where the orchestrator needs to research architecture, dependencies, and impacted files before committing.