task-pipeline-skill 1.65.0 → 1.66.0

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## v1.66.0 — the shape is not fixed, so nothing may assume it
+
+**The check-list printed the size of the work labelled as who it hurts, in every seeded
+project.** `exposure.sh` read the board's blast radius from column 5. That is `Blast` in the
+family umbrella's eight-column board and **`Size`** in the ten-column board this repository
+seeds, so a host project got `[blast L]` — a work-size letter presented as a severity.
+
+It shipped for a full release **two lines away from where the same lesson had just been
+applied to the ledger's status column**. Fixing one instance of a class and leaving the
+other in the same file is the recurrence this repository's retro already names.
+
+Blast is resolved by header now, and two fixtures hold both shapes: the ten-column board
+must yield `[blast 3]` and not `[blast L]`, and the eight-column one must not regress. A
+third case asserts that a board with **no** blast column prints no blast at all — an
+invented weight is worse than a missing one, because it looks like data.
+
+**The rule is written down rather than left as two fixes.** `references/backlog.md` gains
+*The shape is not fixed, so nothing may assume it*: resolve every column by header name,
+once per section and knowing a file may hold more than one shape; treat an absent column as
+absent; and name the column in the output where the reading depends on it. Two board shapes
+exist in this family and five ledger shapes, all documented in their own headers, and none
+of them is wrong — reading any of them by position is.
+
+Fixtures 18 → **20**. Guards: 351 → **351**; these are behaviours of the seeded script,
+which the fixtures exercise by running it.
+
 ## v1.65.0 — a decision is not debt
 
 **`open` is work not done, `dropped` is an idea abandoned, and neither fits a deliberate

package/SKILL-CARD.md

