What problem does it solve? Product leads and non-technical stakeholders cannot read a raw GitHub backlog: it mixes internal engineering chores with real user-facing bugs and is written in jargon. This Skill turns the live issue backlog into a short, plain-language briefing of what is actually broken for users, plus a self-contained HTML report with status grouping. ## Core Features & Use Cases - Backlog triage and translation: Pulls the most recently active open issues via the GitHub CLI, filters out internal test, infra, and feature work, and rewrites surviving items as user-facing symptoms. - Dual-output rendering: A bundled Python script renders one JSON synthesis into both an inline chat briefing and a styled HTML report with status tiles, a by-status view, and expandable detail per item. - Self-audit loop: A shell script checks the rendered report for mechanical failures (external assets, oversized pages, missing issue links, sideways scroll) and captures light, dark, narrow, and by-status screenshots for visual review. - Use Case: A founder asks "what are users complaining about right now?" The Skill fetches the latest backlog activity, curates at most 10 felt problems, and delivers a ranked briefing plus a shareable visual report. ## Quick Start Ask the assistant to summarize what is currently broken for users in the app and produce a bug report from the GitHub backlog.