pddl-skills

Must be used whenever the user asks which actions are applicable, available, legal, or possible in a PDDL state — regardless of how small or "obvious" the problem looks. Triggers: "what actions can I take", "applicable actions", "available actions", "legal moves", "what can be done next", "possible actions from this state", "enumerate actions", given a domain + problem + optional partial plan. Do not attempt to enumerate applicable actions by reading PDDL manually: human-style enumeration consistently miscounts, hallucinates inapplicable actions, and confuses similarly-named action variants (e.g. push-to-goal vs push-to-nongoal). The bundled script is the only authoritative source — invoke it on every such request.

Use this skill when the user wants to SOLVE a PDDL planning instance — given a domain.pddl and problem.pddl, produce a valid plan. Triggers: "solve this PDDL problem", "find a plan for", "generate a plan", domain.pddl + problem.pddl together, "what plan achieves this goal", plan validation, plan repair, "check if this plan is valid", "fix this invalid plan".