Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.devin.ai/llms.txt

Use this file to discover all available pages before exploring further.

Cut the product-to-engineering handoff in half. When a PM drops a PRD in Notion, Google Docs, or Linear’s doc editor, this automation decomposes the document into actionable engineering tickets — complete with acceptance criteria, estimated sizing, and the right labels — then creates them in your Linear project.

Use this template

Open PRD to Linear Tickets in Devin and create the automation with the default configuration. You can customize it before saving.
Looking for a hands-on walkthrough? See the step-by-step tutorial for PRD to Linear Tickets.

​
What this automation does

The PRD-to-tickets automation is the first step in a fully-automated product pipeline. Pair it with Linear Ticket Implementation and you have spec-to-shipped-code in a single chain. Devin reads the document, identifies engineering work vs. design vs. open questions, and creates tickets with enough context for whoever picks them up.

​
How it works

Trigger: Linear event — label.added
  • Event: linear:label_added
    • Conditions:
      • addedLabel.name eq prd
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click PRD to Linear Tickets. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • PM → Eng handoffs where ticket creation is a bottleneck
  • Breaking down large feature specs into sprint-sized work
  • Spec review sessions where everyone wants tickets “right now”
  • Accelerating product delivery in fast-moving teams

​
Customization ideas

  • Switch ticket system (Linear, Jira, GitHub Issues, Asana)
  • Add label/priority mapping from PRD metadata
  • Scope to a specific Linear team or Notion database
  • Include design tasks, QA tasks, and docs tasks, not just engineering

​
See also