task-pipeline-skill 1.32.0 → 1.33.0

package/CHANGELOG.md

@@ -1,5 +1,51 @@
 # Changelog
 
+## v1.33.0 — the number, the list, and the command that shows them with no task running
+
+Three modules shipped as one, because they are one capability: the index, the list it
+produces, and the command that prints them when nothing else is running.
+
+**Exposure is a vector with its components named, never a probability.** The request that
+started this asked for *"the probability of an error"*. It is not computable from these
+inputs, and a number dressed as one is the class this repository has spent its history
+removing — so the guard rejects a `%` on that line outright:
+
+```
+exposure: 99 unverified · never checked · 10 releases carry one
+    REQ-001  references/setup.md — the entry audit: when it runs …   v1.10.0
+    …
+    and 91 more — the full list is `/task-pipeline checkup`
+```
+
+**`never checked`, not `0 days`.** When no row has ever been confirmed — this repo's
+exact state — a zero would read as *checked today*, the precise inversion this pipeline
+exists to prevent. The literal is required by its own guard.
+
+**A single score was refused on purpose.** One number invites a threshold, and a
+threshold here is a target on `never`, which `verification.md` says may never have one.
+The components are one line; a reader can hold three.
+
+**`/task-pipeline checkup` runs with no task in flight**, which is the whole point:
+accumulated unconfirmed work is invisible precisely because nobody is running a pipeline,
+so a check living only inside a run can never say *stop, fourteen things are
+unconfirmed*. It reads four files this pipeline already keeps and writes nothing unless
+asked — and then only board rows whose `Source` names the checkup, printed before they
+are added.
+
+**And `continuity.md` finally names the file it always demanded.** It has required each
+iteration to re-measure the work-list since the beginning, and said *"next up is X"* is
+a claim no gate reads. The board is that list; the claim now cites a `B-NNN`, which can
+be checked, rather than a description, which cannot.
+
+**Two defects in the new guard, both self-inflicted and both instructive.** Its needle
+looked for *"never a percentage"* while the doctrine it guards says *"no percentage,
+ever"* — guard and prose written an hour apart, already disagreeing. And the `%` check
+searched for a literal that its own line necessarily contains, so it matched **itself**
+and passed a planted percentage. A detector that matches itself first is checking the
+wrong thing.
+
+Guards: 185 → **188**, property checks 8.
+
 ## v1.32.0 — the column a machine may not fill
 
 Stage 8 already performs the verification trio, reads the CI verdict and opens the

package/CONTRIBUTING.md

@@ -396,7 +396,16 @@ property check proves that filling the column does not fail the build, because a
 that punishes an honest answer will not receive one.
 *(guard: `either a date or the literal` and `is in no brief's REQ table`)*
 
-**46. Every invariant above names the guard that enforces it, and that guard exists.**This list claims to be *what the validator enforces*; it was eight guards behind when
+**46. Exposure prints as a named vector and never as a probability.** The request that
+produced it asked for `P(defect)`; it is not computable from these inputs, and a single
+score invites a threshold, which is a target on `never` — the one thing the verification
+ledger says may never have one. A `%` on that line fails the build. Where no row has ever
+been confirmed the line prints the literal `never checked`, because `0 days` reads as
+*checked today*. The doctrine carries both rules where a reader proposing a percentage
+will find them.
+*(guard: `may never take` and `carry it where the next reader looks`)*
+
+**47. Every invariant above names the guard that enforces it, and that guard exists.**This list claims to be *what the validator enforces*; it was eight guards behind when
 an audit measured it. A claim of enforcement is now checked like any other claim.
 *(guard: `whose message does not appear in`)* — and a cited literal must lie inside
 a **single** string in `test/validate.py`: the check reads that file as text, so a

package/README.md

@@ -131,6 +131,7 @@ until it is installed.
 | run-wide pacing | [`continuity.md`](plugins/task-pipeline/skills/task-pipeline/references/continuity.md) — the loop mode (`run.loop`, default off, never collapses a manual gate) and the context budget (fires on a harness signal, never on an estimate) |
 | the board between runs | [`backlog.md`](plugins/task-pipeline/skills/task-pipeline/references/backlog.md) — the work-list that outlives a run: seeded at stage 0 or picked up, priority **computed** from three stated inputs rather than assigned, and the seam where the carry-over ledger's `backlog` pointer finally resolves |
 | what a human confirmed | [`verification.md`](plugins/task-pipeline/skills/task-pipeline/references/verification.md) — one row per shipped REQ and the one column a machine may not fill: the date somebody **looked**, or `never`. No floor, no target — `never` is a fact, and a count driven down is a column that has started lying |
