What problem does it solve? Unreal Engine packaging failures are hard to diagnose because Build, Cook, Stage, Package, Deploy, and Run are distinct phases with different failure modes. This Skill structures the entire release pipeline so you can produce reproducible artifacts, isolate the first causal error, and verify builds on clean target hardware. ## Core Features & Use Cases - Pipeline orchestration: Separate and control Build/Cook/Stage/Package/Deploy phases via Project Launcher profiles, AutomationTool BuildCookRun, or CI, with a defined artifact contract. - Cook and content validation: Define cook roots, maps, chunks, and Primary Asset ownership; inspect manifests and containers instead of masking issues with -cookall. - Release hardening: Manage symbols, crash reporting, signing/encryption keys, config staging, runtime dependencies, patches, and DLC against a retained base release. - Use Case: A Shipping build crashes on a clean machine with an unreadable callstack. Use this Skill to match the exact build ID to retained private symbols, capture the runtime log, and identify the missing staged runtime dependency. ## Quick Start Use the unreal-packaging-deployment skill to diagnose why my packaged Unreal Engine 5.8 game is missing cooked assets in the Shipping build.