On November 20, 2026, Figma introduced a workflow in its official blog: Specs, combined with the Figma agent, gathers context scattered across requirement documents, FigJam diagrams, design files, and code layers into a single implementation plan, which is then handed to a coding agent. Specs is currently in open beta, available on all plans, on web, desktop, and mobile.
How a plan gets made
The blog walks through the whole process using Pickup, a fictional food-delivery app. The engineer first notices the team has agreed on a "single-city pilot" but not on which city, so he asks the Figma agent to connect Hex, the team's analytics platform, and generate a spec breaking down usage and order volume by city, while updating the map code layer. The team picks Bengaluru, where demand is densest. He then selects the technical spec, annotated design frames, the interactive map code layer, and the design-system guidance together, and calls the team's preconfigured build-implementation-plan skill. The agent produces an implementation plan covering how the feature should look and behave, how the design system applies, testing and observability, rollout steps, and a task list. Before handoff, the engineer reviews the plan end to end, flags problems in comments, and the agent replies with fixes; where a designer needs to weigh in, he tags them in the spec, and they make the change in real time.
The final step is pasting the spec link into Codex: through Figma's MCP, Codex reads not only the spec but also the annotated designs, code layers, and design-system components behind it, and writes code against the same context.
The valuable step is the "plan" itself
What this workflow really changes is the division of labor: the coding agent no longer starts from scattered requirements, but from a plan a human has reviewed. The winners are teams where design and engineering collaborate closely — the more scattered the context, the greater the payoff from assembling the plan. But the boundary sits in the same place: Pickup is a fictional app, the skill has to be configured by the team in advance, and if a piece of context is missing from the canvas, the plan the agent assembles may miss it too. And no matter how complete the plan, the code still has to pass review and testing before it ships — that step cannot be skipped.
For Figma, Specs and the previously updated MCP Server are pushing the same idea further: design context is no longer just "pictures for people to look at," but material a coding agent can consume directly. See the related update in Figma Updates MCP Server: Get Design Context Anywhere, with Remote Access and Figma Make Support.
What to watch next is the feedback from the open beta: whether Specs will be priced, whether a skill ecosystem grows around it, and whether real teams running full projects with it actually see rework fall. The blog gives no timeline — the answers will have to wait for the next update.