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
trainingConfigure and launch LatentSync U-Net and SyncNet training with safe config, file-list, DDP, checkpoint, and VRAM guidance.
Independent GitHub snapshot · Automated classification · Original documentation governs
Route LatentSync training work through this sub-skill when the task involves choosing or adapting U-Net or SyncNet training configs, generating dataset file lists, rendering distributed launch commands, or diagnosing training-time config/checkpoint/VRAM failures.
stage1, stage1_512, stage2, stage2_512, and stage2_efficient configurations.torchrun command rendering for scripts.train_unet and scripts.train_syncnet without executing long training unless explicitly requested..mp4 clips.scripts/run_training.py — render or explicitly execute a safe torchrun command for U-Net or SyncNet training; run it after editing a config copy and use --preflight to validate data/file-list paths.scripts/write_fileslist.py — recursively write deterministic training fileslists from one or more processed dataset roots.references/workflows.md — U-Net and SyncNet training flow, dataset/file-list preparation, command patterns, and post-training validation notes.references/configuration.md — config anatomy and how the U-Net and SyncNet variants differ.references/troubleshooting.md — failure-mode matrix for checkpoints, DDP, fileslists, VRAM, and config mismatches.scripts/train_unet.py and train_unet.sh, adapted through scripts/run_training.py.scripts/train_syncnet.py and train_syncnet.sh, adapted through scripts/run_training.py.tools/write_fileslist.py, adapted as scripts/write_fileslist.py.configs/unet/*.yaml, configs/syncnet/*.yaml, configs/audio.yaml, and configs/scheduler_config.json, distilled in the bundled references and launcher metadata.docs/syncnet_arch.md, distilled in references/configuration.md.latentsync/data/*_dataset.py, latentsync/models/*.py, latentsync/trepa/loss.py, latentsync/utils/util.py, and latentsync/whisper/audio2feature.py, used to explain runtime requirements and failure modes.--repo-root to make that explicit.torchrun, not direct python -m, because both training entry points initialize distributed state from torchrun-provided environment variables.--execute only after paths, fileslists, checkpoints, CUDA devices, and VRAM budget are verified.stage2_512.yaml as a high-VRAM production configuration, not as a casual smoke target.