Figma introduced Specs in its October 15, 2026 release notes, giving teams a place for written product context beside designs, diagrams and code layers. The feature is rolling out in open beta. Its practical appeal is proximity: a decision can sit alongside the work it describes, where collaborators can inspect both.
A document on the canvas
Teams can create a standalone Spec file or insert one into Figma Design or FigJam. The Specs guide describes an editor with headings, lists, code blocks, comments and other document elements. Figma’s launch article says teams can also drag an existing Markdown file onto the canvas and embed a frame, canvas node or FigJam material in a Spec.
That makes Specs relevant to a common handoff problem. Requirements, visual exploration and implementation notes often live in different places; a Spec can bring references into the same collaborative workspace. It does not, by itself, establish that those references are complete or current. Teams still need to maintain decisions as designs and code change.
What connected agents can use
Figma says agents connected through its MCP server can read, create and update Specs. Its launch article describes sharing a Spec link with a coding agent so the agent can use the document and its references as context. This is a way to supply material to an agent, not a guarantee that generated code matches a design or meets a product requirement. A working MCP connection, appropriate access and human review remain important.
Figma also distinguishes direct editing from AI-assisted work. The Help Center says writing or editing a Spec without the agent does not use AI credits. Using the agent with Specs does, and consumption varies with the task and the context supplied.
Availability remains uneven
Figma describes Specs as a gradual open-beta rollout. Its release notes call it a rollout on paid plans, while the Config India Help Center page also lists Education and Government access. Figma warns that team members may gain access at different times. Before building a workflow around Specs, teams should check availability, file permissions and AI-credit terms in their own account.
The immediate change is a new place to keep and transmit product context. Whether that produces a better handoff depends on the quality of the Spec, the references it carries and how the resulting work is checked.
