See which Figma designs never made it into engineering
A board that lists every screen across your Figma projects, shows which ones have a Linear ticket, and flags designs that changed after handoff.
Figma
LinearProductEngineeringData SyncContent GenerationBuild me a design to dev handoff coverage board: an app that shows me, across a whole Figma project, which screens have actually made it into engineering and which have quietly fallen through the gap. The point of the app is the gap view, so lead with coverage and treat ticket creation as the follow up action, not the headline.
Setup and file list. On first use I paste the link to my Figma team page, since team IDs cannot be discovered through the API and have to be read out of that URL. Use Get Team Projects to list the team's projects, let me pick which ones the board covers, and remember that selection. For each selected project, use Get Project Files to list the files and Get File Metadata for the name, thumbnail, and last modified time. Only Figma Design files work with these operations, so show FigJam and Slides files greyed out and labelled unsupported rather than erroring on them or dropping them silently.
Inside a file. Opening a file loads its top level frames, meaning the direct children of each page, using Get File for the initial load and Get File Nodes for targeted refreshes of individual frames. Show each frame as a card with a rendered preview from Render Images of File Nodes. Node IDs in Figma URLs use hyphens but the API expects colons, so convert before requesting. Rendered image URLs expire after 30 days, so re-render on demand instead of storing those URLs permanently.
The columns. Sort frame cards into four columns: no ticket yet, linked, in progress, and done. Compute the column from real data, never from something I maintain by hand. For each frame, read the dev resource links attached to it with Get Dev Resources. A frame with no Linear link sits in no ticket yet. A frame with a Linear link gets matched against my issues using List Issues, with Get Issue for detail, and the card is placed by that issue's actual Linear workflow state: unstarted states map to linked, started states to in progress, and completed or cancelled states to done. Show per column counts and an overall coverage percentage at the top of the file view, and let me filter the board by file and by drift.
Create handoff ticket button, backed by an embedded background agent. Every frame in the no ticket yet column has a Create handoff ticket button. Clicking it kicks off a background agent that reads the frame's node JSON with Get File Nodes, renders a preview image with Render Images of File Nodes, drafts a developer ready spec covering layout, spacing, interaction states, and the library components used, creates the Linear issue with Create Issue, attaches the resulting issue URL back onto that same frame as a dev resource with Create Dev Resources, and posts a Figma comment on the frame with Post Comment so designers see the handoff in canvas. Show the agent's progress on the card and move the card into the linked column when it finishes. Dev resources are capped at 10 per node and Create Dev Resources is a bulk call, so batch the writes when I hand off several frames at once.
Drift detection. For every frame that already has a ticket, compare the file's latest version timestamp from Get File Versions, along with the last modified time from Get File Metadata, against when the linked Linear issue was created. If the design is newer than the ticket, put a design changed since handoff badge on the card and surface a drift count alongside the coverage number. Each flagged card gets a repair action: update the stale link with Update Dev Resources, or reopen the Linear issue with Update Issue so engineering knows to re-read the spec.
Persistence and audience. Remember my project selection and let me mark individual frames as not tracked, so screens we deliberately never intend to build drop out of the gap count and the coverage number stays meaningful. Design leads and engineering managers use this during planning, so make the board fast to scan: coverage and drift numbers first, the no ticket yet column first, and previews large enough to recognize a screen without opening Figma.
What does this prompt do?
- Lists every design file in the Figma projects you pick, and every top level screen inside a file, each with a rendered preview so you can recognize it at a glance.
- Sorts those screens into columns by handoff state: no ticket yet, linked, in progress, and done, with the column driven by the real status of the matching Linear issue instead of a list you maintain by hand.
- Puts a Create handoff ticket button on every screen that has no ticket, which hands off to a background agent that writes the developer spec, opens the Linear issue, links it back onto the frame, and leaves a comment in Figma for the designer.
- Flags a design changed since handoff badge when a file was edited after its ticket was created, with a one click repair to refresh the stale link or reopen the issue.
What do I need to use this?
- A Figma account with access to the team whose projects you want to track
- A Linear workspace where handoff tickets should be created
- The link to your Figma team page, so the board knows which projects to pull in
How can I customize it?
- Choose which projects appear on the board, and hide files or screens you never intend to build.
- Set which Linear team new tickets land in, along with the default priority and assignee.
- Map your own Linear workflow states onto the four columns, so in progress and done match how your team actually works.
- Adjust how much detail the spec agent writes about layout, spacing, states, and library components.
FAQs
Does this change my Figma designs?
Does it file tickets automatically?
Will this work with FigJam boards or Figma Slides?
What about screens we decided not to build?
How does it know a design changed after handoff?
Do I need a paid Figma or Linear plan?
Related templates
Open one board each morning, see which voice calls went badly, replay the exact moment the caller got frustrated, and file the fix.
See every customer waiting on a bug fix, file the ticket without creating a duplicate, and tell them the moment engineering ships it.
See every recent deploy across all your Heroku apps in one timeline, then roll back, restart, or file an incident without leaving the screen.
Pick a date range, see which support topics are climbing fastest, read the real customer threads behind them, and file the worst ones as tickets.
See every Hacker News story and comment that mentions your product or your competitors, mark each one new, needs reply or handled, and stop losing threads.
One grid of every table you track, when it last landed, and what broke, with stale tables pinned to the top and an agent that explains why.
Stop guessing which designs engineering never saw.
Open one board that shows every screen in your Figma projects and exactly where it stands in Linear.