task-pipeline-skill 1.48.0 → 1.49.1

package/CHANGELOG.md

@@ -1,5 +1,54 @@
 # Changelog
 
+## v1.49.1 — the entry states the count its own guard reads
+
+### Fixed
+
+- **v1.49.0 tagged but never released.** Its CHANGELOG entry stated no
+  `Guards: N → **M**` count, so two of this repo's negative self-tests had
+  nothing to patch and reported `PLANT DID NOT LAND` — the release job failed
+  after the tag was already public. Same class as v1.45.0, and the guard worked
+  exactly as designed: a probe that cannot plant says so instead of passing.
+
+  The count is unchanged because v1.49.0 added a feature, not enforcement.
+
+Guards: 309 → **309**. Property checks: 9 → 9. The installer change is
+behavioural and carries no new guard; the count is stated because two probes read
+the newest section and a count-shaped sentence with no count is the one case
+where silence and agreement look the same.
+
+### Changed
+
+- Everything in v1.49.0, which never shipped: the installer now offers the
+  family's routing block via `npx sshlg-skills routers --member task-pipeline`,
+  scoped so it repairs only this skill's own section. See that entry below.
+
+## v1.49.0 — the installer stops leaving the skill unrouted
+
+### Changed
+
+- **The installer now offers the family's routing block** (closing B-06 in the
+  umbrella). Until now only `super-ux` delegated: install this skill on its own
+  and no router was written at all, so an agent had the skill and no rule saying
+  when to reach for it. The bundle installer wrote all eight, which is why
+  nothing looked broken — the gap only opened for someone installing one member.
+
+  Delegated to `npx sshlg-skills routers --member task-pipeline` rather than
+  reimplemented, for three reasons:
+
+  - The block describes what the machine actually has. A lone member rendering
+    the whole thing would print a table for routers nobody installed.
+  - `--member` scopes the write to this skill's own section. Verified by damaging
+    two sections of a real block and running this installer: its own was
+    repaired, the other left exactly as it was.
+  - The launcher is the only writer that copies the operator's global instruction
+    file before touching it. That file has no version control behind it.
+
+  `--no-install` keeps it from silently downloading a package nobody asked for.
+  When the launcher is absent the command is printed instead of failing: ending
+  an install in an error over an optional follow-up reads as a failed install.
+  Both paths were exercised.
+
 ## v1.48.0 — a screen is the frame implemented, and four mechanisms this project owed itself
 
 **A screen is the frame, implemented.** Until now Figma was an address and a link: the

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.48.0 |
+| **Version** | 1.49.1 |
 | **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/bin/task-pipeline.js

@@ -54,6 +54,39 @@ function installOne(label, src, dest, isDir, force) {
   console.log(`Installed ${label} -> ${dest}`);
 }
 
+/**
+ * Ask the family launcher to write the routing block, for this member only.
+ *
+ * Delegated rather than reimplemented, for three reasons. The block describes
+ * what the machine actually has, so a lone member rendering the whole thing
+ * would produce a table for routers nobody installed. `--member` limits this to
+ * the `task-pipeline` section and leaves everyone else's alone, which is what
+ * lets the bundle and a single installer both write. And the launcher is the
+ * only writer that copies the operator's global instruction file before touching
+ * it — that file has no version control behind it, and two defects in this
+ * family's history destroyed it.
+ *
+ * `--no-install` keeps this from silently downloading a package the user did not
+ * ask for. When the launcher is absent, print the one command instead of
+ * failing: an installer that ends in an error because an OPTIONAL follow-up is
+ * missing reads as a failed install.
+ */
+function offerRouters() {
+  const { spawnSync } = require('child_process');
+  const r = spawnSync(
+    'npx',
+    ['--no-install', 'sshlg-skills', 'routers', '--member', 'task-pipeline'],
+    { stdio: 'inherit', shell: process.platform === 'win32' }
+  );
+  if (r.status !== 0) {
+    console.log(
+      '\nTo have this skill apply by default in every project, add the\n' +
+      "family's routing block to your agent's global instructions:\n\n" +
+      '  npx --yes sshlg-skills routers --member task-pipeline\n'
+    );
+  }
+}
+
 function main(argv) {
   const args = argv.slice(2);
   if (args.includes('--help') || args.includes('-h')) {
@@ -115,6 +148,7 @@ Rerun with --force if you deliberately want the plain copy instead.`);
     false,
     force
   );
+  offerRouters();
   return 0;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "task-pipeline-skill",
-  "version": "1.48.0",
+  "version": "1.49.1",
   "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.48.0",
+  "version": "1.49.1",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"