# 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.
```motion-demo
{
"id": "sequence",
"title": "Overall choreography",
"src": "demos/sequence.html",
"duration": 20.033333,
"status": "authored",
"description": "Motion and composition example",
"initialTime": 4.4,
"params": [
{
"key": "title",
"label": "Sample main copy",
"type": "text",
"value": "Orchestrate",
"maxLength": 60
},
{
"key": "accent",
"label": "Accent color",
"type": "color",
"value": "#9966cc"
}
],
"presets": [
{
"label": "Default content",
"values": {
"title": "Orchestrate",
"accent": "#9966cc"
}
},
{
"label": "OpenDesign adaptation",
"values": {
"title": "OpenDesign",
"accent": "#7050da"
}
}
]
}
```
## 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.
## 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.
## 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.
## Color and typography
Sans-serif interface text with a clear size hierarchy.
#f5f5f1 · #202122 · #9966cc · #f1ba8a · #9ab8ad
## Elements and production rules
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
## Content replacement
- 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 parameters
[Visuals and objects](style.json) · [Section timing](timeline.json) · [Position data](tracks.json) · [File manifest](manifest.json)
This specification is based on the reference video. The HTML provides editable choreography examples; each file identifies the source, precision and valid interval of its data.
```motion-board
{
"version": 1,
"brand": "Cursor",
"id": "V075",
"palette": [
"#f5f5f1",
"#202122",
"#9966cc",
"#f1ba8a",
"#9ab8ad"
],
"typography": "Sans-serif interface text with a clear size hierarchy",
"sample": "Orchestrate",
"objects": [
"Input field",
"Command label",
"Planner",
"Subplanner",
"Worker",
"Verifier",
"Tree lines"
],
"frames": [
{
"path": "assets/reference-1.jpg",
"timeSeconds": 0.0,
"frameId": "K0001",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-2.jpg",
"timeSeconds": 4.0,
"frameId": "K0005",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-3.jpg",
"timeSeconds": 8.0,
"frameId": "K0011",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-4.jpg",
"timeSeconds": 10.0,
"frameId": "K0013",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-5.jpg",
"timeSeconds": 14.0,
"frameId": "K0018",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-6.jpg",
"timeSeconds": 19.0,
"frameId": "K0023",
"role": "reference-evidence",
"status": "measured"
}
],
"stages": [
{
"start": 0.0,
"label": "Enter the task",
"end": 2.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 2.0,
"label": "Command completion",
"end": 4.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 4.0,
"label": "Main planner",
"end": 5.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 5.0,
"label": "Work and verification",
"end": 8.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 8.0,
"label": "Feature explanation",
"end": 10.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 10.0,
"label": "Recursive branching",
"end": 12.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 12.0,
"label": "Subplanning and work",
"end": 14.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 14.0,
"label": "Verification complete",
"end": 16.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 16.0,
"label": "Name and command",
"end": 19.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 19.0,
"label": "Brand",
"end": 20.033333,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
}
],
"duration": 20.033333,
"fontFamily": "Arial, sans-serif"
}
```