Triage that can answer “has anyone else asked for this?”
Give Linear triage the evidence behind the issue — directly when your setup supports external MCP, or through an evidence-backed ticket from Specky.
- Steps
- 5
- Tools
- 5
- Metrics
- 3
- Read
- 4 min
A team of nine shipping weekly, with an issue inbox that grows faster than anyone reads it and a triage rota nobody enjoys.
Composite blueprint. This is the loop and the wiring — assembled from workflows our early design partners run — not a single named customer’s audited results. Every number on this page is a metric to instrument, not a result we’re claiming.
What the week looked like
Triage was pattern-matching from memory. Whoever was on rota that week decided what mattered, and the answer changed with the person.
“Has anyone else asked for this?” was the most important question in the meeting and the one nobody could answer without twenty minutes of searching.
Duplicates got closed as duplicates only when the closer happened to remember the original. Otherwise they became parallel tickets.
Priority was set by who filed the issue, because that was the only signal reliably attached to it.
The agent answers the evidence question before a human opens the issue. Triage becomes a decision about trade-offs rather than an archaeology exercise.
The tools this loop runs on
Native connectors where they exist, and an honest label where they don't — anything else reaches Specky over MCP, the REST API, or an automation hop.
An optional consumer when the team’s Linear plan and agent client support external MCP sources.
Answers the query: how many distinct accounts have raised this, when, in what words, and what did we already decide about it.
Issues sync into the graph too, so a triage decision made today is evidence for the next one.
The channel where the request usually appeared first — often weeks before the issue was filed.
Support history, which is where most duplicate requests actually live.
How it actually runs
Every step is labelled by who does it. The steps marked 'you review' are the ones worth keeping human.
Choose the Linear handoff that is available to you
AutomaticIf your Linear workspace supports external MCP sources, add Specky’s endpoint and authenticate with a workspace API key. If it does not, keep the same evidence flow inside Specky and push the approved ticket through the native Linear integration.
An issue arrives and gets a second opinion
AgentTriage automation queries Specky before a human sees the issue: is this a known theme, how many accounts, what’s the sentiment trend, did we already decide against it and why.
The answer lands on the issue, not in someone’s head
AgentA comment with the count, the quotes, and a link to any prior decision. The next person to open this issue starts where the last one finished instead of re-deriving it.
You triage the trade-off
You reviewWith the evidence attached, the human call is priority against everything else — which is the part worth a person. Closing a duplicate now takes a glance rather than a search.
The decision becomes tomorrow’s evidence
AutomaticWhatever you decide syncs back as a node. Next month, when the same request arrives from a different account, the agent can say “we looked at this in August, here’s why we passed.”
The numbers to watch — not the ones we'd like to quote
We're not going to invent a percentage for you. These are the three metrics that tell you whether the loop is real, and how to compute each one from data the graph already holds.
Issues triaged with an evidence count attached
Every issue that touches customer-facing behaviour
Count issues carrying an agent comment with at least one cited node, over all triaged issues. Low means the agent isn’t being queried, not that the evidence is missing.
Duplicates caught at triage rather than after build
Rising, then flat once the graph is dense
Issues closed as duplicate within 24h of filing, over all duplicates eventually found. The late ones are the expensive ones.
Decisions re-litigated
Approaching zero
Count issues where the agent surfaced a prior decision on the same question. Every one is a meeting that didn’t need to happen twice.
Start here, not everywhere
Check the Linear path your workspace supports
Where external MCP sources are available, add Specky’s endpoint and use a workspace API key. Otherwise connect Linear natively in Specky and push the approved, evidence-backed ticket. Both paths are workspace-scoped and reviewable.
Start with one triage question
“How many distinct accounts have raised this?” Get that one answer landing reliably before you add sentiment, prior decisions, or anything else. A triage bot that comments too much gets muted.
Feed the graph before you query it
The agent can only count what’s in there. Connect the support desk and Slack first — those hold the duplicate requests that make the count meaningful.
https://www.specky.space/api/mcpClaude Code · Codex · Cursor · Claude Desktop · ChatGPT · n8n
Frequently asked questions
Does this replace Linear’s own triage features?+
No — it feeds them. Linear’s triage is good at routing, SLAs, and workflow; what it can’t do is tell you whether nine other customers already asked for the same thing, because that evidence lives in your support desk and call transcripts rather than in Linear. Specky answers that one question and Linear does the rest.
What if we use Jira instead of Linear?+
Jira has a native Specky connector, so issues sync both ways and the same evidence is queryable. The exact agent handoff depends on what your Jira or Linear setup supports; when external MCP is unavailable, the native connector still gives the team the same evidence with one more click.
Will the agent comment on every issue?+
Only if you configure it to, and you shouldn’t. Scope the automation to issues in the triage state or a specific label first. A bot that comments on everything gets muted within a week, and then the useful comments go unread too.
Run this loop on your own product.
One source, one agent, one approval gate. You’ll know inside a week whether it holds.
14-day free trial · No credit card required · Cancel anytime