task-pipeline-skill 0.4.0 → 0.5.0

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+## v0.5.0 — 2026-07-20
+
+UX track: scenario-first design for user-facing tasks, built on
+[super-ux](https://github.com/ssheleg/super-ux).
+
+- **Stage 2 (Brainstorm)** now includes a mandatory **UI detection** check —
+  records whether the task touches a user-facing surface (web/mobile/CLI/TUI);
+  the verdict arms the UX track and is part of the stage gate.
+- **Stage 3 (Spec)** gains a conditional **UX track that runs before the spec**
+  (and therefore before any plan): `/ux` setup check → `ux-foundation`
+  (personas, JTBD, **customer journey maps**, user stories) → `ux-scenarios`
+  (usage scenarios drafted + validated per ux-contract v2, traced to
+  foundation). Spec must embed the UX layer: scenario IDs, CJM stages served,
+  applicable UX patterns/quality bars. Gate extended accordingly; super-ux
+  missing on a UI task → install instructions + stop.
+- **Stage 4 (Plan)** gate extended: UI tasks name the scenario ID(s) they
+  implement; DoD includes satisfying them.
+- README (EN + RU): UX track section; super-ux added to prerequisites.
+
 ## v0.4.0 — 2026-07-19
 
 npm installer.

package/README.md

@@ -14,8 +14,8 @@ Each stage gates the next; each names the model to use.
 | # | Stage | Model | Gate |
 |---|---|---|---|
 | 1 | Docs study | Fable | contracts grounded on current docs |
-| 2 | Brainstorm | Fable | design approved |
-| 3 | Spec | Fable | committed + reviewed |
+| 2 | Brainstorm | Fable | design approved; UI verdict recorded |
+| 3 | Spec | Fable | committed + reviewed; UI: scenarios + CJM traced |
 | 4 | Plan | Fable | parallel-ready, DoD per task |
 | 5 | Dev | Opus | tasks DONE, TDD green per task |
 | 6 | Tests | Opus | full suite green, new code covered |
@@ -23,7 +23,17 @@ Each stage gates the next; each names the model to use.
 | 8 | Post-deploy | host | clean boot / honest degradation |
 | 9 | Docs + wiki | host | docs + wiki synced |
 
-## Prerequisite
+## UX track (user-facing tasks)
+
+When a task touches any user-facing surface (web / mobile / CLI / TUI), the spec
+stage runs the [super-ux](https://github.com/ssheleg/super-ux) skills **before any
+plan is written**: `/ux` (setup check) → `ux-foundation` (personas, JTBD,
+**customer journey maps**, user stories) → `ux-scenarios` (usage scenarios
+validated against the base, ux-contract v2). The spec then embeds the UX layer —
+scenario IDs, CJM stages served, applicable UX patterns — and the plan's
+UI tasks carry scenario IDs in their DoD. Scenarios come before interface.
+
+## Prerequisites
 
 **superpowers** — https://github.com/obra/superpowers
 
@@ -32,6 +42,13 @@ Each stage gates the next; each names the model to use.
 /plugin install superpowers@superpowers
 ```
 
+**super-ux** (only for user-facing tasks) — https://github.com/ssheleg/super-ux
+
+```
+/plugin marketplace add ssheleg/super-ux
+/plugin install super-ux@super-ux
+```
+
 ## Install
 
 **Plugin (recommended):**
@@ -89,6 +106,11 @@ docs / wiki) with detection fallbacks, so the skill works in any repo.
 
 - Ни одна стадия не стартует, пока не пройден гейт предыдущей; деплой требует
   зелёного полного прогона тестов и явного «go» оператора.
+- **UX-трек:** для user-facing задач стадия спеки сначала гоняет скиллы
+  [super-ux](https://github.com/ssheleg/super-ux) (`/ux` → `ux-foundation`:
+  персоны, JTBD, CJM → `ux-scenarios`: сценарии использования по контракту
+  ux-contract v2) — до написания плана; спека включает ID сценариев, стадии
+  CJM и применённые UX-паттерны. Сценарии — до интерфейса.
 - Каждая стадия напоминает, какую модель включить (`/model`): 1–4 — Fable,
   5–6 — Opus, 7–9 — наследуется. Это только напоминание — модель переключает
   оператор.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "task-pipeline-skill",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Full-cycle task delivery pipeline orchestrator skill for Claude Code — 9 gated stages (docs, brainstorm, spec, plan, build, tests, deploy, post-deploy, docs/wiki) built on the superpowers skills. This package is the installer CLI.",
   "bin": {
     "task-pipeline": "bin/task-pipeline.js"

package/plugins/task-pipeline/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "task-pipeline",
   "description": "Thin orchestrator that runs a task through the full delivery pipeline: docs study, brainstorm, spec, plan, subagent build, test suite, lint/deploy, post-deploy log check, docs/wiki sync. Built on the superpowers skills; per-stage model reminders; generic-portable.",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "author": { "name": "ssheleg" },
   "homepage": "https://github.com/ssheleg/task-pipeline",
   "repository": "https://github.com/ssheleg/task-pipeline",

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

@@ -18,11 +18,16 @@ If missing → tell the operator to install from **https://github.com/obra/super
 (`/plugin marketplace add obra/superpowers` → `/plugin install superpowers@superpowers`)
 and stop.
 
+For **user-facing tasks** (web/mobile/CLI/TUI) the spec stage additionally requires
+the **super-ux** skills (`ux-foundation`, `ux-scenarios`, `/ux`) —
+**https://github.com/ssheleg/super-ux**. Check only when stage 2 flags UI; if
+missing then → tell the operator to install and stop.
+
 ## How to run
 
 1. Restate the task in one line. Create a **TaskList: one task per stage** (survives
    context loss; lets you resume).
-2. Walk stages 1→8. Before each: **model check** (see `references/model-tiering.md`) —
+2. Walk stages 1→9. Before each: **model check** (see `references/model-tiering.md`) —
    if recommended ≠ current, emit the reminder block and wait for the operator to `/model`.
 3. Do **not** advance until the stage **gate** passes (`references/stages.md`).
 4. Cross-cutting, every stage: task tracker + conventional commits per host
@@ -35,8 +40,8 @@ and stop.
 | # | Stage | Model | Invoke | Gate |
 |---|---|---|---|---|
 | 1 | Docs study | Fable | `context7` (resolve-library-id → get-library-docs) / `context7-docs` | contracts grounded on fetched docs |
-| 2 | Brainstorm | Fable | `superpowers:brainstorming` | design approved by user |
-| 3 | Spec | Fable | brainstorming writes `docs/superpowers/specs/…-design.md` | committed + user-reviewed |
+| 2 | Brainstorm | Fable | `superpowers:brainstorming` + **UI detection** | design approved; UI verdict recorded |
+| 3 | Spec | Fable | **UI → super-ux first** (`/ux` → `ux-foundation` CJM → `ux-scenarios`), then spec `docs/superpowers/specs/…-design.md` | committed + reviewed; UI: scenarios validated + CJM traced |
 | 4 | Plan | Fable | `superpowers:writing-plans` → `docs/superpowers/plans/…md` | parallel-ready, DoD per task |
 | 5 | Dev | **Opus** | `superpowers:using-git-worktrees` + `superpowers:subagent-driven-development` (TDD) | tasks DONE, TDD green per task |
 | 6 | Tests | **Opus** | host test runner + `superpowers:test-driven-development` | full suite green; new/changed code covered |

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

@@ -15,13 +15,36 @@ must pass before advancing.
 ## 2 — Brainstorm (Fable)
 - **Invoke:** `superpowers:brainstorming`. One question at a time; 2–3 approaches +
   a recommendation; design presented in sections.
-- **GATE:** the user approves the design.
+- **UI detection (mandatory check):** decide whether the task touches any
+  user-facing surface (web, mobile, CLI, TUI — new feature, new screen/command,
+  or a change to user-visible behavior). Record the verdict; it arms the UX
+  track in stage 3.
+- **GATE:** the user approves the design **and** the UI verdict is recorded.
 
-## 3 — Spec (Fable)
-- brainstorming writes the design to
+## 3 — Spec (Fable) — with UX track for user-facing tasks
+- **UX track (runs FIRST when stage 2 flagged UI; skip entirely otherwise).**
+  Requires the **super-ux** skills (`/plugin marketplace add ssheleg/super-ux` →
+  `/plugin install super-ux@super-ux`, or `npx skills add ssheleg/super-ux`);
+  if missing on a UI task → tell the operator to install and stop.
+  1. `/ux` (super-ux entry) — inspects/repairs `docs/ux/` setup in the host project.
+  2. `ux-foundation` — the WHY layer: personas, Jobs to Be Done, **customer
+     journey maps (CJM)**, user stories with Given/When/Then acceptance
+     criteria. Create if missing; update if the feature shifts who/why.
+  3. `ux-scenarios` — draft the feature's usage scenarios and validate them
+     against the existing base per the super-ux format contract
+     (`scenario-format.md`, ux-contract v2): IDs, statuses, `Traces:` to
+     foundation stories/journey stages, edge/error states enumerated.
+- **Spec:** brainstorming writes the design to
   `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` and commits it. Lock all
-  shared contracts (types, schemas, signatures, file layout).
-- **GATE:** spec committed **and** user-reviewed.
+  shared contracts (types, schemas, signatures, file layout). For UI tasks the
+  spec **embeds the UX layer**: links the validated scenario IDs and the CJM
+  stages the feature serves, and states which UX patterns/guides from super-ux
+  apply (per-scenario quality bars, error/empty/loading states, traceability).
+- **GATE:** spec committed **and** user-reviewed; for UI tasks additionally:
+  scenarios validated in `docs/ux/scenarios.md`, CJM/foundation coverage in
+  `docs/ux/foundation.md` (or explicit v1-mode/tiny-project waiver by the
+  operator), and every user-facing spec requirement traces to a scenario ID.
+  No plan (stage 4) starts before this — scenarios come BEFORE interface.
 
 ## 4 — Plan (Fable)
 - **Invoke:** `superpowers:writing-plans` →
@@ -29,7 +52,8 @@ must pass before advancing.
   paths, TDD steps, DoD each, dependency graph + parallel groups, non-overlapping
   file ownership.
 - **GATE:** every spec requirement maps to a task; no placeholders; parallel-group
-  tasks share no files.
+  tasks share no files. For UI tasks: every task building user-facing behavior
+  names the scenario ID(s) it implements, and its DoD includes satisfying them.
 
 ## 5 — Dev (Opus)
 - **Invoke:** `superpowers:using-git-worktrees` (isolate) →