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-generationInspect and operate OpenPrompt training, evaluation, generation, runner selection, device placement, checkpointing, few-shot, zero-shot, LM-BFF, and ProtoVerb workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task asks how to run, inspect, resume, test, or debug OpenPrompt training/generation jobs after the dataset, template, verbalizer, and package environment choices are known.
Start here:
Operating rules:
experiments/*.yaml with scripts/inspect_training_config.py before running experiments/cli.py or a tutorial script.experiments/cli.py: classification with classification.auto_t or classification.auto_v uses LMBFFClassificationRunner; classification with verbalizer: proto_verbalizer uses ProtoVerbClassificationRunner; other classification uses ClassificationRunner; task: generation uses GenerationRunner.environment.num_gpus > 0 as a real CUDA request. OpenPrompt calls model.cuda() or wraps DataParallel; it does not automatically fall back to CPU when CUDA is unavailable.BaseRunner writes TensorBoard and checkpoints under config.logging.path unless train.clean: True. The code writes checkpoints/last.ckpt and copies to best.ckpt on improved validation; the declared checkpoint.save_latest and checkpoint.save_best flags are not enforced by BaseRunner.tgt_text and correct teacher_forcing/predict_eos_token behavior. For evaluation/generation, pass generation kwargs deliberately; generation.max_length includes prompt/input tokens in the native generation API.experiments/cli.py: few-shot loops over sampling_from_train.seed; zero-shot calls runner.test() without fitting.../data-and-config-workflows/, prompt grammar/verbalizer design to ../template-verbalizer-design/, and top-level import/loading quickstarts to ../pipeline-basics/.accelerate, and PaddlePaddle tutorial variants are optional workflows. The minimum verified scope is CPU package/config/API inspection, not GPU training throughput or benchmark reproduction.