task-pipeline-skill 1.9.0 → 1.9.1

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # Changelog
 
+## v1.9.1 — 2026-08-03
+
+### Added — the direction of the artifact map that was missing
+
+`references/artifacts.md` mapped **stage → what it writes → who consumes it** and
+nothing the other way. What an agent actually needs at runtime is **what each stage
+reads, and from where** — and that direction had been absent since the file was
+written. It is `references/learned.md` rule 2 (*compute the mapping in both
+directions*) left unapplied to this file itself: the direction that feels redundant
+is the one that finds things.
+
+Two tables now sit above the old one:
+
+- **Stage → input map** — per stage, the exact inputs and their origin. Stage 9's row
+  is the one worth reading twice: it takes **two different lists**, the stage-0 source
+  ledger (what the run *read*) and the doc map's propagation matrix (what the run
+  *owes*), and the gap between them is where documentation rots.
+- **Project-saved rules, and where each one binds** — the eight files a host project
+  owns that change how a run behaves, each with where it is read and where it is
+  enforced: `CLAUDE.md`/`AGENTS.md`, `docs/DOCMAP.md`, the retro's standing
+  instructions, the brief's autonomy section, the carry-over ledger,
+  `docs/ux/scenarios.md`, `.claude/agent-sync.json`, and the operator's global config
+  that decides whether a task routes here at all. Plus the precedence rule: for *what
+  is*, code wins; for *what should be*, the register wins, and the gap is a finding
+  rather than a tie-break.
+
+A guard holds all three maps present, with a negative self-test watched failing.
+
 ## v1.9.0 — 2026-08-03
 
 ### Added — the adoption track, and default-on inside a stated boundary

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.9.0 |
+| **Version** | 1.9.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 (15 evals, 5 categories). **Never executed** — see [`evals/RESULTS.md`](evals/RESULTS.md) |
@@ -38,7 +38,7 @@ apply.
    instruction surface, and every one is linked directly from `SKILL.md`.
 2. Read `templates/docgate.sh` before seeding it; it is the only shipped script a
    host project will run on its own repository.
-3. Run `npm run test:all` — 55 guards, each with a negative self-test that plants a
+3. Run `npm run test:all` — 56 guards, each with a negative self-test that plants a
    defect and requires rejection.
 4. Run `python3 evals/run.py` for the behavioural protocol, and read
    `evals/RESULTS.md` for what has actually been observed.
@@ -54,7 +54,7 @@ apply.
 - **Versions are pinned by git tag** and mirrored into `sshlg-skills`'s catalogue.
   Rollback is `git checkout v<previous>` or pinning the previous plugin version;
   the previous version is never deleted.
-- **Behavioural evidence is missing, not merely thin.** 55 structural guards prove
+- **Behavioural evidence is missing, not merely thin.** 56 structural guards prove
   the skill is well-formed. Until `evals/RESULTS.md` carries a dated run, nothing in
   this repository proves it *behaves* — triggers correctly, stays quiet on a
   question, or performs the steps it documents.

package/evals/RESULTS.md

@@ -37,9 +37,9 @@ or it belongs in a check.
 | Dated runs recorded | **0** | 2026-08-03 |
 
 The bottom two numbers are the honest state of this skill's behavioural evidence.
-Everything else in this repository is proven by 55 structural guards that check the
+Everything else in this repository is proven by 56 structural guards that check the
 *form*; these are the only checks that would speak to the *behaviour*, and they have
-not been run yet. Printed here so "55 of 55 green" is never read as "the skill is
+not been run yet. Printed here so "56 of 56 green" is never read as "the skill is
 known to work".
 
 ## Runs

package/package.json

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

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

@@ -8,6 +8,7 @@ shape.
 ## Contents
 
 - In the host project
+- Stage → input map — where each stage's information comes from
 - Stage → artifact map
 - This repo (task-pipeline itself), for reference
 
@@ -65,6 +66,52 @@ Stage 5 also creates a **git-ignored** scratch workspace per plan at
 review packages. It is deleted when the final review is clean; git history is the
 record (see `build.md`).
 
