Figma Specs is a markdown document on the canvas. Open beta, rolling out over a few weeks to Professional, Organization, Enterprise, Education, and Government. View access is enough to read one. You need edit access to write one. You can place it next to frames in a Design file, start a spec from the file browser, or fold a FigJam critique into one.

An agent can draft a spec from outside context, including a codebase, through MCP. You can turn a spec into a code layer. Using the agent on a spec spends AI credits. Hover the receipt after a prompt and you can see the cost.

I have watched this fail

The frame says what it looks like. A page in another tool says what it must do. Engineering opens one. The agent sees whichever one you attached. A spec that points at the frame, the constraint, and the code is the first artifact both sides can share.

Keep it short enough that a person will still read it. The agent will. Your reviewer might not. One live decision, moved out of a side doc and onto the canvas beside the frame, is enough to learn whether your team will actually maintain it.

I checked the Figma release notes and the Config India 2026 help article on 18 Oct 2026. Plans, betas, and the 4 Nov credit window come from those pages. If your admin console disagrees, trust the console.