backlog-prioritizelisted

# Backlog Prioritize — Suggested Issue Ordering This skill fetches all open `approved-for-grackle` issues, filters out ones that already have a PR, and outputs a suggested priority ordering with rationale. ``` REPO="nick-pape/grackle" ``` ## Step 1: Fetch All Approved Issues ```bash gh issue list -R $REPO --label "approved-for-grackle" --state open --limit 100 --json number,title,labels,body ``` ## Step 2: Find Issues That Already Have PRs Check for open PRs that reference these issues (via branch name or body): ```bash gh pr list -R $REPO --state open --limit 100 --json number,title,body,headRefName ``` Cross-reference: if a PR's body contains `Closes #<N>` / `Fixes #<N>`, or its branch name contains the issue number (e.g., `nick-pape/295-unified`), that issue is already in progress. Exclude it from the ordering. ## Step 3: Classify and Sort For each remaining issue, extract: - **Priority label**: `priority:critical` > `priority:high` > (unlabeled) > `priority:low` - **Type**: `bug` > `feature` > `refactor` (bugs first — they degrade existing functionality) - **Domain labels**: `orchestration`, `web`, `server`, `powerline`, `cli` - **Dependencies**: Read each issue body for references to other issues. If issue A mentions "depends on #B" or "requires #B first" or "after #B", A should come after B. Sort by: 1. Priority label (critical first) 2. Type (bugs before features before refactors) 3. Dependency ordering (blockers before dependents) 4. Issue number (older i