dynamic-workflowslisted

# Dynamic Workflows A **dynamic workflow** is a self-authored, ephemeral multi-agent harness: a small program an agent writes for one task, runs once, and discards. It spawns subagents, gives each its own clean context window and model tier, optionally isolates them in worktrees, and coordinates their results. The capability and its patterns originate from Anthropic's "A harness for every task: dynamic workflows in Claude Code" (Shihipar & Bidasaria, 2026); the runtime is triggered by the word `ultracode`. This skill is **knowledge agents read, not a script they run** — a sibling of [`harness-engineering`](../harness-engineering/SKILL.md) and [`context-engineering`](../context-engineering/SKILL.md). It answers three questions before any workflow is authored: 1. **When** is a workflow warranted? — see [`references/when-not-to-use.md`](references/when-not-to-use.md). 2. **Which** pattern fits? — see [`references/patterns.md`](references/patterns.md). 3. **How** does the plugin's governance constrain it? — see [`references/governance.md`](references/governance.md). ## Runtime scope — Claude Code only Dynamic workflows are a **Claude Code runtime capability** and are **not transferable** to GitHub Copilot CLI or any other coding agent — those trees have no workflow runtime. This plugin ships to both the Claude Code and Copilot CLI trees, so this skill is **knowledge everywhere, runtime only on Claude Code**: - **On Claude Code:** workflows can be authored and spawn