Answer: A great Devin playbook should include a Procedure section with one step per line written imperatively, covering setup, the actual task, and delivery, plus Advice and Pointers, Specifications, and What's Needed From User sections. It should also tell Devin what good looks like and iterate through trial and error. Status: Confirmed Entry: tool/devin/features/playbook-best-practices Revision: 1 Digest: sha256:b01c1013f642abca (changes whenever the content changes) Timeline: Created: 2026-11-13T03:15:35Z Last changed: 2026-11-13T03:15:35Z Last verified: 2026-11-20T12:47:32Z Next check: 2026-11-21T12:47:32Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of procedure format | one step per line | [1] | 2026-11-20 required step coverage | at least one step for setup, the actual task, and delivery | [1] | 2026-11-20 procedure goal | Mutually Exclusive | [1] | 2026-11-20 specifications purpose | describe the postconditions of the playbook | [1] | 2026-11-20 parallel Devins | 2+ | [1] | 2026-11-20 deliverable clarity | Be explicit about what the deliverable is | [1] | 2026-11-20 Sources: [1] Cognition. "Creating Playbooks". https://docs.devin.ai/product-guides/creating-playbooks.md Role: primary. Accessed: 2026-11-20T12:47:32Z Quote: "Have **one step per line**, each line written imperatively" (Supports: procedure format) Quote: "Include at least one step for setup, the actual task, and delivery" (Supports: required step coverage) Quote: "Aim to make the steps **Mutually Exclusive** and **Collectively Exhaustive**" (Supports: procedure goal) Quote: "The **Specifications** section can be helpful to describe the postconditions of the playbook" (Supports: specifications purpose) Quote: "Run 2+ Devins in parallel with the same playbook to quickly identify possible errors." (Supports: parallel Devins) Quote: "Be explicit about what the deliverable is & how Devin should communicate the fact that it’s done" (Supports: deliverable clarity) Published: 2026-11-20T09:55:38Z Snapshot SHA-256: 41d0a504a8f38bf0f1e1a3c34f325ac080522a3b750d67ade9d9dbbec6a38f11 (captured 2026-11-13T03:15:35Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:15:35Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:47:32Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:47:32Z Last attempt: 2026-11-20T12:47:32Z Notes and limitations: Extracted automatically from a single official source (section "Writing a Great Playbook"). Related: https://latestn.com/tool/devin/features/playbook-macros What are macros in Devin playbooks? https://latestn.com/tool/devin/features/playbooks-to-skills-migration What happens to my Devin playbooks and !macro when my account moves to Skills? https://latestn.com/tool/devin/features/preinstalled-tools What is preinstalled on Devin macOS VMs and how do I select an Xcode version? https://latestn.com/tool/devin/features/mute-microphone-during-call How do I mute or unmute my microphone during a Devin voice call? https://latestn.com/tool/devin/features/open-deepwiki-symbol-explanation How do I open DeepWiki explanations for a code symbol in Devin Desktop? https://latestn.com/tool/devin/features/original-files-preserved Does migrating to Devin delete or change my other coding agents' original files? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:15:35Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/devin/features/playbook-best-practices/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/devin/features/playbook-best-practices POST: https://latestn.com/dispute/tool/devin/features/playbook-best-practices with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/devin/features/playbook-best-practices?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What should a great Devin playbook include? Revision 1, last verified 2026-11-20T12:47:32Z. https://latestn.com/tool/devin/features/playbook-best-practices (accessed 2026-11-21T09:56:57Z). @misc{LatestN_tool_devin_features_playbook_best_practices_r1, title = {What should a great Devin playbook include?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/devin/features/playbook-best-practices}}, note = {Revision 1; digest sha256:b01c1013f642abca; last verified 2026-11-20T12:47:32Z; accessed 2026-11-21T09:56:57Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/devin/features/playbook-best-practices