ııı motion.mdVideo style specification
Cursor / V075

Cursor · Recursive task orchestration

Explain recursive collaboration through a gradually growing task tree. Planning, execution, and review are distinct roles; graphical expansion must follow their dependencies.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 20.03 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Introducing /orchestrate, a skill that recursively spawns agents to tackle your most ambitious tasks with the Cursor SDK · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f5f5f1}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsInput fieldCommand labelPlannerSubplannerWorkerVerifierTree lines
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Grow the first division of work from one command

After task input, show the main planner, connect workers first, then place reviewers after the relevant work. Do not open with a fully complex tree; allow viewers to learn the roles.

Keep the diagram clear with ample white space, short labels, and fine lines. Use distinct accents for planning and review, more neutral execution nodes, and consistent brief sans serif labels.

02

Subplanners unfold the same rule

When a task needs subdivision, grow a subplanner from that branch, followed by its own work and review nodes. Grow mainly in one direction, using clear elbow connections and avoiding lines through labels.

Update the branch after review completes, then collapse local details. Collapsing must not erase the task's origin; retain completed relationships in the parent node.

03

Keep roles fixed while depth varies

For research, design, or engineering tasks, choose node counts and levels from real responsibilities. Preserve planning→work→review→results returned upward; do not mistake same-level positions for strict serial execution.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 4.00 seconds
4.00s
Composition reference at 8.00 seconds
8.00s
Composition reference at 10.00 seconds
10.00s
Composition reference at 14.00 seconds
14.00s
Composition reference at 19.00 seconds
19.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to hierarchical task orchestration, preserving the dependency tree and execution-before-verification
  • Tree depth and node count may vary, but nodes at the same level need not share an execution order

Production constraints

Input field / command label / planner / subplanner / worker / verifier / tree lines

  • Top-level planning creates tasks, which branch further into subplans and worker nodes
  • validators change color after the corresponding work, and completed local graphs collapse
  • use a simple orthogonal tree for connections, with colors distinguishing planning and validation roles