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
trainingConfigures, runs, and evaluates Luminoth training jobs, including the optional Google Cloud ML workflow.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to train or evaluate a Luminoth model, tune a configuration file, or submit the same run to Google Cloud ML Engine.
lumi train and lumi eval command planning.--config and --override.train.job_dir, train.run_name, TensorBoard output, and
evaluation watch behavior.lumi cloud gc workflow, including train, evaluate, jobs,
and logs.Read references/configuration.md for the key config fields and override syntax.
Read references/workflows.md for local train/eval commands and the cloud workflow summary.
Run the bundled preflight before you suggest a train or eval command:
python scripts/check_config_keys.py --config ./config.yml --mode train
If the request involves Google Cloud, read references/cloud.md and confirm the required service account, APIs, and bucket setup.
If the task requires a run directory or checkpoint package, route that part to checkpoints instead of keeping it here.
lumi train -c ./config.yml
lumi train -c ./base.yml -c ./task.yml -o model.network.num_classes=3
lumi eval -c ./config.yml --split val --no-watch
lumi cloud gc train -c ./config.yml --bucket my-bucket --dataset gs://my-bucket/dataset
lumi cloud gc evaluate --train-folder gs://my-bucket/lumi_job --split val
Keep the answer anchored to the config keys the code actually reads:
model.typedataset.typedataset.dirtrain.job_dirtrain.run_nameThen explain any model-specific or cloud-specific fields only as far as the current task needs them.