task-pipeline-skill 1.64.0 → 1.65.0

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## v1.65.0 — a decision is not debt
+
+**`open` is work not done, `dropped` is an idea abandoned, and neither fits a deliberate
+*no*.** Putting a decision in `open` has a cost that only appears later: **it accrues age
+exactly like debt and eventually outranks real work.**
+
+Measured on 2026-08-16. Two rows in the family umbrella recorded decisions on 2026-08-06 —
+one waiving a UX chain in favour of fixtures, one keeping a skill an audit because another
+router carries the design-time rule. Both sat `open`. The moment the age term started being
+computed they reached the **top** of that board at 2.67 each, and the next run spent itself
+re-deriving two decisions that were correct when made and are still correct.
+
+So `waived` is a state: not counted open, no priority (`—`), and it must name what would
+bring it back. **The `revisit:` clause is mandatory and gated** — a waiver with no trigger
+is a row nobody will reconsider, and the trigger has to be something a later run can
+measure. *"The command surface grows past what the fixtures describe"* is checkable; *"if
+it becomes a problem"* is not.
+
+The doctrine also requires the condition to be **re-derived when the row is touched**, like
+any other claim. Both umbrella rows were re-measured before being waived — 8 CLI commands
+with 0 uncovered by fixtures, and a router that still states the rule — because a waiver
+resting on a condition nobody has checked is the same expired claim in a quieter voice.
+
+Guards: 349 → **351**. Both new plants watched rejecting their defect: a waived row that
+keeps its priority, and a waiver that names no trigger.
+
 ## v1.64.0 — the exposure line reported a clean bill on ledgers it could not read
 
 **The exposure command reported a clean bill on ledgers it could not read.** Shipped two

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.64.0 |
+| **Version** | 1.65.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.64.0",
+  "version": "1.65.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.64.0",
+  "version": "1.65.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
+- A decision is not debt — `waived`
 - What a loop iteration does with it
 - Rationalizations
 
@@ -120,6 +121,39 @@ 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.
 
+## A decision is not debt — `waived`
+
+`open` is work not done. `dropped` is an idea abandoned. Neither fits a deliberate **no**
+that could be revisited, and putting one in `open` has a cost that only shows up later:
+**a decision accrues age exactly like debt, and eventually outranks real work.**
+
+Measured in this family on 2026-08-16. Two rows recorded deliberate decisions on
+2026-08-06 — one waiving a UX chain in favour of fixtures, one keeping a skill an audit
+because another router carries the design-time rule. They sat `open`. The moment the age
+term started being computed they reached the **top** of the board at 2.67 each, and the
+next run spent itself re-deriving two decisions that were correct when made and are still
+correct.
+
+So:
+
+```
+| B-NNN | … | … | 1 | 7 | 3 | — | waived — revisit: <the condition, and how to measure it> |
+```
+
+- **Not counted open.** It is not queued work and must not appear as any.
+- **No priority.** The cell reads `—`; ranking a decision puts it above things to do.
+- **`revisit:` is mandatory.** A waiver with no trigger is a row nobody will reconsider,
+  and the trigger must be something a later run can **measure** — *"the command surface
+  grows past what the fixtures describe"* is checkable; *"if it becomes a problem"* is not.
+- **Still disclosed every run.** A waiver that becomes invisible is how a decision outlives
+  the reason for it. It is printed beside the verdict, never counted in it.
+
+**And the revisit condition is re-derived when the row is touched**, like any other claim
+([`knowledge-sources.md`](knowledge-sources.md)). Both of the rows above were re-measured
+before being waived — 8 commands with 0 uncovered by fixtures, and a router that still
+states the rule — because a waiver resting on a condition nobody has checked since 2026 is
+the same expired claim in a quieter voice.
+
 ## What a loop iteration does with it
 
 At the **top** of an iteration, one command: count the open rows and read the top few.

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

@@ -15,6 +15,7 @@
 | B-002 | XLSX export path | `2026-07-28-export` / 5 Dev | M | 1 | 2 | 12 | 2 | open | LIN-483 |
 | B-003 | REQ-007 bulk export | `2026-07-28-export` / 2 Brainstorm | L | 1 | 1 | 12 | 1 | dropped | operator 2026-07-28 |
 | B-004 | Retry/backoff on the upload path | `2026-07-28-export` / 5 Dev | M | 2 | 2 | 4 | **4** | parked — feat/upload-retry | — |
+| B-005 | Per-tenant rate limits | `2026-07-28-export` / 2 Brainstorm | L | 1 | 1 | 9 | — | waived — revisit: a tenant exceeds 1k req/min in `docs/metrics.md` | — |
 
 ## Columns