sdd-explore

Codebase exploration involves investigating requirements and existing contexts to compare approaches before committing to a change. This structured analysis process clarifies risks and generates a shared report, reducing rework when planning features, bug fixes, or refactors.

Structured codebase exploration is the process of thinking through problems and investigating requirements before writing code. You need it for feature development, bug fixes, or refactor planning to clarify requirements, understand context, and reduce the risk of implementing the wrong solution.

To generate a structured exploration report for change management, provide a specific topic to explore along with the orchestrator context. The system then investigates the codebase and produces a structured analysis that can be shared with teammates or used to guide implementation decisions.

Yes, codebase exploration can be used for both bug fixes and feature planning. It investigates the codebase and requirements to understand the context before committing to a change, ensuring that risks are clarified and implementation decisions are guided by a structured analysis.

The best way to compare approaches before changing code is to run a structured exploration that investigates the codebase context and requirements. This generates a structured analysis detailing the options and risks, allowing you to confidently decide on an implementation path without rework.

You should not use codebase exploration when a change is trivial or lacks a named context, as exploration reports are designed to be created only when tied to a specific change or directed by orchestration to ensure meaningful analysis and avoid unnecessary overhead.