From 968686c4c8977d69848fb4fbea2e29dcae56a136 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Sun, 31 May 2026 13:12:47 +0200 Subject: [PATCH] fix whats-next: pql ticket --status is single-valued MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .claude/skills/whats-next/SKILL.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/.claude/skills/whats-next/SKILL.md b/.claude/skills/whats-next/SKILL.md index d711f988..136c570d 100644 --- a/.claude/skills/whats-next/SKILL.md +++ b/.claude/skills/whats-next/SKILL.md @@ -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 --leaf --unblocked --status backlog,ready --pretty +pql ticket list --under --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