docs(skills): whats-next adopts pql 1.11.0 --fields projection (FR-1 landed)

ticket list now omits description by default (D-27 upstream); batch
selection uses --fields id,type,parent_id,priority,status,title — the
238KB phase-subtree dump is now 23KB, no output spill.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

.claude/skills/whats-next/SKILL.md

@@ -44,20 +44,21 @@ 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 --status in_progress
+pql ticket list --under T-745 --status in_progress --fields id,type,status,title
 ```
 
-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.)
+The phase epic is the `"type": "epic"` row. Use pql natively — no ad-hoc python/jq
+projections over its output: since pql 1.11.0, `ticket list` omits `description` by
+default and supports `--fields id,type,parent_id,priority,status,title` (the batch-
+selection projection) and `--oneline`; `--full` opts back into whole rows when you
+genuinely need bodies.
 
 Then list its ready subtree — `--under` gathers the whole phase, `--unblocked` does the
 dependency walk (only tickets whose blockers are all `done`/`cancelled`):
 
 ```bash
-pql ticket list --under <active-phase-epic> --unblocked   # e.g. T-750 for Phase 4
+pql ticket list --under <active-phase-epic> --unblocked \
+  --fields id,type,parent_id,priority,status,title   # e.g. T-750 for Phase 4
 ```
 
 If this is empty, the phase is either complete or fully in progress — tell the user and stop.