What it does
- Reads the last seven days of Front conversations tagged as bug, feedback, or feature request and skims the actual customer messages.
- Clusters the recurring themes and ranks them by how many separate conversations support each one.
- Files a Linear issue for every top theme, complete with quoted customer language and links back to the original Front conversations.
- Posts a ranked rollup to your #product Slack channel every Monday at 9am so the team starts the week with real customer signal.
The prompt
Paste it into a new chat in General Input, and a specialist builds it with you.
Every Monday at 9am, roll up the last seven days of Front conversations into a set of Linear issues that capture recurring product themes, and post the rollup as a digest in our #product Slack channel.
Trigger: cron, weekly, Mondays at 9am in the org's local timezone.
Step 1. Pull the raw material from Front. Call Front's List Tags to fetch every tag the token can see, then identify the tags that mean bug, feedback, or feature request (default names to look for: bug, feedback, feature-request, but let me override the list). For each of those tags, call List Tagged Conversations and keep only conversations updated in the last 7 days. For each of those conversations, call List Conversation Messages and read the inbound (customer-authored) messages. Ignore outbound replies from teammates and internal comments.
Step 2. Cluster the customer messages into recurring themes. Group by the underlying issue people are describing, not by keyword or tag. Rank themes by the number of distinct supporting Front conversations. Drop any theme with fewer than 3 supporting conversations so we don't file noise.
Step 3. For each remaining theme, use Linear's Create Issue to file an issue in our product team. Each issue should have: a plain-language title that names the pattern; a description that summarizes the theme in a paragraph, then quotes the top 3 most representative customer snippets verbatim (with a light attribution like the requester's company or first name); and a footer that lists the count of supporting conversations. Then, for every supporting Front conversation, call Linear's Add Link to Issue once with the Front conversation URL so the product team can click straight back to the source thread.
Step 4. Post the digest to Slack using Send a Message in the #product channel. The message should list every top theme in ranked order (most supporting conversations first). For each theme include: the theme title, a one-line summary, the count of supporting conversations, and a link to the newly created Linear issue. Keep the tone factual and skimmable, not editorial.
Edge cases: if the week has zero qualifying themes (nothing hit the 3-conversation threshold), skip Linear entirely and post a short 'no recurring themes this week' note to Slack with the raw tagged-conversation count so the team still knows the job ran. If Front returns a merged conversation redirect, follow it and use the merged conversation. Respect Front's rate limits when paging.
What you'll need
- A Front account with tags for bugs, feedback, and feature requests (or whatever tag names your team already uses).
- A Linear workspace and a team where the agent can create issues.
- A Slack workspace and a channel like #product for the weekly digest.
Make it yours
- Change which Front tags count as feedback, or shift the window from weekly to biweekly, monthly, or daily.
- Raise or lower the minimum number of supporting conversations before a theme becomes a Linear issue (three by default).
- Send the digest to a different Slack channel, cross-post to multiple channels, or route issues to a specific Linear team or project.