search-first

To evaluate existing solutions before coding, apply a search-first workflow during the PM or lead design phase to assess new libraries, tools, and architectures. This process ensures evidence-based tool selection and outputs an Adopt, Extend, Compose, or Build decision.

A structured evaluation checklist for dependency evaluation assesses compatibility, maintenance status, licensing, and dependency footprint. It runs parallel searches across package managers, official docs, community solutions, and GitHub trends within a timebox to inform tool selection.

Trigger a search-first workflow during early design phases when introducing new libraries, tools, or architectures, or solving unfamiliar problems. It applies systematic risk-management and decision-making to prevent reinventing existing solutions and ensure proven solutions are sought.

To document a progress decision record for new architecture choices, evaluate dependency options against a structured checklist and output a final Adopt, Extend, Compose, or Build decision. This ensures evidence-based tool selection and risk-management are formally recorded.

Choosing between Adopt, Extend, Compose, or Build decisions requires a parallel search across package managers and community solutions within a timebox. Evaluate compatibility, maintenance, licensing, and dependency footprint to determine whether to use proven solutions or build custom.

A timeboxed search workflow for evidence-based tool selection limits exhaustive evaluation, relying on parallel searches across package managers, official docs, and GitHub trends. It focuses on compatibility, maintenance, licensing, and dependency footprint rather than comprehensive risk-management coverage.