sdd-explore

Codebase exploration is the process of analyzing ideas and assessing risks before implementing a change. It helps identify tradeoffs, clarify requirements, and generate a structured report outlining the current state and recommended actions for refactors or new features.

To assess risks for a codebase refactor, provide a named change topic to generate a formal exploration report. This captures the current state, evaluates options, outlines potential risks, and records recommended actions to ensure traceability before committing.

You need a structured exploration report when clarifying requirements or planning feature ideas. It provides a formal artifact that captures tradeoffs and risk assessments, ensuring decision-making and change management are thoroughly documented before code changes begin.

Yes, you can apply code analysis to clarify requirements across a project. By exploring a named change, the workflow analyzes the current state and generates a ready-to-persist artifact that ensures traceability for your feature ideas or refactoring efforts.

The best way to document decision-making is to generate a formal exploration artifact tied to a named change. This persists your risk assessment and tradeoff analysis, creating a traceable record of the current state, options, and recommended actions.