Turn PRDs into Sprint Tickets
Point Devin at a Notion PRD and get scoped Linear tickets for each work package.Connect Notion and Linear
Devin reads your PRD directly from Notion using the Notion MCP. Go to Settings > MCP Marketplace, find Notion, and click Enable. You’ll be prompted to authorize access to your Notion workspace — grant read access to the workspace where your PRDs live.Your Linear integration also needs to be connected. Go to Settings > Integrations > Linear and click Connect, then select the teams where Devin should create tickets. Once connected, Devin has native Linear tools automatically — no separate Linear MCP needed.
Point Devin at your PRD
Share the Notion page URL and tell Devin exactly how to structure the tickets. Be specific about the Linear project name, your ticket format, and any team conventions.If your team follows a specific ticket template, add it as a Knowledge entry instead of repeating it in every prompt. For example: “All engineering tickets must include: Description, Acceptance Criteria, Technical Notes, and T-shirt size estimate.” Devin applies Knowledge automatically to every session.
Review the ticket breakdown
Devin reads the full PRD via the Notion MCP, searches your codebase to map the relevant architecture, then creates Linear tickets scoped to independent code boundaries. It posts a summary like this:
Each Linear ticket includes acceptance criteria, file paths, and implementation notes drawn from the actual PRD and codebase — not generic descriptions.
| Ticket | Title | Size | Dependencies |
|---|---|---|---|
| UP-101 | Add avatar upload endpoint to /api/users/avatar | S | None |
| UP-102 | Create profile settings page in src/pages/settings/profile | M | None |
| UP-103 | Migrate users table to support bio and social links | M | None |
| UP-104 | Build profile preview card component | S | UP-103 |
| UP-105 | Add public/private visibility toggle to profile settings | M | UP-103 |
| UP-106 | Index new profile fields in Elasticsearch for user search | L | UP-103 |