diff --git a/docs/shared/concepts/inferred-tasks.md b/docs/shared/concepts/inferred-tasks.md
index 98135d3080dfe..3d81e31ea4396 100644
--- a/docs/shared/concepts/inferred-tasks.md
+++ b/docs/shared/concepts/inferred-tasks.md
@@ -1,9 +1,14 @@
-# Inferred Tasks
+# Inferred Tasks (Project Crystal)
 
 In Nx version 18, many Nx plugins will automatically infer tasks for your projects based on the configuration of different tools. Many tools have configuration files which determine what a tool does. Nx is able to cache the results of running the tool. Nx plugins use the same configuration files to infer how Nx should [run the task](/features/run-tasks). This includes [fine-tuned cache settings](/features/cache-task-results) and automatic [task dependencies](/concepts/task-pipeline-configuration).
 
 For example, the `@nx/webpack` plugin infers tasks to run webpack through Nx based on your repository's webpack configuration. This configuration already defines the destination of your build files, so Nx reads that value and caches the correct output files.
 
+{% youtube
+src="https://youtu.be/wADNsVItnsM"
+title="Project Crystal"
+/%}
+
 ## How Does a Plugin Infer Tasks?
 
 Every plugin has its own custom logic, but in order to infer tasks, they all go through the following steps.