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
fx-graph-workflowsOperate Optimum Torch FX graph transformations and version-gated tensor parallelism guidance.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task involves Optimum's Torch FX graph workflow surface:
optimum.fx.optimization.Transformation / ReversibleTransformation classes, compose(...), and reverse=True restoration.optimum.fx.parallelization.Do not use this sub-skill for GPTQ quantization, exporter task mapping, CLI export commands, dummy inputs, or normalized configs. Route those to the generated gptq-quantization, exporters-and-cli, or utilities-and-configs sub-skills.
torch.nn.Module.Confirm the user is asking for FX graph transformations or tensor-parallel triage, not export/quantization/config utilities.
For optimization work, require a torch.fx.GraphModule or trace a local torch.nn.Module into one. Keep inputs local and deterministic; avoid Hub downloads unless the user explicitly authorizes them.
Read references/fx-optimization.md before changing a graph. Apply transformations with default lint/recompile unless batching a compose chain.
Run the bundled smoke test when validating the local environment:
python scripts/fx_transform_smoke.py
python scripts/fx_transform_smoke.py --check-compose
For tensor parallelism, read references/tensor-parallelism.md first. Treat it as optional/advanced unless the environment has a compatible Python, CUDA-capable PyTorch with torch.compile, initialized distributed/NCCL process groups, and enough GPUs for the requested world size.
Use references/troubleshooting.md whenever import, graph lint/recompile, preservation, reverse, or backend errors appear.