Question

A developer tools team is building a feature that generates SQL queries from natural-language requests. They have a validator that can run each generated query against a test schema and return specific errors (syntax problems, missing columns, wrong joins). The team wants the system to iteratively improve its output until the query passes validation, since a single generation attempt often contains fixable mistakes. Which agent pattern best fits this need?

Accepted Answer

Evaluator-optimizer — one call generates the query and another evaluates it against the validator, feeding critique back in a loop until it passes

Answer

Routing — classify the request type first, then send it to a specialized query generator

Answer

Parallelization (voting) — generate several queries simultaneously and pick the one that appears most often

Answer

Orchestrator-workers — a lead model dynamically breaks the request into subtasks assigned to worker models