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
multitask-modelingUse DeepCTR-Torch SharedBottom, ESMM, MMOE, and PLE multi-task models with aligned labels, losses, metrics, and predictions.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task needs one DeepCTR-Torch model to optimize more than one target with the implemented multi-task classes: SharedBottom, ESMM, MMOE, or PLE.
SparseFeat, DenseFeat, VarLenSparseFeat, feature names, and model_input dictionaries with ../feature-column-inputs/SKILL.md first.references/mtl-models-and-training.md for model selection, label matrix construction, compile/fit/predict flow, ByteRec-style two-target recipes, and metric handling.references/api-reference.md for exact constructor signatures, supported task types, loss strings, output shape, and parameter notes.references/troubleshooting.md before changing model code when target shape, task order, loss list, ESMM semantics, flattened metrics, or tiny batch behavior looks wrong.scripts/mmoe_multitask_smoke.py --help or the default smoke command to verify that a local installation can train an MMOE on inline two-label data and return predictions shaped (n_samples, 2).../single-task-modeling/SKILL.md and shared training references.(n_samples, num_tasks). Column i must be the label for task_names[i].model.predict(model_input, batch_size) returns a NumPy array shaped (n_samples, num_tasks). Prediction column i belongs to task_names[i]; evaluate each task column explicitly.task_types length must equal len(task_names). Supported values are "binary" and "regression" for SharedBottom, MMOE, and PLE; ESMM accepts two binary tasks only.task_names, for example ['binary_crossentropy', 'binary_crossentropy'] or ['binary_crossentropy', 'mse'].