Don't want to set this up manually? Paste a link to this page into a Devin session and ask it to set everything up for you. Start by creating a [playbook](/product-guides/creating-playbooks) for the task you want to standardize. In this example, we'll build a playbook that generates API documentation whenever a team member labels a ticket. Go to [**Settings > Playbooks**](https://app.devin.ai/settings/playbooks?utm_source=docs\&utm_medium=use-case-gallery) and click **Create playbook**. Give it a name and a macro (e.g., `!add-docs`). Write specific, step-by-step instructions. Reference real file paths and conventions so Devin follows your team's standards: ```txt !add-docs playbook theme={null} Read the Linear ticket for context on the feature or endpoint. Then: 1. Find the relevant source code — route handlers, controllers, models, and type definitions 2. Read our existing docs in docs/api/ to understand the format and conventions we use 3. Generate documentation covering: endpoint URL, HTTP method, request/response schemas, authentication requirements, error codes, and a usage example with curl 4. Add the new page to the docs sidebar in docs/sidebar.json 5. If there are related endpoints, add cross-references 6. Open a PR with the new documentation ``` The more specific your playbook, the better the output. Reference your team's actual doc templates, style guides, and tooling. See the [playbook docs](/product-guides/creating-playbooks) for more on writing effective playbooks. Connect your [Linear integration](/integrations/linear) if you haven't already: go to [**Settings > Connections > Linear**](https://app.devin.ai/settings/connections/linear?utm_source=docs\&utm_medium=use-case-gallery) and click **Connect**. Select the teams Devin should have access to. Once connected, scroll to **Synced playbook labels** and click **Add playbook**. Select `!add-docs` from the dropdown. This automatically creates a label called `!add-docs` in Linear under the **Devin Playbooks** label group. Now when anyone adds that label to a ticket, Devin starts a session using your playbook. For playbook labels to sync to Linear automatically, your Linear workspace must have **Manage workspace labels** set to **All members** (found under Linear's **Settings > Security**). If that's not enabled, you'll need to create the labels manually in Linear. When a team member adds the `!add-docs` label to a ticket like this: > **ENG-215**: Add POST /api/v2/webhooks endpoint — accepts a URL and event types, validates the URL is reachable, stores the subscription, and returns the webhook ID. Devin automatically starts a session and follows your docs playbook: * **Reads the ticket** — pulls the endpoint description, parameters, and any linked PRs * **Finds the source code** — locates the route handler, request validation schema, and response types * **Generates documentation** — creates a new page in `docs/api/` following your existing format * **Opens a PR** — includes the new doc page and updated sidebar This works well for batch operations too — multi-select tickets with **Cmd+A**, right-click, and add the `!add-docs` label to generate docs for multiple endpoints in parallel. With the Linear integration installed, Devin natively has access to Linear's tools — so your playbook can instruct Devin to update ticket labels or status based on the outcome. Since labels can trigger other automations, you can chain workflows — e.g., after docs are generated, a `Docs Ready` label could notify the tech writer for review. The same pattern works for any recurring task. Create a playbook, sync it as a label, and your team can trigger it from any ticket. Here are some ideas: * **`!write-tests`** — Add test coverage for the feature described in a ticket * **`!refactor`** — Refactor code following your team's conventions * **`!security-audit`** — Review code for security vulnerabilities and open a PR with fixes * **`!migrate`** — Run a standardized migration (dependency upgrade, API version bump) You can also set up [automation triggers](/integrations/linear) so Devin starts working without anyone applying a label at all. Go to [**Settings > Connections > Linear**](https://app.devin.ai/settings/connections/linear?utm_source=docs\&utm_medium=use-case-gallery), scroll to **Automation triggers**, and configure a trigger that fires when tickets transition to a specific status or label.

{title}