Skip to main content
Changelogs document design system changes with dates, authors, and descriptions. Unlike other spec types, changelogs don’t require deep component analysis. You describe what changed and the agent formats it.

​
What you need

  • A description of what changed (for create/update) or a Figma link to an existing changelog (for convert/update)
  • Date and author information
You don’t need to worry about formatting. The agent rewrites your input for clarity, normalizes dates, and structures everything automatically.

​
Three modes

Create

Start a fresh changelog template and populate it with initial entries

Update

Add new entries to an existing changelog frame directly in Figma

Convert

Extract an existing Figma changelog into structured JSON

​
Create

Use @create-changelog when starting a new changelog for a component or library. Describe the changes in plain language. The agent structures and formats the output. 
@create-changelog

Start a changelog for the Button component. First entry:
- Date: Feb 10, 2026
- Author: ian.guisard
- Added loading state with spinner icon
- Changed disabled opacity from 0.4 to 0.38
Copy the JSON output and paste it into the Echo Specs plugin in Figma to generate the changelog template.

​
Update

Use @update-changelog to add entries to an existing changelog. Share a Figma link to the changelog frame and describe what changed. The agent writes directly to Figma. No JSON copy-paste needed. 
@update-changelog https://www.figma.com/design/abc123/Specs?node-id=500:600

Add a new entry:
- Date: Feb 10, 2026
- Author: ian.guisard
- Added Danger variant for destructive actions
Update mode requires the Desktop Bridge plugin running in Figma Desktop.

​
Convert

Use @convert-changelog to extract an existing Figma changelog into structured JSON. This works whether the changelog follows the Echo Specs template or uses a custom layout. 
@convert-changelog https://www.figma.com/design/abc123/Specs?node-id=500:600

Convert this existing changelog to JSON format.
Convert mode requires the Desktop Bridge plugin running in Figma Desktop.

​
Example prompts

@create-changelog

Create a new changelog for our design tokens library.
First entry:
- Date: February 10, 2026
- Author: ian.guisard
- Changes:
  1. Added Consumer theme tokens
  2. Updated communication colors for dark mode

​
Tips for better output

  • Be specific about token changes: include token names and before/after values when relevant. For example: “Changed button-disabled-opacity from 0.4 to 0.38”
  • Use arrow notation for value changes: the agent converts old -> new into proper formatting automatically
  • Group related changes: describe related updates together (e.g., all color token updates in one entry)
  • Include the author: mention the author name if you want attribution; otherwise the agent uses a placeholder
  • Keep descriptions concise: the agent rewrites for clarity, so focus on what changed rather than lengthy explanations