investigate

To assess DDD readiness for a system migration, you perform a deep-dive system investigation that evaluates the codebase structure and technical debt. This analysis determines how well the current architecture supports domain-driven design principles and highlights areas needing adjustment.

System investigation identifies technical debt by utilizing AST analysis and pattern searching to detect and classify issues within the codebase. It categorizes these findings into a comprehensive report, highlighting areas that require immediate attention or refactoring.

You identify the technology stack and external services by running a system investigation that scans the codebase for languages, frameworks, and libraries. The investigation generates a report detailing all identified technologies and external service integrations.

To analyze codebase structure and technical debt before a refactor, you need a deep-dive system investigation that inspects directory layout, module structure, and classifies existing issues. This process generates detailed reports to help you understand the current state and plan improvements.

Yes, you need a local path to the codebase to start the system architecture investigation. The analysis requires direct access to the directory to perform AST analysis, pattern searching, and generate multiple detailed investigation reports.