Figma Specs Makes Markdown a Shared Canvas Object, and That Is Overdue

Figma announced Specs on 15 October: a multiplayer container for written context that lives on the canvas. You can drag any .md file onto the canvas to turn it into a spec, then embed a FigJam file, a frame or any node beside the text.

The pitch is that Markdown has become the default way to give agents context, but the files sit on one person's laptop with brittle links to the work they came from. Specs puts them next to the designs, lets people comment, and lets Figma's agent reply to those comments directly. Figma's MCP server then sends the finished spec to a coding agent.

We like the idea more than the novelty. Written intent next to visuals is how good briefs already work, and screenshots in a document go stale the moment a frame changes. Embedding the live frame fixes that.

The test will be discipline. A spec that nobody prunes is just a longer wiki page. If you try it, keep one spec per decision, link frames instead of pasting images, and write down what is out of scope. Agents follow instructions literally, so vague specs produce vague builds.