executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
video-inferenceBuild and validate one-shot TurboDiffusion Wan T2V/I2V inference commands without running models.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to plan or review a one-shot TurboDiffusion video generation command for:
Do not use this sub-skill for interactive multi-turn generation; route that to interactive-serving. Route checkpoint conversion, quantization, rCM/SLA training, and checkpoint merging to training-and-checkpoints. Route CUDA extension, Sparse/SageSLA dependency, custom-op, and low-level acceleration failures to acceleration-backends.
These helpers only render shell commands. They do not import TurboDiffusion, download assets, run models, train, convert checkpoints, or access credentials.
--quant_linear mistakes.TurboDiffusion's public one-shot scripts are usually launched from a source layout with helper packages such as imaginaire, rcm, serve, SLA, and ops importable from the inner turbodiffusion source directory. If a command fails with an import such as No module named imaginaire, add a public source-layout PYTHONPATH pointing at that inner source directory, for example PYTHONPATH=turbodiffusion, or run from an environment/layout where those helper packages are already importable.