accelerated-mode

The loop runs one step at a time, each gated. On Claude Code there is an optional faster gear for the slow, repetitive parts: a dynamic workflow — a small program that fans work out across many short-lived agents at once instead of walking a list one item at a time.

This skill holds the rules that are identical across every surface that offers one. The commands hold only what differs: which script, what arguments, and how to fold the results back in.

The two gates — both must hold, every time

1. Runtime gate. A Workflow tool must be available. It exists only in Claude Code. On Codex, opencode, or any copy-paste chat surface there is no Workflow tool. Do not emulate one with extra Task subagents — that would break the 3-agent cap and produce an unbounded fan-out on a surface that was never designed for it.
2. Opt-in gate. The user asked for it this run — "verify with a workflow", a workflow argument, or an ultracode request. Never automatic. A single run can spawn many agents (up to 16 concurrent, 1000 over a run) at real token cost, so it is always a deliberate escalation the user chose.

If either gate is false, run the serial path. Not a degraded version of it — the same path that has always been the default.

Fallback is the design, not a safety net

The serial path is the portable one: it works on every surface the loop runs on. The accelerated path can only ever be a speed-up on one of them. So every accelerated step is written to fall through cleanly, and nothing in the loop may depend on a workflow having run.

Detection is automatic: no Workflow tool means not Claude Code, which means serial.