A playbook is a recipe for work: a fixed set of steps that turns a known input into a known output, the same way every time. The value is that it repeats. A one-off question is a task; "every time a contract lands, pull the parties, the term, and the get-out clauses, then flag anything unusual" is a playbook.
The shift is from asking Claude a question to running Claude through a job. A good playbook names the trigger (what starts it), the steps in order (gather, shape, check), and the single finished thing it produces. It pulls together everything else in this course: projects for context, skills for method, connectors for reach, all running in Cowork.
Build one by spotting a job that repeats, naming the steps out loud, testing it once by hand, and adding a checkpoint on any risky step. When it works, put it on a scheduled task, or share it as a skill so your whole team runs it the same way.