​
What are Playbooks?

Playbooks are a way to create reusable prompt snippets that can be injected into Devin’s queries. This allows you to standardize certain tasks and make it easier for developers to use Devin effectively. Building up a robust and effective library of playbooks can significantly enhance our team’s productivity.

​
Creating a Playbook

Playbooks are just text snippets tied to a macro that can be referenced in Devin’s queries. To create a playbook, you need to define a set of prompts that are relevant to a specific task or workflow. For example, you might create a playbook for code reviews that includes prompts like:
  • Common code patterns
  • Frequently used libraries or frameworks
  • Specific project requirements
Once you’ve defined your playbook, you can enter a macro for it and then reference it in your interactions with Devin. You can also add instructions for Devin on how to use the playbook, such as:
  • “Immediately exit and inform the user if X doesn’t exist.”
  • “If this request is not related to X, do not use this playbook.”

​
Using a Playbook

You will have defined the macro for thhe playbook when you created it. If you named the macro code_review, you can inject it anywhere you are interacting with Devin by using the syntax !code_review.

​
Best Practices

  • Keep your playbooks generically appliable, but specifically relevant. An example of this is a playbook to review a PR under specfic criteria.
  • Regularly review and update your playbooks to ensure they remain relevant.
  • Let the team know when you create a new playbook so they can start using it.