What problem does it solve? Maintainers of open-source or team projects face a constant stream of unstructured bug reports and feature requests. This Skill moves issues through a consistent triage workflow—classification, reproduction, clarification, and handoff—so every issue ends up with a clear category, state, and actionable specification instead of languishing unlabeled. ## Core Features & Use Cases - State machine triage: Moves issues through canonical roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) paired with bug or enhancement categories, with maintainer override support. - Agent brief generation: Produces durable, behavior-focused agent briefs with acceptance criteria so AFK agents can implement issues without re-reading stale discussion threads. - Out-of-scope knowledge base: Records rejected feature requests in .out-of-scope/ files and surfaces prior rejections when similar requests reappear, preventing re-litigation. - Use Case: A maintainer runs triage on a backlog of 30 unlabeled issues; the Skill buckets them by attention needed, reproduces reported bugs, grills reporters for missing detail, and posts ready-to-implement briefs on the actionable ones. ## Quick Start Ask the assistant to triage issue number 42 and recommend a category and state with reasoning.
