What problem does it solve? Teams running GitHub issue backlogs lose track of stale issues, file duplicates from automated signals like Sentry, and drift their label taxonomies across repos. This Skill centralizes board snapshots, backlog reads, stale-issue detection, and gated issue creation into one consistent set of gh + GraphQL operations. ## Core Features & Use Cases - Board and backlog reads: Snapshot a ProjectV2 board grouped by status column, read label-driven backlogs, and pull a fill/drain work queue with parsed touches/depends-on/stack contracts. - Stale-issue detection: Find shipped-but-still-open issues, stub bodies needing scoping, and completed tracking epics, with explicit degraded-run signaling instead of silent empty results. - Dedupe-then-file writes: Create issues idempotently using a body-marker convention with a two-stage search plus recent-scan lookup, preview-then-confirm dry runs, and a burst rail that halts runs filing more than five issues. - Label-state transitions: Claim, release, block, promote, and demote issues against the ready/in-progress/blocked taxonomy, with double-pick guards and claim-residue cleanup. - Use Case: A Sentry escalation needs filing: run the file script with a stable marker in dry-run mode, preview the would-file result, then file once approved — re-runs return the existing issue instead of a duplicate. ## Quick Start Ask the agent to snapshot the project board by status and list any stale or stub issues in this repository.