+## Stage → input map — where each stage's information comes from
+
+The map below this one answers *what a stage writes*. This one answers *what it
+reads, and from where* — the direction that was missing, which is
+[`learned.md`](learned.md) rule 2 (*compute the mapping in both directions*) applied
+to this file itself. A stage whose inputs are unnamed is a stage that will read
+whatever the context happens to hold.
+
+| Stage | Reads | From where |
+|---|---|---|
+| **0 Harvest** | the project's own knowledge about this task | code · the code graph (`graphify-out/`) · `CLAUDE.md`/`AGENTS.md` · `CONTEXT.md`/`docs/adr/` · `docs/` + `docs/ux/` · past briefs and carry-over ledgers · the retro's standing instructions **in full** · the wiki · any doc repo or hosted system the project names |
+| **0 Inventory (1b)** | the documentation regime | `docs/DOCMAP.md` — registers, single homes, propagation matrix, gate commands, ratchet floors. Absent ⇒ seeded ([`adoption.md`](adoption.md)) |
+| **0 Reconcile (1c)** | intent vs as-built | git (how it *should* be) against the run record (how it *turned out*) |
+| **0 Grill** | the operator | the interview — every answer checked against the harvest, which is what makes it checkable rather than confident |
+| **1 Docs study** | external library/API contracts | `context7:resolve-library-id` → `context7:query-docs`; web search where it cannot resolve. **Never from recall** |
+| **2 Brainstorm** | what is already settled | the brief (scope, constraints, done-criteria) + the codebase. Re-asking what the grill answered is this stage's most common waste |
+| **3 Spec** | the approved design + the UX chain | stage-2 design · `docs/ux/{foundation,flows,screens,scenarios}.md` (UI only) · the Figma canonical record in `docs/ux/foundation.md` → *Design tooling* · `DOCMAP.md` for where a settled contract is recorded |
+| **4 Plan** | the spec and the frozen list | the spec's locked contracts and **Global Constraints** · the brief's REQ ids (the gate is a set comparison against them) |
+| **5 Dev** | one task at a time | the plan task · the spec's Global Constraints, copied verbatim · host test/lint commands · the brief's branch policy. **A subagent reads only its own file-based brief** — that is the whole of its context |
+| **6 Tests** | the host's runner | `CLAUDE.md`/`AGENTS.md` → *Lint + test*, else detection ([`conventions.md`](conventions.md)) |
+| **7 Lint + deploy** | the host's lint and deploy path, and the authorization | host conventions · the brief's autonomy sweep, where a standing go must name target **and** preconditions |
+| **8 Post-deploy** | where health lives | the brief's autonomy sweep (app name, endpoint, workflow) |
+| **9 Docs + registers** | two different lists | the stage-0 **source ledger** (what this run *read*) **and** `DOCMAP.md`'s **propagation matrix** (what this run *owes*). They are not the same list, and the gap between them is where documentation rots |
+| **10 Acceptance** | everything the run produced | the brief's REQ table · the carry-over ledger **in full** · plan task statuses · `git log` · the final suite output · stage-8 notes · stage-9 changes · `docs/ux/scenarios.md` + `/ux-lint` for UI |
+
+### Project-saved rules, and where each one binds
+
+These are the files a **host project** owns that change how a run behaves. An agent
+that has not read them is running the pipeline's defaults, not this project's.
+
+| Rule file | What it binds | Read at | Enforced at |
+|---|---|---|---|
+| `CLAUDE.md` / `AGENTS.md` | commands, deploy path, house rules, which docs exist and where | 0 | 6–10 |
+| `docs/DOCMAP.md` | the decision home, each fact's single home, the propagation matrix, the gate and its ratchet floors | 0 (1b) | 9 |
+| `docs/superpowers/retro.md` | standing instructions — the rules no check can decide. Capped at ten, **read in full**, stamped the moment one fires | 0 | pruned at 10 |
+| `specs/<topic>-brief.md` → *Autonomy* | every pre-resolved decision; stages 1→10 **answer from it instead of asking** | 0 | 1–10 |
+| `specs/<topic>-carryover.md` | everything deferred, parked or half-done; appended the moment it is said | all | read in full at 10 |
+| `docs/ux/scenarios.md` | the source of truth for user-facing behaviour (super-ux) | 3 | 3, 7, 9, 10 |
+| `.claude/agent-sync.json` | which registers are guarded, and by whose lease | 0 | every guarded write |
+| the operator's global `CLAUDE.md` | whether a task routes here at all, and the opt-out phrase | before stage 0 | — |
+
+**Precedence when two of them disagree.** For *what is*: code, then host docs and
+ADRs, then the wiki, then memory. For *what should be*: the register outranks the
+code, because a decision not yet built is still the decision — and the gap between
+them is a finding, not a tie-break ([`knowledge-sources.md`](knowledge-sources.md)).
+
 ## Stage → artifact map
 
 | Stage | Writes | Consumed by |