Issue triage & routing

On the schedule you choose, the agent classifies and dedupes incoming issues, verifies the actionable ones, proposes labels and routing under explicit rules, and drafts a triage summary for you to approve before anything is applied.

Saves you ~2.2 h / week

Start with this playbook

How it works

Trigger
On the “Triage issues” schedule.
Job
Classify and dedupe, verify the actionable ones, then draft a triage summary for approval.
Outcome
An evidence-backed issue queue with proposed labels, routing, and next actions.

What it installs

Agents 2

  • Triage Agent

    Triages incoming issues against a state machine and drafts a triage summary.

  • Issue triage & routing Quality Reviewer

    Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Teams 1

  • Issue triage & routing quality team

    The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.

Workflows 1

  • Triage issues

    Classify and dedupe, verify the actionable ones, then draft a triage summary for approval.

Goals 1

  • Issues triaged daily

    Incoming issues are classified, deduped, verified, and labelled without backlog. Success looks like: Each run lands an approved triage summary that classifies every new issue, links duplicates, and proposes label and routing updates — leaving no untriaged backlog.

Skills 3

  • triage-frontend-issues

    Archive non-actionable noise from the issue queue safely: archive-only, always with a stated reason, weigh stack-frame and title signals, and when in doubt skip and flag for a human. Adapted from getsentry/skills/triage-frontend-issues.

  • github-triage

    Move issues and external PRs through a triage state machine: gather context, check for duplicates and prior rejection, recommend a category and state, verify the claim, and write a durable, agent-ready brief. Adapted from mattpocock/skills/triage.

  • triage-issue

    Break a thick report into independently-grabbable issues using thin vertical slices, each with a durable description, acceptance criteria, and honest blocking order. Adapted from mattpocock/skills/to-issues.

Schedules 1

  • Triage issues

    Triages incoming issues on the schedule you choose. ## Professional quality control Objective: complete the recurring Issue triage & routing operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Inspect the repository and actual diff, reproduce the behavior, run the declared tests and checks, cover known success and error paths, and verify security, performance, migration, and rollback implications where relevant. Never infer a passing command. Technical prose must cite command output and avoid generic AI phrasing or claims that the code does not prove. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

Requirements

  • Connected repository — Needs a connected code repository so the agent can read the incoming issue queue, check the codebase for context and duplicates, and propose label updates.

Setup guide

How to Triage Issues With an Agent

A practical guide to classifying, deduplicating, verifying, routing, and approving issue-triage updates.

Read the setup guide

Don't see your workflow? Describe it.

A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.

* What keeps taking time you don't have? *

Takes a minute · no account needed