task-pipeline-skill 1.52.0 → 1.53.0

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

@@ -101,7 +101,7 @@ never that the work was skipped quietly.
   when one is built ([`knowledge-graph.md`](knowledge-graph.md): `graphify query` /
   `affected` / `god-nodes` answer *reach*, which is what grep cannot), `CLAUDE.md`,
   `CONTEXT.md`/ADRs, `docs/` + `docs/ux/`, past pipeline briefs and carry-over
-  ledgers, **the retro's standing instructions and run stamps** (`docs/superpowers/retro.md`,
+  ledgers, **the retro's standing instructions and run stamps** (`<artifacts>/retro.md`,
   read **in full** — ten standing rows and ten stamps, both bounded **by a cap**, and they bind this
   run; stamp each instruction as it fires. Its *Recent log* is **queried** by the
   task's nouns, not read: uncapped narrative inside a binding source is what makes the
@@ -185,7 +185,7 @@ never that the work was skipped quietly.
   now (use it if installed; otherwise give the install line — see SKILL.md
   *Prerequisites*); this arms the stage-3 UX track.
 - **Artifact:** lock the resolved decisions into a **task brief** committed at
-  `docs/superpowers/specs/YYYY-MM-DD-<topic>-brief.md` (scope, users/UI verdict,
+  `<artifacts>/specs/YYYY-MM-DD-<topic>-brief.md` (scope, users/UI verdict,
   constraints, assumptions, explicitly-deferred items, done-criteria) **plus the
   autonomy sweep's per-stage answers and the model decision**. Seed it from
   the skill's `templates/brief.md` skeleton — but only when absent, never
@@ -213,7 +213,7 @@ never that the work was skipped quietly.
   confirms the brief. Stop when a
   re-scan surfaces no new branches (don't grill past diminishing returns;
   reversible calls can be deferred with a note). Only then start stage 1.
-- **The verification ledger is read.** `docs/superpowers/verification.md` — the harvest
+- **The verification ledger is read.** `<artifacts>/verification.md` — the harvest
   quotes **how many rows sit at `never`**, because that is the project's standing
   exposure and stage 0 is where it is cheapest to look ([`verification.md`](verification.md)).
 - **The run ledger is seeded and the header block is printed** — in that order, before
@@ -224,7 +224,7 @@ never that the work was skipped quietly.
   [`progress.md`](progress.md) derives the rail and the iteration counter from the
   `stage:` and `iter:` lines. The header goes out before the interview because a run
   that announces its position only at the end announced it to nobody.
-- **The board is read, or seeded.** `docs/superpowers/backlog.md` ([`backlog.md`](backlog.md)) — its **open count is quoted in the brief**, measured by a command at the top of the run rather than inherited from the last run's report. Absent ⇒ seeded from the template and said so; an empty board and no board are the same thing to work on, and only one of them can be appended to.
+- **The board is read, or seeded.** `<artifacts>/backlog.md` ([`backlog.md`](backlog.md)) — its **open count is quoted in the brief**, measured by a command at the top of the run rather than inherited from the last run's report. Absent ⇒ seeded from the template and said so; an empty board and no board are the same thing to work on, and only one of them can be appended to.
 
 ## 1 — Docs study
 - **Freedom: medium** — which sources to fetch is judgement; grounding contracts on fetched docs is not ([`gates.md`](gates.md) → *Axis C*).
@@ -339,7 +339,7 @@ never that the work was skipped quietly.
   so a run designed a flow, then wrote its strings by taste and picked its values at the
   keyboard — and every gate in the pipeline reported green over both.
 - **Spec:** write the approved design to
-  `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` and commit it. Lock all
+  `<artifacts>/specs/YYYY-MM-DD-<topic>-design.md` and commit it. Lock all
   shared contracts (types, schemas, signatures, file layout). For UI tasks the
   spec **embeds the UX layer**: links the validated scenario IDs, the flows and
   `SCR-` screens, the CJM stages the feature serves, and the UX
@@ -366,7 +366,7 @@ never that the work was skipped quietly.
 ## 4 — Plan
 - **Freedom: low** — the task format is prescribed and the REQ set-comparison is mechanical ([`gates.md`](gates.md) → *Axis C*).
 - **How it runs: [`planning.md`](planning.md)** — built into this skill →
-  `docs/superpowers/plans/YYYY-MM-DD-<topic>.md` (same slug as the brief and the
+  `<artifacts>/plans/YYYY-MM-DD-<topic>.md` (same slug as the brief and the
   spec). Zero-context tasks, exact
   paths, complete code in every step, TDD steps with expected output, DoD each,
   dependency graph + parallel groups, non-overlapping file ownership, and the
@@ -510,7 +510,7 @@ never that the work was skipped quietly.
   its run id** — "CI is green" written without a command behind it prints the same
   whether it looked or not ([`gates.md`](gates.md) → *False success*).
 - **Write the verification row.** One line per REQ this run shipped, into
-  `docs/superpowers/verification.md` ([`verification.md`](verification.md)) — the run,
+  `<artifacts>/verification.md` ([`verification.md`](verification.md)) — the run,
   the tag or commit it went out in, what the gate said, and `Human: never` unless the
   operator confirmed during the run. The verification above already happened; this is
   the only step that makes it answerable **later**, and `never` is a fact rather than a
@@ -581,7 +581,7 @@ never that the work was skipped quietly.
   brief carries.** Both directions: a shipped feature that entered no ledger and a
   ledger row about nothing are different failures ([`verification.md`](verification.md)).
 - **The ledger's open rows are resolved onto the board.** Every carry-over row still
-  `open` leaves with a `B-NNN` id on `docs/superpowers/backlog.md`, and the ledger row
+  `open` leaves with a `B-NNN` id on `<artifacts>/backlog.md`, and the ledger row
   is updated to name it ([`backlog.md`](backlog.md)). Both directions, because they are
   different failures: a ledger row pointing at an id nobody issued, and a board row
   traceable to nothing. Measured before this was built: across the ledgers in
@@ -613,7 +613,7 @@ never that the work was skipped quietly.
 - **How it runs:** built in. Read the brief's REQ table, the carry-over ledger in
   full, the plan's task statuses, git log, the final suite output, stage-8 notes and
   stage-9 doc changes (plus `docs/ux/scenarios.md` + `/ux-lint` for UI tasks). Write
-  `docs/superpowers/specs/YYYY-MM-DD-<topic>-acceptance.md` — one row per REQ,
+  `<artifacts>/specs/YYYY-MM-DD-<topic>-acceptance.md` — one row per REQ,
   status `verified` / `partial` / `deferred` / `dropped`, each with **evidence** (a
   passing test name, `file:line`, a command and its output, or a scenario ID).
   "Done" without evidence is not done: downgrade to `partial` and say so rather
@@ -636,7 +636,7 @@ never that the work was skipped quietly.
   the forgotten one: `git -C <submodule> push`, then
   `git add <submodule> && git commit`.
 - **The retrospective is the run's last act** ([`retrospective.md`](retrospective.md)),
-  written to `docs/superpowers/retro.md` — one file per project, not per run. The
+  written to `<artifacts>/retro.md` — one file per project, not per run. The
   pipeline's gates are good at *this* run and blind across runs: the same class of
   failure can be caught, fixed and forgotten five times and nothing in the flow
   notices it is the same one. So, in this order: **stamp the run first** (one line,
@@ -666,7 +666,7 @@ never that the work was skipped quietly.
   with a floor, neither ever a target ([`gates.md`](gates.md) → *Disclosures*); **the
   retrospective is written — stamped first, then pruned, then the entry; the
   list at or under its cap, every deletion logged in the archive with its commit,
-  entries older than five run stamps rotated into `docs/superpowers/retro/` **and the
+  entries older than five run stamps rotated into `<artifacts>/retro/` **and the
   stamp table itself held to ten — at the eleventh the oldest stamp rotates whole into
   the same archive, and both counts print beside the verdict** (the stamp table is read
   in full at stage 0, so *one line per run* is a slope the prune has to stop), the run

package/plugins/task-pipeline/skills/task-pipeline/templates/README.md

@@ -9,10 +9,10 @@ from `super-ux`.
 
 | Template | Seeded to | Stage |
 |---|---|---|
-| `brief.md` | `docs/superpowers/specs/YYYY-MM-DD-<topic>-brief.md` | 0 — intake grill |
-| `carryover.md` | `docs/superpowers/specs/YYYY-MM-DD-<topic>-carryover.md` | 0 seeds, all stages append, 10 reads |
-| `verification.md` | `docs/superpowers/verification.md` | 8 writes a row per shipped REQ, 10 requires it, a human fills `Human` |
-| `backlog.md` | `docs/superpowers/backlog.md` | 0 seeds when absent, any stage appends, 10 resolves and re-derives |
+| `brief.md` | `docs/evidence/specs/YYYY-MM-DD-<topic>-brief.md` | 0 — intake grill |
+| `carryover.md` | `docs/evidence/specs/YYYY-MM-DD-<topic>-carryover.md` | 0 seeds, all stages append, 10 reads |
+| `verification.md` | `docs/evidence/verification.md` | 8 writes a row per shipped REQ, 10 requires it, a human fills `Human` |
+| `backlog.md` | `docs/evidence/backlog.md` | 0 seeds when absent, any stage appends, 10 resolves and re-derives |
 | `run.md` | `.task-pipeline/run.md` — **git-ignored**, one per run | 0 seeds it, every gate appends a verdict, every repeating pass a `touch:` line |
 | `context.md` | `CONTEXT.md` at the repo root (or per context) | 0 — grill, domain awareness |
 | `adr.md` | `docs/adr/NNNN-<slug>.md` | 0 — grill, hard-to-reverse decisions |
@@ -23,8 +23,8 @@ from `super-ux`.
 | `hygiene.sh` | `scripts/check-hygiene.sh` | 0 seeds it · **5 runs it after every task** · 6 and 9 run it · 10 proves it |
 | `hooks.example.json` | the project's `.claude/settings.json` | 0 — offered, never installed silently |
 | `routing-rule.md` | the operator's `CLAUDE.md` — **offered by `setup`, never written silently** | 0 / `setup` |
-| `retro.md` | `docs/superpowers/retro.md` — **one per project, not per run** | 10 writes (stamp → prune → entry), 0 reads it in full |
-| `retro-archive.md` | `docs/superpowers/retro/YYYY-QN.md` | 10 rotates into it, 0 **queries** it |
+| `retro.md` | `docs/evidence/retro.md` — **one per project, not per run** | 10 writes (stamp → prune → entry), 0 reads it in full |
+| `retro-archive.md` | `docs/evidence/retro/YYYY-QN.md` | 10 rotates into it, 0 **queries** it |
 
 The documentation-track templates (`docmap.md`, `decisions.md`,
 `open-questions.md`, `docgate.sh`) are seeded **together**, and they are useful at

package/plugins/task-pipeline/skills/task-pipeline/templates/backlog.md

@@ -1,6 +1,6 @@
 # Backlog — <project>
 
-> **The board.** One per project, at `docs/superpowers/backlog.md`. Unlike the
+> **The board.** One per project, at `docs/evidence/backlog.md`. Unlike the
 > carry-over ledger, this file is **mutable**: priority is re-derived, state changes,
 > rows close. What may never happen silently is a row *disappearing* — a closed row is
 > marked closed, with the commit that closed it.

package/plugins/task-pipeline/skills/task-pipeline/templates/brief.md

@@ -1,7 +1,7 @@
 # Task brief — <topic>
 
 > Stage-0 intake artifact. The grill fills this in and the operator confirms it
-> before stage 1. Copy to `docs/superpowers/specs/YYYY-MM-DD-<topic>-brief.md`.
+> before stage 1. Copy to `docs/evidence/specs/YYYY-MM-DD-<topic>-brief.md`.
 > Every field is a resolved decision or an explicit deferral — no open unknowns.
 
 - **Date:** YYYY-MM-DD
@@ -58,11 +58,11 @@ source is a recorded decision, an unquoted one is an undetected divergence.
 - **Doc repos / hosted doc systems this project names:** … (or `none`)
 - **Knowledge wiki:** installed / not installed
   ([obsidian-wiki](https://github.com/ar9av/obsidian-wiki); recommended, never a gate)
-- **Retro, in force:** `docs/superpowers/retro.md` — none / N standing instructions
+- **Retro, in force:** `docs/evidence/retro.md` — none / N standing instructions
   (read **in full**, together with the run stamps and the recent-log window; list
   which ones bind this run, and stamp each as it fires **with the commit** — that
   stamp is the only evidence behind stage 10's cold-retirement rule)
-- **Retro archive:** `docs/superpowers/retro/` — **queried** by this task's nouns;
+- **Retro archive:** `docs/evidence/retro/` — **queried** by this task's nouns;
   what it returned: … (or `nothing`)
 - **Code graph:** built / installed-not-built / not installed
   ([graphify](https://github.com/Graphify-Labs/graphify); recommended, never a gate —
@@ -139,7 +139,7 @@ is not neutral — it is a scheduled interruption.
 | 7 Deploy | **Authorization** — standing go, or ask every time? | … |
 | 8 Post-deploy | Where logs / health live (app name, endpoint, workflow) | … |
 | 9 Docs+wiki | Which module docs / runbooks this change updates; wiki sync yes/no; **code-graph refresh yes/no** (`/graphify . --update`); which stale ledger rows get fixed | … |
-| 10 Acceptance | Who signs off; where deferred REQs get tracked (issue tracker / backlog); **retro file** — `docs/superpowers/retro.md` present? which standing instructions bind this run? | … |
+| 10 Acceptance | Who signs off; where deferred REQs get tracked (issue tracker / backlog); **retro file** — `docs/evidence/retro.md` present? which standing instructions bind this run? | … |
 
 > **Deploy authorization has a hard floor.** A standing go counts only if it is
 > **specific** — named target and named preconditions ("staging, once lint and the

package/plugins/task-pipeline/skills/task-pipeline/templates/carryover.md

@@ -1,7 +1,7 @@
 # Carry-over ledger — <topic>
 
 > **Append-only.** Any stage may add a row; nobody edits or deletes one. Committed
-> to `docs/superpowers/specs/YYYY-MM-DD-<topic>-carryover.md` beside the brief, and
+> to `docs/evidence/specs/YYYY-MM-DD-<topic>-carryover.md` beside the brief, and
 > read in full by stage 10 (acceptance).
 >
 > **The rule: deferred out loud is forgotten.** If it isn't written here, it wasn't
@@ -24,7 +24,7 @@
   "Forgot" is a legitimate and useful answer here.
 - **REQ** — the requirement it belongs to, or `—` if it's outside the REQ spine.
 - **Where it lives now** — an issue id, a **board id** (`B-NNN` on
-  `docs/superpowers/backlog.md`), or `dropped` with the operator's agreement. Those are
+  `docs/evidence/backlog.md`), or `dropped` with the operator's agreement. Those are
   the three ways a row is *settled*.
   **Three values are not settled and all three block the stage-10 gate:** `unresolved`,
   `open`, and a bare `backlog` — the last one because it names a place without naming a

package/plugins/task-pipeline/skills/task-pipeline/templates/retro-archive.md

@@ -1,7 +1,7 @@
 # Retro archive — <project> · <YYYY>-Q<N>
 
 **Append-only. Queried, never read in full.** The in-force list
-(`docs/superpowers/retro.md`) is capped at ten and read whole at stage 0; this file
+(`docs/evidence/retro.md`) is capped at ten and read whole at stage 0; this file
 is where entries and retirements go when they age out, so pruning stops losing
 things. Doctrine: `references/retrospective.md`.
 

package/plugins/task-pipeline/skills/task-pipeline/templates/retro.md

@@ -8,7 +8,7 @@ Doctrine: `references/retrospective.md`.
 
 **What stage 0 reads in full:** *Standing instructions*, *Run stamps* and *Recent
 log* — all three are bounded by construction, which is why the cap is not
-negotiable. The **archive** (`docs/superpowers/retro/YYYY-QN.md`) is *queried* by
+negotiable. The **archive** (`docs/evidence/retro/YYYY-QN.md`) is *queried* by
 the task's nouns and never read end to end.
 
 ## Standing instructions (max 10 — in force right now)
@@ -33,7 +33,7 @@ row goes — the cap is not negotiable, ranking is.
 
 ## Recent log — entries from the last five run stamps (newest first)
 
-Older entries and every retirement **move** to `docs/superpowers/retro/YYYY-QN.md`
+Older entries and every retirement **move** to `docs/evidence/retro/YYYY-QN.md`
 at the prune. Moving is not deleting: the archive is append-only and holds the
 incident forever, so pruning the in-force list costs no knowledge. This section
 stays short precisely so that reading it in full at stage 0 stays cheap.