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-workflowsConfigure and launch EasyR1 distributed RL post-training jobs with OmegaConf configs, CLI overrides, Ray/FSDP/vLLM runtime assumptions, algorithms, LoRA, logging, checkpoint resume, and launch troubleshooting.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to configure, lint, explain, or launch an EasyR1 RL post-training job through python -m verl.trainer.main.
python -m verl.trainer.main config=... key=value... command from a config path and CLI overrides without executing it.This sub-skill owns training configuration and launch decisions: OmegaConf files, CLI overrides, python -m verl.trainer.main, Ray resource assumptions, FSDP actor/ref/critic settings, vLLM rollout settings, GRPO/DAPO/Reinforce++/ReMax/RLOO/GSPO/CISPO/SAPO choices, LoRA launch cautions, logger selection, validation, save, and resume.
Route these tasks elsewhere in the EasyR1 skill graph:
data-and-rewards.DataProto, padding/unpadding, dynamic batching internals, and low-level algorithm tensor APIs belong to core-apis.checkpoint-export.Static config checks and command construction are CPU-safe and do not prove that a full training run will work. Full EasyR1 training requires a CUDA-capable runtime with the EasyR1 training stack, including Ray, vLLM, flash-attn, a compatible PyTorch build, sufficient GPUs, and accessible model and dataset assets.