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
running-and-trainingRun, validate, and troubleshoot Scenic app/config/training workflows without accidentally launching expensive jobs.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a user wants to install-check Scenic, understand how the
Scenic application runner passes --config, --workdir, dataset-service, RNG,
and JAX backend flags into training, validate an experiment config before
launch, build a safe training command, or troubleshoot training utility imports.
lr_schedules, optimizers, train_utils, TrainState, checkpoint helpers,
trainer flow, transfer/pretraining caveats, and source-script exclusion notes.running-and-configuration.md.--config and --workdir; add
--dataset_service_address only with a compatible config.training-api.md.tensorflow_addons, keras.src.engine, big_vision, or trainer import
failures: read troubleshooting.md; avoid importing the trainer registry
for simple config/LR/optimizer checks.../modeling-and-layers/SKILL.md.../data-pipelines/SKILL.md.../baselines-and-projects/SKILL.md.Do not tell future agents to open or run the original repository's tests, examples, notebooks, or source files for this sub-skill. Use the bundled references and helper script as the runtime knowledge base.