Context & docs
The distance between "add a filter to the results list" and a story someone can start is usually the design. Connect Figma, pin up to five files, and Spectr reads them every time it drafts - including screenshots of the relevant screens, which go to the model as real images. Stories come back describing your actual layout, states and components instead of guessing at them.
How Figma fits in
A call is imported from a note-taker (Fathom, Granola, Read.ai, or Fireflies.ai). Spectr picks out a requirement, a bug, an action item and an out-of-scope ask, reads Figma, Notion, and GitHub for context, and drafts a story and a bug with acceptance criteria. A person approves both, they are published to the team's tracker (Jira, Linear, or Shortcut), and the requirements, scope log and project memory update from the same call.
OAuth with granular read-only scopes - file content, file metadata, and your user profile. Spectr never writes to a Figma file.
View access to the files you want pinned - up to five per project. Any Figma account that can open a file can authorise access to it.
In the Spectr project, go to Integrations.
Choose Figma and click Connect, then authorise on Figma.
Paste the URL of each file you want pinned - up to five. Spectr validates each one and stores its name.
Generate a spec sheet. Figma screenshots appear in the context the model was given.
Anything else? Email hello@crowdlinker.com and a person will answer.
No. The connection is read-only by scope - Spectr can read file content and metadata and nothing else.
No. Spectr uses Figma's standard OAuth scopes; any account that can view the file can authorise access to it.
Up to 15 per run, within an 8MB image budget. Each one is labelled with its screen, which is how a generated story can link straight to the design it describes.
Use case
Draft stories with real acceptance criteria, then approve, edit or reject each one
Fathom
Granola
Read.ai
Fireflies.ai
Card controls PRD
bank/mobile
Jira
Linear
Shortcut