> single line addition to prompt to use subagents proactively.
This misses an important detail. In Claude Code [1], ultracode suggests the agent create a JavaScript code to deterministically orchestrate sub agents. This is different from just having the main agent launch sub agents and (non-deterministically) manage them.
The resulting workflow is called “dynamic” because CC creates this orchestration script dynamically, “on the fly”.
[1] https://claude.com/blog/introducing-dynamic-workflows-in-cla...
Another useful thing about dynamic workflows is you can ask Claude to make them durable as skills (or slash command) that can be invoked later.
I believe inside Google they have a similar concept called “deterministic workflows”.
I find ultracode extremely useful. Of course you have to watch how your 5 hour and weekly session usage percentages are getting used. So I had Claude make a status-line with 3 progress bars: for context window, 5h session, 7d session:
https://pchalasani.github.io/claude-code-tools/tools/statusl...
This misses an important detail. In Claude Code [1], ultracode suggests the agent create a JavaScript code to deterministically orchestrate sub agents. This is different from just having the main agent launch sub agents and (non-deterministically) manage them.
The resulting workflow is called “dynamic” because CC creates this orchestration script dynamically, “on the fly”.
[1] https://claude.com/blog/introducing-dynamic-workflows-in-cla...
Another useful thing about dynamic workflows is you can ask Claude to make them durable as skills (or slash command) that can be invoked later.
I believe inside Google they have a similar concept called “deterministic workflows”.
I find ultracode extremely useful. Of course you have to watch how your 5 hour and weekly session usage percentages are getting used. So I had Claude make a status-line with 3 progress bars: for context window, 5h session, 7d session:
https://pchalasani.github.io/claude-code-tools/tools/statusl...