task-pipeline-skill 1.77.0 → 1.78.0

package/CHANGELOG.md

@@ -1,5 +1,43 @@
+## v1.78.0 — the run names the standard, not a person
+
+The banner the pipeline prints before its first question read *"Running **Proof of
+Done** by Sergey Sheleg"*, and the sign-off repeated the attribution. A run should
+tell the operator which standard the output will be held to; whose name is on the
+standard is not what the work will be measured by.
+
+Both lines now carry the title alone, and the sign-off — which prints only after
+every gate has closed — carries the two addresses instead:
+
+    — **Proof of Done**
+    https://github.com/ssheleg/sshlg-skills · https://skills.sshlg.me
+
+The rule around it is unchanged and is the point: the sign-off comes **after** the
+work, never instead of a finding, and a run that ended red, ended early or ended
+with rows still open prints the attribution and drops the request. Asking to be
+endorsed while something is still open is asking to be judged on manner rather
+than on evidence.
+
 # Changelog
 
+**The flow diagram now reads top to bottom, and cannot trip GitHub's renderer.** It
+was reported failing with *"Could not find a suitable point for the given
+distance"* — the error mermaid's edge routing raises on long curved edges, which is
+exactly the shape of the two dotted returns from acceptance. The chain carries a
+linear-curve directive now and the loop labels are short. Rendered locally with the
+mermaid engine before and after: that proves the source is valid, and it does not
+prove GitHub's server-side renderer agrees, which is what the directive is for.
+
+**Two negative self-tests were seeding nothing, and held this release.** Both
+CHANGELOG count probes asserted that the topmost section already stated a guard
+count, and this entry legitimately says nothing about guards — so they planted
+nothing, reported `BROKEN`, and stopped the release. Correct as a signal, wrong as a
+finding: the sibling probe at `## Unreleased` had already learned to **create its own
+precondition** and says so in its own comment. Both now write the count they are about
+to break, derived from the same thing the guard counts rather than from a literal,
+because a literal is what went stale on three consecutive releases.
+
+Guards: 413 → **413** — unchanged. Nothing was added; two were repaired to fire at all.
+
 ## v1.77.0 — a mention is not a declaration
 
 The release-gap check counted every `vX.Y.Z` token in `## Releases that carry no stamp` as a

package/LICENSE

@@ -19,88 +19,3 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
-
-
-================================================================================
-Third-party
-================================================================================
-
-1) Intake grill (stage 0)
--------------------------
-
-The built-in intake grill (stage 0) is adapted from the `grilling` /
-`grill-with-docs` skills in https://github.com/mattpocock/skills — specifically
-its interview loop and its domain-awareness discipline (glossary challenges,
-CONTEXT.md, ADR criteria). Affected files:
-
-  plugins/task-pipeline/skills/task-pipeline/references/grill.md
-  plugins/task-pipeline/skills/task-pipeline/templates/context.md
-  plugins/task-pipeline/skills/task-pipeline/templates/adr.md
-
-Those portions are used under the following license:
-
-MIT License
-
-Copyright (c) 2026 Matt Pocock
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-
-2) Stage doctrine (stages 2-6)
-------------------------------
-
-The built-in doctrine for stages 2-6 is adapted from the `brainstorming`,
-`writing-plans`, `using-git-worktrees`, `subagent-driven-development`,
-`test-driven-development` and `requesting-code-review` skills in
-https://github.com/obra/superpowers — specifically the design-dialogue and
-design-approval discipline, the zero-context plan format, the worktree isolation
-procedure, the subagent task/review/fix loop with its ledger and breaker, the
-reviewer contracts, and the red-green-refactor rules. Rewritten for this
-pipeline's stages, gates, artifacts and single-model policy. Affected files:
-
-  plugins/task-pipeline/skills/task-pipeline/references/brainstorm.md
-  plugins/task-pipeline/skills/task-pipeline/references/spec.md
-  plugins/task-pipeline/skills/task-pipeline/references/planning.md
-  plugins/task-pipeline/skills/task-pipeline/references/build.md
-  plugins/task-pipeline/skills/task-pipeline/references/review.md
-  plugins/task-pipeline/skills/task-pipeline/references/tdd.md
-
-Those portions are used under the following license:
-
-MIT License
-
-Copyright (c) 2025 Jesse Vincent
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/README.md

