research

You should run code pattern analysis to prevent regressions before any writing task, specifically during the planning and coding phases. Early detection of functionality conflicts and overlaps across agents prevents regressions and avoids code duplication.

To analyze a codebase for existing implementations, run a search during the planning phase to identify similar modules, check for conflicting APIs, and document findings for the team. This prevents duplication by providing a proactive inventory of current code patterns to reuse or extend.

The best way to detect naming and functionality conflicts during feature planning is to run systematic checks against existing specs and reference patterns. This early detection prevents duplication and regressions before any writing or coding begins.

To gather context from specs and patterns for cross-agent planning, consult available references to locate related code and document findings. This guides decisions by enabling proactive inventory and gathering contextual knowledge across agents and features.

Yes, you can use codebase analysis to find reuse opportunities across different features. It provides a proactive inventory of current code patterns and implementations, applying systematic checks to reuse or extend existing modules before writing new tasks.

You should run code pattern analysis to prevent regressions before any writing task, specifically during the planning and coding phases. Early detection of functionality conflicts and overlaps across agents prevents regressions and avoids code duplication.