@@ -12,7 +12,7 @@ harmless.
 |---|---|
 | **Purpose** | Runs a substantial task through ten gated delivery stages — intake grill, docs study, brainstorm, spec, plan, subagent build, tests, lint/deploy, post-deploy, docs+registers, acceptance — refusing to advance until each gate passes |
 | **Owner** | ssheleg ([github.com/ssheleg/task-pipeline](https://github.com/ssheleg/task-pipeline)) |
-| **Version** | 1.65.0 |
+| **Version** | 1.66.0 |
 | **Surface** | Claude Code (filesystem skill + plugin) and the vercel `skills` CLI. **Not** uploaded to the Skills API; custom Skills do not sync across surfaces |
 | **Dependencies** | None required. Optional: `context7` (MCP), `figma` (MCP), super-ux, agent-sync, graphify, obsidian-wiki, and **one of two browser channels** — `playwright` (CLI or MCP) or `chrome-devtools` (MCP); either satisfies the browser step and neither is required. Every stage's doctrine ships in-repo; the one conditional requirement is super-ux for the stage-3 UX track on a user-facing task |
 | **Evaluation status** | Suite authored, 5 categories. One recorded run, **self-observed by the author**; **zero blind runs on zero of three models** — the split, and the numbers, live in [`evals/RESULTS.md`](evals/RESULTS.md) and are computed by `evals/run.py` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "task-pipeline-skill",
-  "version": "1.65.0",
+  "version": "1.66.0",
   "description": "Full-cycle delivery pipeline for coding agents: a mandatory built-in intake grill, then 10 gated stages (docs, brainstorm+decompose, spec, plan, build, tests, lint/deploy, post-deploy, docs/wiki, acceptance). Every stage's doctrine ships inside the skill — no companion plugin required. This package is the installer CLI.",
   "bin": {
     "task-pipeline": "bin/task-pipeline.js"

package/plugins/task-pipeline/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "task-pipeline",
   "displayName": "Task Pipeline",
   "description": "Runs a substantial task through a mandatory built-in intake grill, then 10 gated stages (docs, brainstorm+decompose, spec, plan, subagent build, tests, lint/deploy, post-deploy, docs/wiki, acceptance). Every stage's doctrine is built into the skill — no companion plugin required — with typed auto/manual gates, a frozen requirement spine that closes with evidence, a work board and a verification ledger that outlive a run, an exposure line naming what shipped unconfirmed, a progress rail computed from the project's own config, a loop guard whose review ceiling measures rather than stops, and stage-3 tracks for what a product does, how it sounds and how it looks. Two modes need no task: `checkup` (what is unverified) and `setup` (audit existing docs). Retro insights can publish upstream as issues, opt-in and redacted.",
-  "version": "1.65.0",
+  "version": "1.66.0",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/task-pipeline/skills/task-pipeline/references/backlog.md

@@ -20,6 +20,7 @@ exactly one seam, and that seam already existed as a dangling pointer.
 - Seeded or picked up
 - A row that says work exists names where it lives
 - Priority is computed, not assigned
+- The shape is not fixed, so nothing may assume it
 - A decision is not debt — `waived`
 - What a loop iteration does with it
 - Rationalizations
@@ -121,6 +122,32 @@ Two consequences worth stating, because both are the point:
 `sev` and `blast` are judgement, and they are written down *as* judgement: two small
 integers a reader can disagree with, rather than a ranking they can only accept.
 
+## The shape is not fixed, so nothing may assume it
+
+This template ships one shape. Projects change it, and they are right to — the family
+umbrella dropped `Size`, `Sev` and `Home`, added `Effort`, and divides by it, which ranks
+cheap-and-old above expensive-and-old in a way `sev × blast` cannot. Two shapes, both
+documented in their own headers, neither wrong.
+
+**What is wrong is reading either one by position.** `$5` is `Blast` in an eight-column
+board and `Size` in this ten-column one, so a check-list that read index 5 printed
+`[blast L]` in every seeded project — the *size* of the work, labelled as who it hurts.
+It shipped for a full release, two lines from where the same lesson had just been applied
+to a different column.
+
+So the rule, for anything that reads a board or a ledger:
+
+- **Resolve every column by its header name**, once per section, and remember that a file
+  may hold more than one shape.
+- **A column that is absent is absent.** Print nothing rather than a default — an invented
+  weight is worse than a missing one, because it looks like data.
+- **Name the column in the output** where the reading depends on it. `[blast 3]` says which
+  number that is; a bare `3` does not.
+
+The same rule governs the verification ledger, where five shapes exist across this family
+and only one carries a column that can say a *person* looked
+([`exposure.md`](exposure.md)).
+
 ## A decision is not debt — `waived`
 
 `open` is work not done. `dropped` is an idea abandoned. Neither fits a deliberate **no**

package/plugins/task-pipeline/skills/task-pipeline/templates/exposure.sh

@@ -273,7 +273,15 @@ head -"$LIST_MAX" "$TMP/sorted" | while IFS="$(printf '\t')" read -r ship req wh
   # than inventing a weight here. Absent is printed as absent, never as a default.
   blast=""
   if [ -f "$BOARD" ]; then
-    blast=$(grep -m1 "| $req |" "$BOARD" 2>/dev/null | awk -F'|' '{ b=$5; gsub(/^[ \t]+|[ \t]+$/, "", b); print b }')
+    blast=$(awk -F'|' -v req="$req" '
+      function trim(s) { gsub(/^[ \t]+|[ \t]+$/, "", s); return s }
+      # BY HEADER, not by index — the same lesson as the status column, and it was left
+      # two lines away for a whole release. `$5` is `Blast` in an eight-column board and
+      # `Size` in the ten-column one this repository SEEDS, so a host project`s check-list
+      # printed `[blast L]`: the size of the work, labelled as who it hurts.
+      tolower(trim($2)) == "id" { for (i = 2; i < NF; i++) if (tolower(trim($i)) == "blast") bcol = i; next }
+      bcol && trim($2) == req { print trim($(bcol)); exit }
+    ' "$BOARD" 2>/dev/null)
   fi
   if [ -n "$blast" ]; then
     printf '           %-10s %-12s %s  [blast %s]\n' "$ship" "$req" "$what" "$blast"