What problem does it solve? Incoming Slack issue reports pile up without consistent classification, causing duplicate tracker tickets, misrouted bugs, and noisy channel replies. This Skill triages each report with evidence review, cause tracing, dedupe, and a single thread-only verdict. ## Core Features & Use Cases - Evidence-based classification: Reads the full Slack thread, attachments, logs, and screenshots, then classifies the report as bug, performance, feature request, question, or reroute. - Tracker dedupe and fail-closed creation: Searches the configured issue tracker (Linear, GitHub Issues, or another adapter) for duplicates before creating a self-contained ticket linked to the source thread. - Cause-aware routing: Traces the likely code path before assigning an owner, using a configurable routing map with strict ping policies. - Use Case: A scheduled automation scans a feedback Slack channel; for each new report it verifies the thread, dedupes against the tracker, files a ticket only for confirmed new bugs, and posts one marker-tagged verdict in the original thread. ## Quick Start Configure the Benny triage automation with a source channel and tracker adapter, then let it triage each incoming Slack issue report automatically.