+| how much is unconfirmed | [`exposure.md`](plugins/task-pipeline/skills/task-pipeline/references/exposure.md) — the unconfirmed count as a **vector with its components named**, never a percentage: `P(defect)` is not computable from these inputs and a single score invites a threshold, which is a target on `never`. Plus the check-list, oldest first, and the `/task-pipeline checkup` mode that prints it with no task in flight |
 | 0 + 9 + any settled decision | [`documentation.md`](plugins/task-pipeline/skills/task-pipeline/references/documentation.md) — the inventory, registers and ids, SSOT, the Doc Loop, supersede semantics, the propagation matrix, intent vs as-built |
 | 3 + 4 · every spec and plan | the self-review reads its rules back — is every named check real, does anything contradict a locked decision or a rejected option, and what does this cost now versus at design time. Answers land as a committed `## Self-review` of computed numbers |
 | 6–10 + any check you write | [`gates.md`](plugins/task-pipeline/skills/task-pipeline/references/gates.md) — the three axes, the promotion ladder, gate anatomy, the probe recipe, ratchet floors |

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.32.0 |
+| **Version** | 1.33.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. 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.32.0",
+  "version": "1.33.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 must close with evidence, a loop guard that breaks churn, one provider-agnostic model confirmed up front, and an optional super-ux UX track for user-facing work.",
-  "version": "1.32.0",
+  "version": "1.33.0",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/task-pipeline/commands/task-pipeline.md

@@ -44,6 +44,17 @@ Idempotent entry — inspect state first, never restart blindly:
 - Otherwise, begin at stage 0 (intake grill). If no task is given above, the
   grill's first question asks the operator for the task in one line.
 
+**`/task-pipeline checkup`** — **runs with no task in flight, and that is the point.**
+Accumulated unconfirmed work is invisible precisely because nobody is running a pipeline,
+so a check living only inside a run can never say *"stop, fourteen things are
+unconfirmed."* It takes no brief, opens no grill, and writes nothing on its own. Four
+sections, each read from a file this pipeline already keeps: the **exposure** line with
+its check-list oldest-first, the **board**'s open rows by computed priority, the
+carry-over ledgers' unresolved count, and the code graph's staleness where one exists.
+Where you ask it to file what it found, it appends board rows whose `Source` names the
+checkup and its date — printing what it would add first, never silently. Doctrine:
+`references/exposure.md`.
+
 **`/task-pipeline setup`** — the entry audit instead of a feature. Runs seven passes
 over the documentation this project already has, reports findings as `file:line` + the
 minimal fix ordered by seam, and hands back a fix plan the pipeline can run. Offered

package/plugins/task-pipeline/skills/task-pipeline/SKILL.md

@@ -70,6 +70,7 @@ gate stops until it is installed.
 | run-wide · how a run keeps going (the loop mode + the context budget) | [`references/continuity.md`](references/continuity.md) |
 | run-wide · the work-list **between** runs, and how its priority is computed | [`references/backlog.md`](references/backlog.md) |
 | run-wide · whether a **human** ever confirmed what shipped, and when | [`references/verification.md`](references/verification.md) |
