Skip to main content

​
How the flow works

Everything in Lyse follows the same pattern: Source, AI, Review, Publish.
1

Capture

A discussion reaches a conclusion in Slack. A designer publishes library updates in Figma. These are the moments where tasks are born—but usually lost.
2

Analyze

Lyse reads the conversation or detects the design change. It extracts what matters: the problem, the context, the action needed. A draft task is created automatically.
3

Review (optional)

Every generated task lands in your Lyse inbox first. Check the summary, edit if needed, add labels or assignees. You decide what’s worth publishing.On Pro and higher plans, you can skip this step entirely—tasks go straight to your issue tracker automatically.
4

Publish

One click from your inbox, or automatic if you’ve enabled direct publishing. The task appears in Linear, GitHub, Jira, or GitLab—with full context. Your team knows what to do without asking “what changed?”
You’re always in control. Review everything manually, or trust Lyse to publish automatically—your choice.

​
Sources where tasks come from

Lyse watches two sources for task-worthy content.

​
Slack

When you mention @Lyse in a Slack thread, it reads the entire conversation and extracts what matters. Notification Dark How it works
  1. A discussion happens in Slack—a bug report, feature idea, or decision
  2. You mention @Lyse (optionally with instructions like @Lyse create a bug ticket)
  3. Lyse analyzes the thread and identifies the key information
  4. A task appears in your inbox, ready to review
What Lyse extracts
  • Bug descriptions with reproduction steps
  • Feature requests with context
  • Decisions and action items
  • Technical requirements mentioned in discussion
Example
Your team debates a UI issue for 15 messages. Instead of summarizing it yourself, mention @Lyse create a bug task. Lyse reads the thread, extracts the problem description, identifies who reported it, and creates a formatted ticket—all in seconds.

​
Figma

When you publish a Figma library, Lyse detects what changed and generates tasks automatically. Figma Library Publish How it works
  1. You make changes to components in your Figma library
  2. You publish the library in Figma
  3. Lyse receives a notification
  4. Lyse analyzes what changed and generates a summary
  5. A task appears in your inbox for each change
What Lyse detects
  • Component updates (properties, colors, spacing, typography, variants)
  • New components added to the library
  • Components deleted from the library
Example
You update the padding on your Button component from layout-padding-md to layout-padding-sm and publish. Lyse creates a task: “Button padding reduced. Developers should update the padding value and verify layouts.”

​
Review before publish

The Reviewer is where all generated tasks land before reaching your team. Think of it as a quality gate. Hero Light What you see for each task
  • The source (which Slack workspace or Figma file)
  • The AI-generated title and description
  • A preview of how it will look in your issue tracker
What you can do
  • Check the AI-generated content before publishing
  • Copy the title or description if you want to paste it elsewhere or adjust it manually
  • Publish to send it directly to your issue tracker
  • Dismiss if the change doesn’t need a task
  • Batch publish multiple tasks at once for routine updates
The inbox keeps you in control while eliminating the manual work of writing tasks.

​
Where tasks are sent

Once you approve a task, Lyse publishes it to your connected issue tracker. Supported destinations
  • Linear — Create issues in any team, with labels and project linking
  • GitHub — Create issues in any repository
  • Jira — Create tickets in any project
  • GitLab — Create issues in any project
You can connect multiple destinations. For example, design token changes to Linear and component updates to GitHub.
What gets published
  • Title (AI-generated)
  • Description with full context
  • Project/team (configurable in integration settings)
Coming soon: Auto mode will automatically assign tasks, apply labels, and select the right project/team based on the task context and your workspace structure.

​
How Lyse understands context

Lyse uses AI to analyze content and generate useful task descriptions. For Slack threads
  • Reads the full conversation history
  • Identifies the main topic and any action items
  • Extracts relevant details (error messages, user reports, decisions)
  • Formats everything into a clear task structure
For Figma changes
  • Compares the published version to the previous state
  • Identifies what properties changed
  • Translates design changes into developer-friendly language
  • Suggests what developers should check or update
The AI summaries are designed to give developers actionable context—not just “Button changed” but “Button padding reduced, check layouts.”

​
Example workflow

Here’s a typical workflow combining both sources:
1

Monday

Your design system lead updates several components in Figma and publishes. Lyse generates 8 tasks. They review, dismiss 2 minor changes, and publish 6. Those 6 tasks land in Linear.
2

Tuesday

A PM discusses a bug with engineering in Slack. 20 messages later, they have a clear understanding. The PM mentions @Lyse create a bug task. The task appears in their inbox, they add a priority label, and approve. It’s in Jira 10 seconds later.
3

The result

No context lost. No manual copy-pasting. Tasks flow from where work happens to where work is tracked.

​
Learn more

Connect your issue tracker to publish tasks.

Linear

Publish tasks to Linear

Jira

Publish tasks to Jira

Github

Publish tasks to GitHub

Gitlab

Publish tasks to GitLa