search-first

Pre-coding research identifies existing libraries and patterns by triggering a researcher agent to scan for viable solutions before writing new code. This systematizes code reuse and prevents reinventing the wheel when initiating new features or building utilities.

A decision matrix for evaluating dependencies applies a structured framework to assess suitability, maintenance, and integration effort of existing tools. It enables teams to make informed adoption, extension, or build decisions to reduce code duplication and accelerate delivery.

To stop reinventing the wheel, use a research-first workflow that orchestrates a researcher agent to surface existing tools and libraries before implementation. This structured evaluation of options ensures you reuse existing solutions instead of creating redundant code.

You should evaluate dependencies before building new utilities or abstractions, initiating new features, or creating new patterns. Pre-coding research ensures you identify existing solutions first, applying a structured decision matrix to determine whether to adopt, extend, or build.

A research-first workflow supports evaluating existing tools at scale by orchestrating a researcher agent to surface options and applying a structured decision matrix. This systematically assesses suitability, maintenance, and integration effort to reduce duplication across teams.

The research-first approach relies on a researcher agent to surface existing tools and a decision matrix for evaluation. While it systematizes code reuse, limitations include the quality of surfaced options and the subjective weighting of the decision matrix when assessing integration effort.