Dynamic Workflow — plan-in-code fan-out with verification

This is Hermes's answer to Claude Code's "dynamic workflows" (run hundreds of parallel subagents in one session). The mechanic worth copying is NOT "more subagents" — it is moving the plan, the loop, and the intermediate results OUT of the context window and INTO a script. Normally the agent IS the orchestrator: every intermediate result piles into context, which is exactly what caps you at a handful of agents. A workflow keeps only the final verified answer in context; the script holds everything else.

This skill is self-contained, but it builds on standard fan-out hygiene — chunk inputs to ~50-70KB per child, route structured output to files (not the summary field, which truncates under load), use delimiter-separated lines over JSON wrappers, and remember that a "stalled" child often completed its write anyway (check the filesystem before retrying). If your install has a delegate-task-output-patterns skill, load it for the detailed thresholds; the rules above are the load-bearing subset.

The two orchestration-script layers (pick the right one — they are NOT interchangeable)