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
sf_transfer_recoveryRun a bounded successor-features plus GPI transfer recovery experiment for changing linear-reward RL tasks.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this skill to validate a reduced, mechanism-faithful recovery of Successor Features for Transfer in Reinforcement Learning. It should be used after successor-feature and GPI utilities exist and before claiming the paper mechanism has been recovered.
module_plan.json and environment/runtime_handoff.json.successor_feature_model and generalized_policy_improvement.recovery/recovery_result.json with mean_transfer_advantage.recovery/logs/generated_data_item.json describing the gridworld and reward weights.recovery/logs/generated_skill_invocations.json proving generated modules were imported/called.recovery/logs/training_trace.json recording exact dynamic-programming/source-policy construction traces.Run:
python scripts/run_sf_transfer_recovery.py --attempt-dir <attempt_dir> --skills-root <generated_skills_root>
python tests/test_recovery_harness.py
This is a reduced/proxy recovery. It does not reproduce the paper's four-room continuous-navigation or MuJoCo experiments, but it preserves the core mechanism of shared dynamics, changing linear rewards, successor-feature reweighting, and GPI transfer.