What problem does it solve? Adapting a float PyTorch model to the horizon_plugin_pytorch QAT toolchain requires multiple interdependent code changes (march setup, QuantStub/DeQuantStub insertion, dynamic_block annotation, prepare, fake quantize states) that must happen in a strict order; doing them out of sequence causes scope errors, broken graphs, or wrong quantization states. ## Core Features & Use Cases - Ordered orchestration: Invokes five sub-skills in a fixed sequence: set-march → insert-quant-dequant → dynamic-block → prepare → set-fake-quantize. - Mandatory march confirmation: Pauses the entire workflow to ask the user which march (e.g., NASH_E, NASH_P, NASH_B) to use before any code changes. - Consistency checks: Verifies structural changes happen before prepare, quant/dequant sit only at deployment boundaries, and fake quantize states match the calibration/QAT/validation phase. - Use Case: A user asks to fully adapt a float model in train.py to the Horizon QAT toolchain; the skill confirms the march, then applies each adaptation step in order and runs a final consistency checklist. ## Quick Start Ask the agent to fully adapt your float PyTorch model file to the horizon_plugin_pytorch QAT workflow and specify your target march.