chore(skills): raise kanban WIP soft-limit 5 -> 10 (Jeroen, 2026-07-17 — sidequest track alongside the active batch)

2026-07-17 07:53:04 +02:00
parent 749ba49181
commit 38b989b226
1 changed files with 4 additions and 3 deletions
@@ -87,8 +87,9 @@ natural grouping exists, batch by the readiest related cluster.
 pql ticket list --status in_progress
 ```

-The kanban WIP soft-limit is 5; pql does not enforce it — warn if activating the batch
-would push in-progress past 5.
+The kanban WIP soft-limit is 10 (raised from 5 by Jeroen, 2026-07-17, to allow a
+sidequest track alongside the active batch); pql does not enforce it — warn if
+activating the batch would push in-progress past 10.

 ### 1e. Present the recommended batch

@@ -182,7 +183,7 @@ pql ticket status T-<id> in_progress

 For each ticket in the batch (batch with commas: `pql ticket status T-1,T-2 in_progress`).
 pql does **not** enforce the WIP limit — check it yourself in step 1d and warn if the
-batch pushes in-progress past 5.
+batch pushes in-progress past 10.

 > **Then make sure it persists.** Ticket mutations (status here, and any
 > `ticket append` in Step 2) land only in the gitignored `.pql/pql.db`. The