Back to Study Material Artificial Intelligence

STRIPS planning

STRIPS, which stands for Stanford Research Institute Problem Solver, is one of the earliest and most influential automated planning systems, developed by F...

STRIPS planning

The Language That Defined Classical AI Planning

STRIPS, which stands for Stanford Research Institute Problem Solver, is one of the earliest and most influential automated planning systems, developed by Fikes and Nilsson in 1971. STRIPS defined a formal language for specifying planning problems that remains the foundation of virtually all classical planning research.

A STRIPS planning problem consists of three elements. The initial state is a set of ground atomic formulas that are true at the start. The goal state is a set of conditions that must be true when the plan succeeds. The action schemas define available actions, each with three components: preconditions (facts that must be true before the action can execute), add list (facts that become true after the action), and delete list (facts that cease to be true after the action).

The blocks world domain is the canonical STRIPS example. Actions include Pick-Up(x), Put-Down(x), Stack(x, y), and Unstack(x, y). The action Stack(x, y) has preconditions that x is held and y is clear. Its add list includes On(x, y) and Arm-Empty. Its delete list includes Holding(x) and Clear(y). A planner searches for a sequence of these actions that transforms the initial state into the goal state.

STRIPS planning assumes a closed world, deterministic transitions, and instantaneous actions. These assumptions make planning tractable in simple domains but too restrictive for real-world scenarios where time, concurrency, and uncertainty matter. PDDL (Planning Domain Definition Language) is the modern successor, extending STRIPS with types, durative actions, and probabilistic effects.

The STRIPS assumption — the assumption that anything not in the add or delete list remains unchanged — is known as the frame assumption. It eliminates the need to explicitly state that unaffected facts remain true.

Exam tip: Always list all three components of a STRIPS action — preconditions, add list, delete list — and give a blocks world example. The frame assumption is a common short-answer question.