jpmschweitzer/clide
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix whats-next: pql ticket --status is single-valued

Browse Source 
Dogfooding the skill surfaced it: `--status backlog,ready` is not a comma
list — it matches nothing and silently returns [], which would make batch
selection lie. Use a single `--status backlog` and note the `--unblocked`
filter still surfaces prose-"blocked on upstream" tickets (e.g. T-158).

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
jpmschweitzer
2026-05-31 13:12:47 +02:00
co-authored by Claude
parent 08b88bc841
commit 968686c4c8
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/skills/whats-next/SKILL.md
+8 -2
View File
@@ -68,12 +68,18 @@ Don't walk blockers per ticket — pql does it. Compose the `list` filters
structure/blocker-state only and would otherwise include `done` leaves):
```bash
pql ticket list --under <epic-id> --leaf --unblocked --status backlog,ready --pretty
pql ticket list --under <epic-id> --leaf --unblocked --status backlog --pretty
```
`--status` takes a SINGLE value (not a comma list — `backlog,ready` matches
nothing and silently returns `[]`). The repo is almost all `backlog`; if a
team uses `ready`, run it a second time with `--status ready`.
That returns exactly the actionable, unblocked leaves under the epic — the
multi-result complement to `pql plan whatsnext` (which now also skips blocked
tickets, for the single best pick).
tickets, for the single best pick). Note `--unblocked` only means no *ticket*
blocker is open; a ticket "blocked on upstream" in prose (e.g. T-158) still
shows — read the description before batching.
### 1d. Rank and group