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
model-architectureRoute BiRefNet model construction, architecture, backbone, checkpoint, and export questions.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is about constructing or loading BiRefNet models, matching weights to the right backbone/configuration, cleaning checkpoint keys, understanding decoder/backbone flags, or planning ONNX/export work.
image2patches/patches2image, and check_state_dict, read references/api-reference.md.../inference-and-postprocessing/SKILL.md.Config data fields, task/testset/training-set selection, and custom data validation to ../configuration-and-data/SKILL.md.../training-and-evaluation/SKILL.md.Prefer BiRefNet(bb_pretrained=False) when loading a full BiRefNet checkpoint, then apply check_state_dict before load_state_dict. Use bb_pretrained=True only when intentionally initializing a new model with backbone weights and the configured backbone-weight files or torchvision/timm weights are available. Treat Hugging Face and ONNX flows as asset/backend-dependent unless the model cache, optional packages, and hardware/provider have been explicitly checked.
from_pretrained, Transformers AutoModelForImageSegmentation, or local .pth checkpoint.config.bb is swin_v1_l, while lite/tiny weights need matching config choices.scripts/birefnet_model_probe.py --repo-root <checkout> --json when a source checkout is available; add --construct-model only when dependency imports and memory are acceptable.module. and _orig_mod. prefixes before load_state_dict, then only treat remaining errors as true architecture mismatches.