module-deep-research

You can analyze software architecture and build module documentation by applying a structured, read-only research method to evaluate code, tests, and configurations. This approach ensures you understand module behaviors and constraints without altering business code.

Creating reusable knowledge assets involves conducting in-depth module research to document execution paths, data models, and risks. This iterative process builds a continuous knowledge base for developers and architects to reference.

To research module responsibilities and execution paths, you analyze existing tests, documentation, and configurations iteratively. This read-only analysis clarifies module behaviors and risks without requiring code modifications.

Yes, you can use code analysis to document data models and constraints for complex modules. The structured research method focuses on extracting these details from existing code and configurations to build a comprehensive knowledge base.

You should not use a read-only module research approach when your goal is to fix bugs, refactor, or alter the business code. This method is strictly for building knowledge assets and understanding behaviors, not for modifying the existing codebase.