What problem does it solve? Incoming bug reports and feature requests often arrive vague, unverified, or misframed, and acting on them directly wastes effort on bugs that never reproduce or specs built on a reporter's guess. This Skill moves each item through a lightweight state machine — categorize, verify the claim actually holds, then write a durable agent-ready brief — so nothing gets built before it is confirmed real. ## Core Features & Use Cases - Categorize and verify before acting: Classify each item as bug or enhancement, run one lightweight reproduction to confirm the claim, and route it to states like needs-info, ready-for-agent, ready-for-human, or wontfix. - Agent-ready brief writing: Produce behavioral, durable specs with verified current behavior, desired behavior, key interfaces, independently testable acceptance criteria, and explicit out-of-scope lines that an AFK agent can build from cold. - Solo and tracker modes: Default to a lightweight local-list flow for solo backlogs, mode-switching up to GitHub labels, external PR discovery, and an out-of-scope dedup knowledge base only when a shared tracker exists. - Use Case: A beta tester texts "the app is broken, I can't book anything." Instead of writing "fix the booking error," you reproduce the issue, discover it only fails when a slot is taken between selection and confirm, and hand off a scoped, testable brief. ## Quick Start Triage this bug report from my beta backlog: verify whether it actually reproduces, then write an agent-ready brief for it.
