Turn PRDs into Sprint Tickets
Point Opulent at a Notion PRD and get scoped Linear tickets for each work package.
Connect Notion and Linear
Connect Notion so Opulent can read the PRD and any linked context. Connect Linear so it can create the tickets. If your team uses Jira, the Atlassian connector can create Jira issues instead.
The ticket-creation process follows a playbook, a reusable, named set of steps for turning a PRD into a scoped backlog. It defines the ticket format, size estimates, and dependency ordering.
Playbook: !prd-to-tickets For a PRD: 1. Read the PRD and extract goals, features, and constraints. 2. Investigate the codebase to understand the current architecture. 3. Break the project into independent work packages. 4. For each package, create a ticket with: - Description of the change and why it's needed - Acceptance criteria - Complexity estimate (S/M/L) - List of files likely to be modified - Dependencies on other tickets 5. Order tickets by implementation sequence. 6. Post the ticket breakdown as a summary.
Add a Knowledge entry for your ticket template: 'All engineering tickets must include Description, Acceptance Criteria, Technical Notes, and T-shirt size.' Opulent applies it to every ticket it creates.
Point Opulent at the PRD
Send the Notion URL with the project name and the Linear project or team. Opulent reads the PRD, searches the codebase for relevant files, and drafts the ticket breakdown.
The more specific the prompt, the better the tickets. Name the Linear project, any architectural constraints, and the order you want the work to happen.
Prompt: Read the PRD at https://notion.so/yourteam/user-profiles-v2-abc123. Investigate our codebase to understand the current user profile architecture. Break this into independent work packages. For each package, create a Linear ticket in the "User Profiles V2" project with: - Description and why it's needed - Acceptance criteria - Complexity estimate (S/M/L) - Files likely to be modified - Dependencies Order by implementation sequence.
Review the ticket breakdown
Opulent creates a set of Linear tickets with concrete descriptions, acceptance criteria, and file paths. The summary shows the order and dependencies so the team can see the critical path before starting work.
Review each ticket. If one is too broad, ask Opulent to split it. If a dependency is wrong, update the order. The goal is a backlog the team can start executing without re-scoping.
Ticket breakdown: | Ticket | Title | Size | Dependencies | |--------|--------------------------------------|------|--------------| | UP-101 | Add avatar upload endpoint | S | None | | UP-102 | Create profile settings page | M | None | | UP-103 | Migrate users table for bio/social | M | None | | UP-104 | Build profile preview card | S | UP-103 | | UP-105 | Add public/private visibility toggle | M | UP-103 | | UP-106 | Index new profile fields in search | L | UP-103 | All tickets created in Linear with acceptance criteria and file paths.
Kick off implementation
Once the tickets are approved, assign them to Opulent or the team. Add an !implement label to trigger a run that writes the code and opens a PR for each ticket. The PR references the Linear ticket and the acceptance criteria.
Sharpen the PRD-to-ticket loop
When a ticket format does not work well, update the playbook or the Knowledge entry. When Opulent scopes something wrong, write the correction into memory (the notes a run recalls next time) so the next PRD produces better tickets.
The natural chain: once tickets are created, use Bulk-Plan Your Ticket Backlog to score and sequence the sprint; for implementation, use Implement Bookings API from OpenAPI Spec or Figma to Pixel-Perfect Code depending on the work type.