task-pipeline-skill 1.69.0 → 1.70.0

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## v1.70.0 — the stemmer cannot conjugate, so the description says the other form
+
+`запиши решение` — the imperative a person actually types — reached no route at all, while
+`evidence-docs` advertised the infinitive `записать решение`. The umbrella's matcher stems
+`записать` to `записа-` and cannot reach `запиш-`: the с/ш alternation is a conjugation class,
+not an ending, and `lib/triggers.js` says in its own header that it is *deliberately NOT a
+morphological analyser*.
+
+**So the fix is here rather than there.** Teaching a load-bearing stemmer one conjugation
+class for one trigger was measured and refused (`B-84` on the umbrella's board); advertising
+the second form costs **19 characters in a description with 124 free**. The description now
+carries both, and the umbrella routes `запиши решение`, `запишите решение` and
+`запиши решение по архитектуре` to `evidence-docs`.
+
+**One false positive, measured rather than overlooked.** It also fires on «запиши решение
+суда». A court decision does not occur on this machine and the cost of the hit is one injected
+line — where `аудит` was refused against `аудитория` precisely because that word is common.
+The trade is named here so a later reader does not have to re-derive it.
+
+Coverage on the umbrella's own corpus: **64/15 → 65/14** of 79 prompts.
+
+Guards: 376 → **376**. No guard was added or removed — this release changes one description
+and nothing it asserts is new; the umbrella's fixture that every trigger is advertised is what
+holds the pair together, and it lives there rather than here.
+
 ## v1.69.0 — the work graph, and a check that mentions is not a check that binds
 
 **Module 1 of the role-agent programme, complete** — T-1 through T-7, briefed in

package/README.md

@@ -114,7 +114,7 @@ stage and walks the gates. See [Install](#install) for the other channels.
 `task-pipeline` is the reference implementation of **Proof of Done: The Agentic
 Software Development Manifesto** by Sergey Sheleg — *a foundation for building
 software when agents write the code*. The manifesto has its own home:
-<https://github.com/ssheleg/pod-manifesto>.
+<https://podmanifesto.org> (source: <https://github.com/ssheleg/pod-manifesto>).
 
 Its central claim is that the unit of progress is not generated code but an
 **evidence-carrying change**: one carrying the intent it implements, the evidence that

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

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

@@ -1,6 +1,6 @@
 ---
 name: evidence-docs
-description: "Use when writing or reviewing anything that will be read as true — a decision record, a README, an acceptance report, a runbook, a changelog entry, an audit finding, or any claim that something was verified. Applies the ten canons of evidence-backed documentation — what makes a claim documentation rather than an assertion — and routes to the doctrine that enforces each one. Also use when a project needs a documentation gate, a decision register, a propagation matrix, or a retrospective that outlives its author. Triggers - 'documentation gate', 'decision record', 'ADR', 'acceptance report', 'runbook', 'is this verified', 'доказательная документация', 'записать решение', 'отчёт о приёмке', 'раннбук', 'чем это подтверждено', 'доки в синхроне'. Not for: drafts, chat answers, commit messages or code comments — say 'без доков' to opt out."
+description: "Use when writing or reviewing anything that will be read as true — a decision record, a README, an acceptance report, a runbook, a changelog entry, an audit finding, or any claim that something was verified. Applies the ten canons of evidence-backed documentation — what makes a claim documentation rather than an assertion — and routes to the doctrine that enforces each one. Also use when a project needs a documentation gate, a decision register, a propagation matrix, or a retrospective that outlives its author. Triggers - 'documentation gate', 'decision record', 'ADR', 'acceptance report', 'runbook', 'is this verified', 'доказательная документация', 'записать решение', 'запиши решение', 'отчёт о приёмке', 'раннбук', 'чем это подтверждено', 'доки в синхроне'. Not for: drafts, chat answers, commit messages or code comments — say 'без доков' to opt out."
 ---
 
 # Evidence-backed documentation