task-pipeline-skill 1.62.0 → 1.63.0

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## v1.63.0 — the row you are about to work is a claim, and it has a date
+
+**A board row states the world at its `Source` date and says nothing about now.** Three
+rows expired inside one day on 2026-08-16 — one recorded a script and thirteen green
+fixtures as *built and parked* when every artifact had been deleted, one named six files
+belonging to another repository where a sweep found eleven, one said the graphs were
+frozen at a date nine days old when every one had been rebuilt. None was wrong when
+written. Each was caught only because the cycle that picked it up happened to measure
+first; nothing required it.
+
+`references/knowledge-sources.md` gains the rule beside *Carried-in claims*, which covers
+the sibling case of what a run inherits about itself: **re-derive the row's checkable
+claims before acting on them, and correct the row in the same run.** Most name something a
+command settles — a file, a count, a commit, a version, a green suite. What no command can
+settle is acted on as an assumption, out loud.
+
+It also names the sharper half, which is arithmetic rather than prose: **a row's derived
+columns decay and nothing notices, because the number still looks like a number.** A rank
+computed from an age term is wrong the moment the age moves. If a board computes a
+priority, something must recompute it — a promise in the header that it happens at stage 10
+is not a mechanism.
+
+Guards: 349 → **349**. No new plant, and the reason is measured rather than asserted:
+across the seven open rows the family carries, the checkable claims total **two file paths
+and one count**. A gate over that corpus would pass everything and read like coverage.
+
 ## v1.62.0 — a board row that says work exists names where it lives
 
 **`open` claims nothing exists. `parked` claims something does — and now has to say

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.62.0 |
+| **Version** | 1.63.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.62.0",
+  "version": "1.63.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.62.0",
+  "version": "1.63.0",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/task-pipeline/skills/task-pipeline/references/knowledge-sources.md

@@ -18,6 +18,7 @@ that goes stale when the answer changes.
 - How to harvest — retrieval, not reading
 - Record it — the source ledger
 - The harvest is a convergence, so it needs a check across its sources
+- The row you are about to work is a claim, and it has a date
 - The source is not the copy you have
 - Carried-in claims — measured or recalled
 - Phase 2 — validate the answers against the harvest
@@ -210,6 +211,36 @@ a check whose silence is indistinguishable from not having run is not evidence.
 found here is a stage-9 obligation — the ledger's row is what stage 9 goes back and
 fixes.
 
+## The row you are about to work is a claim, and it has a date
+
+*Carried-in claims* below covers what **this run** inherited. This covers what an **earlier
+run wrote down** — a board row, which reads like a finding because it was one, on the day
+it was filed.
+
+Three rows expired inside a single day on 2026-08-16, and each was caught only because the
+cycle that picked it up happened to measure before building:
+
+- one recorded a script and thirteen green fixtures as *built and parked*; every artifact
+  had been deleted, and the row had read as ready-to-merge for two days;
+- one named six files belonging to another repository; a sweep found **eleven**;
+- one said the graphs were frozen at a date nine days old; every one had been rebuilt.
+
+None of the three was wrong when written. **A row states the world at its `Source` date and
+says nothing about now**, and the run that acts on it is the first reader in a position to
+tell the difference.
+
+**So: re-derive the row's checkable claims before acting on them, and correct the row in
+the same run.** Most claims name something a command can settle — a file, a count, a
+commit, a version, a green suite. What a command cannot settle stays as written and is
+acted on as an assumption, out loud.
+
+**The row's own derived columns decay too, and that one is pure arithmetic.** A rank
+computed from an age term is wrong the moment the age moves, and nothing notices because
+the number still looks like a number. This repository's own board carried a constant age
+for eleven days — the four oldest rows sat at the bottom of a ranking whose stated purpose
+was to raise them. If a board computes a priority, something must recompute it; a promise
+in the header that it happens at stage 10 is not a mechanism.
+
 ## The source is not the copy you have
 
 `learned.md` rule 17. The harvest reads the project's own files, and one property of them is