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-and-weight-utilitiesInspect ControlNet model/config APIs and safely reason about checkpoint initialization, transfer, and state-dict mappings.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a user needs to understand ControlNet architecture/configs, inspect model-loading APIs, dry-run checkpoint key mappings, initialize ControlNet weights from Stable Diffusion, transfer an existing ControlNet to a compatible community checkpoint, or debug checkpoint-loading failures.
For generated-image app usage, route to gradio-inference-apps. For fine-tuning loops, Fill50K data, sd_locked, and dataset schema, route to training-and-datasets. For detector outputs and control-map creation, route to annotators-and-preprocessing.
create_model, load_state_dict, get_state_dict, ControlNet, ControlledUnetModel, ControlLDM, or DDIMSampler signatures and method responsibilities.cldm_v15.yaml with cldm_v21.yaml, explaining jpg/txt/hint, zero convolutions, locked/trainable branches, low-VRAM behavior, or attention options.tool_add_control.py, tool_add_control_sd21.py, or the ControlNet transfer-offset algorithm without destructive hard-coded outputs.scripts/inspect_weight_mapping.py when a user asks for a non-destructive report of ControlNet key mapping or newly initialized keys before writing a checkpoint.cldm_v15/SD1.5 initialization; SD2.1 uses cldm_v21/SD2.1 initialization.--self-test for the mapping logic.cldm_v15 vs cldm_v21": read configuration and architecture, especially context dimension, text encoder, attention head settings, and use_linear_in_transformer.scripts/inspect_weight_mapping.py with --config-family sd15 or sd21 and optionally --checkpoint.load_state_dict behavior and troubleshooting for dependency/device issues.