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-decodingRun and adapt WeNet training recipes, checkpoint averaging, offline decoding, recognition modes, scoring, LM or k2 decoding, and training failure recovery.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the user wants to train or fine-tune a WeNet model,
resume an experiment, run offline recognition on a data.list, average
checkpoints, compare decoding modes, compute WER/CER, or reason about recipe
stages.
Ensure data manifests, dictionaries, and tokenizer resources are valid with ../data-preparation/SKILL.md.
Read references/workflows.md for the staged training/decoding recipe pattern and large-job boundaries.
Read references/cli-reference.md for the installed-module command shapes and important options.
Use scripts/score_text.py for small local WER/CER checks when the full recipe scorer is unavailable:
python sub-skills/training-and-decoding/scripts/score_text.py \
--reference ref.txt --hypothesis hyp.txt --unit word
Read references/troubleshooting.md when distributed training hangs, NCCL/HCCL/gloo fails, DeepSpeed configs disagree with WeNet configs, checkpoints are missing, or decoding output is empty.
python -m wenet.bin.train, recognize,
average_model, and alignment workflows.train.yaml exist.Real training, large decoding, LM graph creation, and k2/LF-MMI workflows can require large corpora, GPUs, distributed launchers, external toolchains, and long runtimes. Treat them as documented operational workflows unless the user explicitly authorizes the data, hardware, and time budget.