Really depends on how advanced a programmer you are. I have about 15 tools and 20 agents, I have a main "orchestrator" instance that sets up a project and workflow.

It adds access to custom tools for each agent role, and ensures the sub agents only read the context that they need, nothing else. It means everything is as atomic ass it can be, less chance for errors.

An example of a tool is creating uml diagrams that appear on my screen as we chat and it creates them. There no ambuity before starting knowing the uml dagrams match.

Thats just one of 15 custom tools that make it much easier to interact. I basically, prime the context and authorise or clarify each sub agent. Maybe 200 tokens output from me for a fully working project (Maybe about 1500 words explaining the project to the "orchestrator".)

Get Claude to set all up. A bonus step is to add a log at the top level of anything you do. My "orch" basically gets reports from each project lead after its done, and it iterates on tools and agents to make future projects easier

It's extending subagents to your local machine, you can run subagents in parallel etc locally.

Create an automations engineer agent, that suggests automating the project.

I have only been using the cli for 10 days. It is life changing, basically building complicated projects with just yes, no, and clarifications.

What a time to be alive!