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
predictionRoutes UltralyticsPro prediction workflows for YOLO image inference presets and their shared sample-image defaults.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the user wants to run or adapt one of the repository's single-image prediction wrappers.
predict_v8.py, predict_yolo11.py, and
predict_yolov10.py.sub-skills/training instead.references/workflows.md for the preset-to-script map and the canonical
command forms.references/troubleshooting.md for weight, source, save-path, and device
failures.../../references/interface-reference.md when you need verified Ultralytics
API or CLI details.../../references/model-family-map.md when you need the broader source
script inventory.scripts/run_predict.py — preferred wrapper for all prediction presets. It is
safe by default and performs a dry run unless --execute is supplied.--list-presets when you are mapping a source script to the
bundled preset.--preset predict-yolo11 or another preset when you want the same model
and sample image pair as a source example.--model, --source, --imgsz, --conf, --save, --device,
--project, or --name when a user asks for a variation.--execute only after confirming that the model weights and source are
available and that the user is willing to start a real inference run.ultralytics/assets/zidane.jpg sample,
which is shipped with the verified public Ultralytics install..pt, the first execution may download the
pretrained weights when they are not already cached.Go back to SKILL.md if the task turns into general package inspection,
installation, or route selection across training and prediction.