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
on-policy-discreteGuides minimalRL single-process discrete CartPole policy-gradient, actor-critic, PPO, PPO-LSTM, and V-trace policy/value workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task asks about minimalRL's single-process discrete-action CartPole algorithms: REINFORCE, vanilla actor-critic, discrete PPO, PPO-LSTM, or the policy/value side of V-trace.
Policy contract and references/workflows.md for the return/backprop loop.ActorCritic.pi, v, make_batch, and train_net.prob_a, or advantage tensors misbehave.Identify the algorithm and action space. All workflows here assume CartPole-style observations of length 4 and 2 discrete actions unless you are intentionally porting.
Read the relevant API contract in references/api-reference.md before changing shapes, tuple fields, or update loops.
When porting to another discrete environment, update input dimension, output action count, softmax_dim, reward scaling, and termination handling together; see references/workflows.md.
Run the bundled shape smoke helper before attempting long training:
python sub-skills/on-policy-discrete/scripts/smoke_on_policy_discrete.py --algorithm all
If the failure involves Gym reset/step arity, PyTorch graph reuse, probability zeros, or hidden-state shapes, read references/troubleshooting.md before editing the algorithm.