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
grid-world-dp-and-controlUse and adapt GridWorld dynamic programming, tabular control, Deep SARSA, and REINFORCE workflows distilled from the reinforcement-learning examples.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is about the repository's 5x5 GridWorld workflows: policy iteration, value iteration, tabular SARSA, tabular Q-learning, Deep SARSA, or REINFORCE. It is self-contained; do not depend on the original checkout at runtime.
1-policy_iteration.py, 2-value_iteration.py) as provenance workflow labels.3-sarsa.py, 4-q_learning.py) as provenance workflow labels.5-deep_sarsa.py, 6-reinforce.py) as provenance workflow labels.references/algorithm-guide.md for the MDP layout, coordinate conventions, formulas, API-shaped examples, and safe adaptation patterns.references/troubleshooting.md when a grid policy points in the wrong direction, rendering blocks on a server, tabular values do not update, or Torch neural checks fail.python scripts/grid_world_smoke.py --help
python scripts/grid_world_smoke.py
python scripts/grid_world_smoke.py --section dp
python scripts/grid_world_smoke.py --section neural --strict-torch
The smoke script intentionally reimplements tiny fixtures and update steps. It does not import source repository files, open Pygame, train to convergence, or require a display.
[row, col]; drawing helpers usually need (col, row), so swap before rendering arrows or markers.Env-style workflows use state as [col, row] and actions 0=up, 1=down, 2=left, 3=right.DynamicEnv-style workflows also use [col, row], but actions are 0=up, 1=down, 2=right, 3=left; the distilled source agents expose a fifth network output/action that behaves as a no-op in the dynamic environment.render_mode=None rather than opening Pygame loops.