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
configuration-and-cliAuthor and validate imagen-pytorch configs and safely use the imagen config, train, and sample CLI commands.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task mentions imagen config JSON, default_config.json, UnetConfig, ImagenConfig, ElucidatedImagenConfig, ImagenTrainerConfig, CLI train/sample commands, config validation, command generation, or safe preflight checks for the imagen console command.
type: "original" or "elucidated"), cascade length, image sizes, channel count, dataset/checkpoint keys, and sample/save/validation interval keys.python scripts/validate_imagen_config.py path/to/imagen_config.json --mode train --unet 1
python scripts/imagen_cli_quickcheck.py
--epoches spelling for training.imagen config --path ./imagen_config.json.dataset_name, dataset.batch_size, labels, checkpoint_path, imagen.image_sizes, imagen.unets, interval keys, and practical model sizes.imagen train be the first validator because it loads datasets and can enter expensive training.imagen train --config ./imagen_config.json --unet 1 --epoches 1 only after dataset and hardware are intentionally chosen.imagen sample --model ./imagen.pt --cond_scale 5 --load_ema true "prompt" only from a commandable trainer checkpoint and on a CUDA-capable runtime.video: true config switch: route to video-and-inpainting.Keep this sub-skill focused on static configuration, CLI flags, command preflights, and safe command construction. Do not use it as proof of generation quality; CUDA import smoke was verified for the package, but realistic Imagen training and sampling remain practical CUDA-scale work.