From bc5043feb2155b6d426a0195adf39904d02b2fe0 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Tue, 7 Jul 2026 22:51:19 +0200 Subject: [PATCH] fix(skills): whats-next 1b uses native pql --status filter, no python one-liner MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Ad-hoc projections over pql output are the wrong layer — the compact-list gap is filed upstream (pql FR-1, --fields projection). Until it lands, use narrow pql invocations and Read spilled output files. Co-Authored-By: Claude Fable 5 --- .claude/skills/whats-next/SKILL.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/.claude/skills/whats-next/SKILL.md b/.claude/skills/whats-next/SKILL.md index 87c435a42..b686f5f7a 100644 --- a/.claude/skills/whats-next/SKILL.md +++ b/.claude/skills/whats-next/SKILL.md @@ -44,10 +44,15 @@ under T-745; the cascade is strictly sequential per D-166, so equivalently the lowest-numbered non-`done` phase epic): ```bash -pql ticket list --under T-745 2>/dev/null | \ - python3 -c "import json,sys;[print(t['id']) for t in json.load(sys.stdin) if t['type']=='epic' and t['status']=='in_progress']" +pql ticket list --under T-745 --status in_progress ``` +The result is small (the initiative, the active phase epic, plus any active batch +tickets); the phase epic is the `"type": "epic"` row. Use pql natively — no ad-hoc +python/jq projections over its output. (A `--fields` projection flag is on file +upstream as pql FR-1 for the large-list case; until it lands, Read the spilled +output file when a full-subtree dump is genuinely needed.) + Then list its ready subtree — `--under` gathers the whole phase, `--unblocked` does the dependency walk (only tickets whose blockers are all `done`/`cancelled`):