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
training-and-modelsUse Towhee's optional PyTorch Trainer, TrainingConfig YAML, NNOperator training bridge, and towhee.models package boundaries safely.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task involves Towhee's optional PyTorch training layer: TrainingConfig, Trainer, NNOperator.train(...), NNOperator.setup_trainer(...), checkpoint/model-card behavior, or deciding whether to install towhee.models instead of using Hub operators.
TrainingConfig fields, YAML save/load shape, device choices, loss/optimizer/scheduler names, Trainer, and NNOperator training, use Training configuration and Trainer.towhee.models package split, create_model(...) pattern, pretrained-download risk, and Hub-versus-model-zoo decisions, use Model-zoo boundaries.--check-imports only in an isolated environment where importing the optional trainer stack is acceptable.Trainer setup, NNOperator training hooks, checkpoint/model-card expectations, and model-zoo installation boundaries.ops, register, Hub revisions, and towhee init to operator-hub-and-cli.DataCollection, DataLoader, image/audio/video wrappers, and non-training data serialization to data-utilities.towhee server, Docker, Triton, and deployment packaging to serving-and-triton.python scripts/training_config_template.py --format yaml --output training_config.yaml
Start with device_str: cpu, dataloader_num_workers: 0, tensorboard: null, and pretrained=False model choices when the user only needs a portable template or diagnosis. Move to actual training only after the active environment has the intended PyTorch stack and any model/data downloads are approved.