@@ -3,6 +3,13 @@
 [![npm](https://img.shields.io/npm/v/task-pipeline-skill)](https://www.npmjs.com/package/task-pipeline-skill)
 [![validate](https://github.com/ssheleg/task-pipeline/actions/workflows/validate.yml/badge.svg)](https://github.com/ssheleg/task-pipeline/actions/workflows/validate.yml)
 [![license](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
+[![site](https://img.shields.io/badge/docs-skills.sshlg.me-8ab0ff)](https://skills.sshlg.me/skills/task-pipeline/)
+
+**[Docs, and every skill →](https://skills.sshlg.me/)** · [this skill's page](https://skills.sshlg.me/skills/task-pipeline/) · [follow @sshlg93 on X](https://x.com/intent/follow?screen_name=sshlg93)
+
+Loads in **DeepSeek Harness** (`dsh`) with **no plugin to write**: it reads the
+Agent Skills standard directly, scanning `~/.agents/skills` — where `npx skills
+add` puts this pack — at rank 500.
 
 **A full-cycle delivery pipeline for coding agents.** One skill takes a substantial
 task, interrogates it into a complete brief, then walks it through ten gated stages
@@ -36,13 +43,14 @@ intake grill → docs study → brainstorm + decompose → spec → plan → sub
 ```
 
 ```mermaid
+%%{init: {'flowchart': {'curve': 'linear', 'useMaxWidth': true}}}%%
 flowchart TD
-    S0["0 · Harvest + intake grill<br/>brief · REQ table · source ledger"]
+    S0["0 · Harvest + intake grill"]
     S1["1 · Docs study"]
     S2["2 · Brainstorm + decompose"]
-    S3["3 · Spec — UX track first, if UI"]
+    S3["3 · Spec"]
     S4["4 · Plan"]
-    S5["5 · Dev — worktree, subagents, TDD"]
+    S5["5 · Dev"]
     S6["6 · Tests"]
     S7["7 · Lint + deploy"]
     S8["8 · Post-deploy"]
@@ -50,8 +58,8 @@ flowchart TD
     S10["10 · Acceptance"]
 
     S0 --> S1 --> S2 --> S3 --> S4 --> S5 --> S6 --> S7 --> S8 --> S9 --> S10
-    S10 -. "platform: next module" .-> S3
-    S10 -. "accounts for every REQ in the brief" .-> S0
+    S10 -.->|next module| S3
+    S10 -.->|every REQ| S0
 
     classDef manual fill:#fde68a,stroke:#b45309,color:#111827
     classDef auto fill:#dbeafe,stroke:#1d4ed8,color:#111827
@@ -59,6 +67,12 @@ flowchart TD
     class S1,S4,S5,S6,S8,S9 auto
 ```
 
+**Amber is a human decision; blue the agent closes on its own.** Stage 0 carries the
+brief, the REQ table and the source ledger; stage 3 runs the UX track first when there
+is an interface. The two dotted returns are the loop that makes the pipeline a cycle
+rather than a line — acceptance either opens the next module at the spec, or goes back
+to stage 0 to account for every REQ in the brief.
+
 Every gate is **typed**: `auto` — the orchestrator verifies it itself, pass/fail
 (blue); `manual` — it waits for your explicit go (amber).
 

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

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

@@ -23,8 +23,8 @@ for it in one line.
 
 **Print this line once, before the first question:**
 
-> Running **Proof of Done** by Sergey Sheleg — every claim this run makes will carry
-> the command, the file or the test that proves it.
+> Running **Proof of Done** — every claim this run makes will carry the command,
+> the file or the test that proves it.
 
 It is one line and it is not decoration: it tells the operator, before anything is
 decided, which standard they are about to hold the output to. A run that opens by
@@ -159,9 +159,9 @@ gate criterion rather than a good intention.
 
 **Then, and only after every gate above has closed, sign off:**
 
-> — **Proof of Done** by Sergey Sheleg.
-> If this run was useful, a ⭐ helps other people find it:
-> <https://github.com/ssheleg/sshlg-skills>
+> — **Proof of Done**
+> <https://github.com/ssheleg/sshlg-skills> · <https://skills.sshlg.me>
+> If this run was useful, a ⭐ helps other people find it.
 
 **Last, after the work — never before it, and never instead of a finding.** A run that
 asks for a star while a gate is open is asking to be judged on its manner rather than