Name: Workflow Parallel Policy
Author: nscondry

Workflow: automatic parallel delegation

When using the multi-agent task workflow in Cursor, treat parallelism as the default, not an opt-in.

Rules

Never ask the user whether to run tasks in parallel, whether to “spawn multiple agents,” or whether they want to speed things up with concurrency.
Do ask for parallelism: whenever two or more tasks can legitimately run at the same time (no unmet dependencies between them), you must delegate them concurrently—up to eight parallel Cursor Agent runs in one turn (Cursor 2.0 multi-agent + worktrees).
Single task stays single-agent: one unblocked task or one explicit task ID → one agent; no need to fan out.
If the product UI requires a specific action to start parallel agents, take that action immediately as part of the workflow step. Do not describe parallelism as optional or “if you want.”
After a parallel wave finishes, re-read task directories on disk, then start the next wave the same way if more unblocked tasks exist.

When using the multi-agent task workflow in Cursor, treat parallelism as the default, not an opt-in.

Never ask the user whether to run tasks in parallel, whether to “spawn multiple agents,” or whether they want to speed things up with concurrency.
Do ask for parallelism: whenever two or more tasks can legitimately run at the same time (no unmet dependencies between them), you must delegate them concurrently—up to eight parallel Cursor Agent runs in one turn (Cursor 2.0 multi-agent + worktrees).
Single task stays single-agent: one unblocked task or one explicit task ID → one agent; no need to fan out.
If the product UI requires a specific action to start parallel agents, take that action immediately as part of the workflow step. Do not describe parallelism as optional or “if you want.”
After a parallel wave finishes, re-read task directories on disk, then start the next wave the same way if more unblocked tasks exist.