A conversation/collaboration… not really.

You can create a ‘swarm’ of agents with differing roles, define different roles and phases, to have it iterate on a problem.

1. Investigations to discover and provide a condensed context of discoveries
2. Use this to propose a plan
3. Some number of iterations of one or more reviewing agents (you can give each an area of focus) criticising the plan, one or more agents to propose improvements based on the reviews, and an agent to review and apply the proposals before the next iteration

Groups of agents of the same role, operating in parallel, should ideally be using different models (or have context that gives them differing goals - eg focused on maintainable abstractions, security, scalability, test case identification, etc).

The implementation can do a similar thing - a code generator followed by reviewers, proposals for action, and then apply improvements… and you can iterate on testing or benchmarking too, all before hand-over.

This can improve results (at a non-trivial cost sometimes, so budgets are important) and it will still miss sometimes. You can help it of course with hints, directions or even implementations or stubs of implementations of abstractions you expect.