Skip to content
Weavz
Menu

Turn selected Figma frames into a product brief

Give the agent a specific file and the node IDs that matter. It can read and render those nodes, then prepare a brief. File comments are read at file scope and must be checked for relevance. It does not inspect every screen automatically or write into a native Figma canvas.

For a product manager or designer preparing a handoff from a selected Figma flow.

What needs to be in place

  • In My apps, add Figma and connect the account you want to use. Figma is separate; the Product Ops Hub template includes Notion and Linear, not Figma.
  • The Figma file key and explicit node IDs for the frames to include. Choose a Notion parent page or Linear team only if you later want to create records.

In My apps, add the apps listed above and connect the accounts you want your AI client to use. Then connect your AI client to Weavz. A workspace template is optional: it can configure app access and defaults, but your AI client runs the task.

Work through the selected sources

The exact actions available depend on the integrations and actions enabled in the workspace. These steps keep the task bounded to the account and records you selected.

  1. Select the source frames

    Copy the file key and node IDs for the frames in scope. The task does not crawl a whole Figma project or infer which frames form a flow.

  2. Read the selected context

    Retrieve and render those nodes, then read file-level comments. Include a comment only when its text or reference clearly relates to the selected frames.

  3. Draft the brief

    Describe the screens, visible copy, interactions, and edge cases supported by the selected material. Mark missing states and assumptions as questions.

  4. Review before saving

    Keep the brief in the AI client first. If you choose to save it to Notion or create Linear issues, review the exact content and destination before that separate write.

App actions and developer details

Action names and inputs

These details help when configuring or implementing the task. You can follow the guide without starting from the action identifiers.

  • figma.get_file_nodes

    Read selected Figma nodes by file key and node IDs.

    Required inputs: fileKeyids

  • figma.list_comments

    Read comments from the specified file.

    Required inputs: fileKey

  • figma.render_images

    Render the specified nodes for visual inspection.

    Required inputs: fileKeyids

  • notion.createPage

    Optional: create a child page under a parent you select after reviewing the draft.

    Required inputs: pageId

  • linear.create_issue

    Optional: create an issue only after you approve its title, description, and team.

    Required inputs: teamtitle

A starting instruction for your AI client

Replace bracketed details with the records and scope you chose. Review the returned result against its sources.

Example instruction

Read Figma file [file key] and only these node IDs: [node IDs]. Render those nodes and retrieve the file comments. Include a comment only when it clearly relates to the selected frames; mark file-level comments with no clear frame reference as broader context. Draft a product brief with one section per selected frame, visible copy, interactions supported by the design, edge cases, and unanswered questions. Do not claim unselected frames were reviewed. Return the draft here. Do not write to Figma, Notion, or Linear unless I review the exact proposed content and give a separate instruction.

What the result contains

A frame-by-frame brief with file and node identifiers, visible evidence, and questions separated from inferred behavior.

Keep the source trail with it

Retain the Figma file key, selected node IDs, and version when provided so a reviewer can open the exact frames. Distinguish file-level comments from comments tied to a selected frame.

Keep drafts and writes separate

Figma operations here are REST reads. The workflow does not provide native canvas editing or CodeConnect behavior. Notion page creation and Linear issue creation are optional, separately reviewed writes.

If a source or connection is missing

If a node is missing or a render fails, ask for a valid node ID or use the returned node data without claiming an image review. If comments are unavailable, mark that source as unavailable rather than filling the gap.

Optional workspace template: Product Ops Hub.

Integrations

  • Figma

    Read and render selected nodes. Comments are retrieved at file scope and checked for relevance.

  • Notion

    Optionally save the reviewed brief to a selected parent page.

  • Linear

    Optionally draft issues after the brief is checked.

Solution

AI assistants

How this task fits a broader app-access workflow.

Industry

SaaS and AI products

Related workflows by team and operating context.

Includes Notion and Linear for optional handoff records. Add Figma as a separate workspace integration before using the selected-frame read workflow.