sdd-explore

Analyzing a codebase before implementation involves investigating existing architecture, dependencies, and patterns to clarify requirements. This process generates structured exploration artifacts that outline affected areas, compare approaches, and identify risks for engineering coordination.

Spec-driven development exploration is the structured investigation of proposed software changes before coding begins. It transforms vague requirements into technical analysis by comparing implementation options, evaluating tradeoffs, and producing reports that guide engineering decisions.

Comparing refactoring approaches and identifying risks before coding is essential for reducing premature decisions. This involves evaluating implementation options against existing architecture, weighing complexity and tradeoffs, and generating structured recommendations for technical coordination.

Turning vague software requirements into structured technical analysis requires investigating the codebase to clarify the requested change. This process evaluates affected files, dependencies, and patterns, producing exploration artifacts that compare approaches and highlight implementation risks.

Codebase exploration applies to spec-driven workflows involving bug fixes, refactors, and architecture decisions. It investigates existing tests and patterns related to the requested change, generating exploration reports that outline affected areas and identify implementation risks.

An exploration report for delegated engineering tasks should include codebase investigation findings, approach comparisons with tradeoffs, and identified risks. This structured artifact clarifies requirements and outlines affected areas to coordinate implementation across engineering teams.