I connected Figma, Claude, and Jira — and I don't open tickets by hand anymore.
I connected Figma, Claude, and Jira into a single workflow. The first run created 23 tickets in 4 minutes — with descriptions and acceptance criteria already written.
View on LinkedInAt the end of a sprint, mockups were ready — but the slowest part was still ahead. Manually translating design work into Jira: stories, tasks, subtasks, acceptance criteria, and developer notes. Repetitive work that added no value to the product.
The bottleneck
Every week, the same ritual. Designers finish the mockups. Someone opens Jira. Someone copies titles, writes descriptions from scratch, tries to capture what a comment in Figma actually meant. An hour gone, every time.
The worst hour of the week isn't designing. It's translating design into empty tickets.
What I built
I connected Figma, Claude, and Jira into a single workflow. Claude reads mockups and comments directly from Figma through MCP, analyzes structure, components, states, and interactions, then generates Epics, Stories, Tasks, and Subtasks organized by development logic.
The workflow runs in three steps:
- Claude reads the Figma file through MCP
- It understands components, states, and interactions
- It creates Jira work items autonomously — with descriptions and acceptance criteria
The result
The first run created 23 Jira tickets in 4 minutes. No copy-paste. Fewer interpretation gaps. Fewer meetings to explain what a comment in the mockup meant.
Takeaway
Design does not end in Figma. It ends when developers have everything they need to start building with clarity and context. If you're still doing handoff manually, you're leaving time on the table.
