From Jira to PR: How we built agent-driven pipelines for design system changes

Design system work follows a well-defined loop: read the ticket, check the Figma spec, find the right component primitives, apply the right tokens, write the Storybook stories, run the tests, open the PR. The steps are consistent enough that when we looked at our design system backlog, we didn’t just see a list of tasks; we saw a set of instructions waiting to be executed. So we set an agent loose on the loop.