Playbooks: what Devin should do repeatedly

Knowledge is what Devin should remember. A playbook is what Devin should do, repeatedly. Every dependency bump looks the same. Every bug triage follows the same steps. Writing a fresh prompt each time means re-describing a procedure your team has run fifty times, and risking inconsistent results depending on who wrote the prompt that day.

A playbook is that procedure written down once and shared across the org: the task, what you need to start (the parameters), the step-by-step, what "done" looks like, and what to never do. Next time the task comes up, anyone invokes the playbook, fills in the specifics, and gets the team's best-known process instead of each person's from-memory version.

You don't have to write one from scratch. The easiest way is to generate one from a session that went well. After a successful session, tell Devin: "Turn this session into a playbook. Parameterize the package name so we can reuse it." Devin distills what worked into a reusable template.

Using one is the easy part: in any new session, type ! to browse your org's playbooks, mention one with @Playbooks, or attach via + → Add Files → Playbooks. Fill in the specifics and go.

Playbooks are living documents. When a run goes sideways, fix the playbook rather than patching a one-off prompt, so the next person doesn't hit the same pothole.