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
ddpm_pa_recovery_harnessRun a bounded DDPM-PA proxy optimizer step and emit mechanism-faithful recovery traces and metrics.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this skill when full DDPM-PA few-shot image generation is blocked by missing checkpoints, datasets, or image-quality evaluators, but soft-mode recovery permits a declared mechanism-faithful proxy. The skill combines the adaptation protocol, pairwise image preservation, high-frequency preservation, high-frequency MSE, and an optimizer update into an auditable reduced experiment.
Do not use this skill to claim full FID or Intra-LPIPS reproduction unless a real pretrained DDPM, target images, sampling loop, and evaluators ran. In proxy mode it validates the adaptation mechanism, not the paper's final image metric.
lambda2 and lambda3 in [0.1, 1.0], lambda4 in [0.01, 0.08] unless an ablation intentionally changes them.training_trace.json with loss values, component losses, params_before, params_after, and optimizer evidence.combined_loss_delta generated by an executable command.Run:
python scripts/proxy_step.py --output /tmp/ddpm_pa_proxy.json
python -m pytest tests
The tests assert finite loss, changed parameters, complete mechanism booleans, and target-compatible output fields.
The default script is intentionally tiny and standard-library only. It is a proxy for the DDPM-PA loss geometry and optimizer execution, not an image generation benchmark.
A zero-pairwise ablation must be recorded as an ablation rather than a valid DDPM-PA mechanism run, because it removes both source-referenced preservation losses even if the base proxy loss still decreases.