This is basically exaclty what Cursor started doing when Composer was first released.

The app would start using it for exploration tasks, and then as it improved it became the default for writing code and tests too. You can change it of course, but I find it does a pretty decent job if you have a large model directing it.

The parent model of course checks the work, but most of the time the handoff is good enough that no edits are needed.

It's also pretty fast and cheap, firing off a bunch of sub-agents to explore different parts of the codebase is a regular occurrence for the way I work.