+| run-wide · how much unconfirmed work has piled up, and what to look at first | [`references/exposure.md`](references/exposure.md) |
 
 **Optional bridge.** If the operator already runs an equivalent skill set (e.g.
 `superpowers:brainstorming` / `writing-plans` / `subagent-driven-development` /

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

@@ -129,9 +129,16 @@ works a stale board for as long as the loop runs. One command, at the top of the
 iteration, recorded ([`knowledge-sources.md`](knowledge-sources.md) → *Carried-in
 claims*; [`learned.md`](learned.md) rule 16).
 
+**The work-list is `docs/superpowers/backlog.md`** ([`backlog.md`](backlog.md)), and the
+other half of the same measurement is the exposure line ([`exposure.md`](exposure.md)).
+Counted at the top of the iteration, re-derived at the bottom — `age` moves on its own,
+so the re-derivation is the only moment the board stops being stale.
+
 This is also where a loop's report goes wrong most quietly. *"Next up is X"* at the
 end of an iteration is a claim about the board, and it is the one sentence in the
-whole cycle that no gate reads. It cites the measurement or it is not written.
+whole cycle that no gate reads. It cites the measurement or it is not written — **a
+`B-NNN`, not a description**: *"next up: B-014"* can be checked against the file,
+*"next up: the export fix"* cannot.
 
 ## Parked at a manual gate
 

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

@@ -0,0 +1,103 @@
+# Exposure — how much unverified work has piled up, and what to look at
+
+**One job: turn the verification ledger into a number somebody can act on, without
+pretending it is a probability.**
+
+[`verification.md`](verification.md) records whether a person ever confirmed each shipped
+REQ. This file turns that record into the line printed beside every verdict, and into the
+list `/task-pipeline checkup` hands an operator.
+
+---
+
+## Contents
+
+- Why it is not a probability
+- The components, each named
+- The check-list, and how it is ordered
+- `/task-pipeline checkup`
+- What the loop does with it
+- Rationalizations
+
+## Why it is not a probability
+
+The request that produced this file asked for *"the probability of an error"*. That is
+not computable from these inputs, and a number presenting itself as `P(defect)` is the
+false-success class this repository has spent its whole history removing: an estimate
+wearing a measurement's clothes.
+
+**So no percentage, ever** — the guard rejects a `%` on the exposure line. What ships is
+a **vector with its components named**, and the reason is not fussiness: a single score
+invites a threshold, and a threshold here is a target on `never`, which is the one thing
+[`verification.md`](verification.md) says may never have one.
+
+It could become a real probability later. `verification.md` is exactly the journal that
+would make calibration possible after enough runs carry both a confirmation date and a
+defect. Until then it is named honestly.
+
+## The components, each named
+
+```
+exposure: 99 unverified · never checked · 31 releases since the last human confirmation
+```
+
+- **unverified** — rows whose `Human` reads `never`.
+- **since** — days since the newest `Human` date. When **no** row has ever been
+  confirmed, this prints the literal **`never checked`**, not `0 days`: zero would read
+  as *checked today*, which is the opposite of the truth and exactly the kind of quiet
+  inversion this pipeline exists to prevent.
+- **releases** — tags cut since that date, or since the first shipped row when there is
+  no date. It is the component an operator feels: *"how much has gone out on top of
+  something nobody looked at."*
+
+Every component is derived from files in the repository. None is estimated.
+
+## The check-list, and how it is ordered
+
+The list is the deliverable — a number without it tells somebody they have a problem and
+not where. Ordered by what the repository can defend:
+
+1. **Oldest first**, by `Shipped in`. The longest-unconfirmed row is the one whose
+   context is most gone, and whose author is least likely to remember it.
+2. **Tie-broken by blast radius** where the board carries a row for it, reusing
+   [`backlog.md`](backlog.md)'s own stated input rather than inventing a weight here.
+
+No third factor. A ranking with an unstated input is the hand-assigned priority the board
+already refuses.
+
+## `/task-pipeline checkup`
+
+A **mode of the command**, like `setup` — not a new command, because a second command
+costs every surface a command touches and this repository has learned what that means.
+
+**It runs with no task in flight, and that is the point.** Accumulated unverified work is
+invisible *precisely because nobody is running a pipeline*; a check that only exists
+inside a run can never say *"stop, fourteen things are unconfirmed."* So it takes no
+brief, opens no grill, and writes nothing on its own.
+
+It prints four sections, each read from a file this pipeline already keeps: the exposure
+line and its check-list, the board's open rows by computed priority, the carry-over
+ledgers' unresolved count, and the code graph's staleness where one exists.
+
+**Where the operator asks it to file findings**, it appends board rows whose `Source`
+names the checkup and its date — so a row a machine created is distinguishable from one a
+run surfaced. It prints what it would add first. Never silently.
+
+## What the loop does with it
+
+[`continuity.md`](continuity.md) has always required each iteration to re-measure the
+work-list, and said that *"next up is X"* is a claim about the board that no gate reads.
+[`backlog.md`](backlog.md) is that board; the exposure line is the other half of the same
+measurement, and both are read at the top of an iteration and re-derived at the bottom.
+
+An iteration that reports what it will do next **cites the file**: `B-014`, not *"the
+export fix"*.
+
+## Rationalizations
+
+| The excuse | What is actually true |
+|---|---|
+| "Give me one number, I'll decide the threshold" | The threshold would be a target on `never`, and the column would start lying within a week. The components are one line; read them. |
+| "A percentage is easier to communicate" | It is easier to communicate because it says more than is known. That is the whole objection. |
+| "The check-list is long, just show the top three" | Then the fourth is never checked and nobody knows it exists. Print it all; the operator can stop reading. |
+| "Checkup duplicates stage 8" | Stage 8 verifies **this run's** deploy. Checkup asks what has accumulated across all of them, which no stage is ever in a position to ask. |
+| "We'll run checkup when something breaks" | After a break you know where to look. The list exists for before. |

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

@@ -56,6 +56,7 @@ a row pointing outside the bundle is the defect this file exists to catch.
 | **The context budget** — the evidence rule and what a flush actually updates | `references/continuity.md` |
 | **The board** — the work-list between runs, its computed priority, and the ledger seam it resolves | `references/backlog.md` |
 | **The verification ledger** — what shipped, and whether a human ever confirmed it | `references/verification.md` |
+| **Exposure** — the unconfirmed count as a named vector, never a probability, and the `checkup` mode | `references/exposure.md` |
 | The retro: prune, cap, commits, archive | `references/retrospective.md` |
 | Rules earned by failure | `references/learned.md` |
 | **The routing default and its boundary** | `templates/routing-rule.md` |