deep-understanding

To ensure accurate codebase understanding, enforce a deep-read of all relevant files and document findings, uncertainties, and corrections in a persistent markdown file for review before proceeding.

The best way to document code research is to write a detailed research.md file capturing what was learned, uncertainties, and corrections, serving as a review surface to verify understanding prior to execution.

You need to write a research.md file when working on tasks involving multiple files, complex behavior, or unfamiliar systems, requiring a written artifact for review before any planning or implementation begins.

Yes, a deep-read workflow improves traceability and rationale for decisions in complex, multi-file work by producing a persistent markdown artifact documenting what was learned and corrected before execution.

No, a written markdown artifact for review is required for meaningful tasks touching non-trivial code, not for simple modifications, ensuring comprehensive understanding only when navigating complex behavior or unfamiliar systems.

You should read the codebase in depth to prevent misunderstandings and improve rationale traceability, ensuring every meaningful task starts with accurate understanding verified through a persistent markdown artifact.