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
atari-breakout-pongGuides standard Atari Breakout and Pong DQN/PPO workflows with preprocessing, devices, checkpoints, W&B logging, and safe synthetic smoke checks.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task is about the repository's standard Atari
Breakout/Pong workflows: DQN, PPO, ALE/Gymnasium preprocessing, Nature CNN
models, DQN replay buffers, PPO vector rollouts, device choice, W&B logging,
checkpoints, --test, or benchmark interpretation.
Do not use this sub-skill for Montezuma's Revenge, Pitfall, PrivateEye, RND, Go-Explore, restore-state search, or robustification curricula; route those to the hard-Atari exploration owner instead. Do not use it for CartPole PPO/DQN or GridWorld formulas.
--env breakout|pong, --device auto|cpu|cuda|mps,
wrappers, frame stacking, ROM/display requirements, or per-life versus
per-game returns.3-atari/1-dqn.py is the Atari DQN workflow label;
3-atari/2-ppo.py is the Atari PPO workflow label; 3-atari/env.py is the
preprocessing/device helper label. Treat these labels as provenance only, not
as files this sub-skill needs future agents to open.From this sub-skill directory:
python scripts/atari_basic_smoke.py --help
python scripts/atari_basic_smoke.py --device cpu
Use --device auto only when you want the helper to choose CUDA, then MPS, then
CPU using the same priority as the Atari workflows.