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
paddle-workflowsUse face.evoLVe PaddlePaddle training, quantization, Paddle Inference, and Paddle Lite workflows safely.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is about the PaddlePaddle side of face.evoLVe: Paddle training configuration, Paddle model component inspection, quantization-aware training, post-training quantization, Paddle Inference server demos, Paddle Lite edge demos, or diagnosing missing Paddle deployment artifacts.
paddle/ source package as the PaddlePaddle framework..pdmodel/.pdiparams, enabling QAT with SAVE_QUANT_MODEL, or preparing dynamic/static PaddleSlim quantization.face_data.fdb, demo video input, GPU predictor settings, and recognition thresholds..nb model artifacts and runtime prerequisites for edge inference demos.data-preparation.face-alignment unless the Paddle demo-specific FaceDatabase flow is the focus.pytorch-training or feature-extraction-verification..pdmodel/.pdiparams/.nb artifacts, hard-coded GPU predictor settings, FaceDatabase/video/font problems, or data layout errors.Construction evidence confirmed only safe import/component checks: PaddlePaddle and PaddleSlim imported, and a Paddle IR_50 CPU eval forward produced a [2, 512] embedding shape. Full Paddle training, QAT quality, post-training quantization, Paddle Inference video recognition, and Paddle Lite edge deployment remain artifact/hardware-dependent and are not verified unless the user supplies data, trained/exported models, videos, fonts, and compatible runtimes.