task-pipeline-skill 0.8.1 → 0.10.0

package/CHANGELOG.md

@@ -1,5 +1,50 @@
 # Changelog
 
+## v0.10.0 — 2026-07-25
+
+Review pass — doc drift and a distribution defect found by an adversarial audit.
+
+- **FIX: the stage-0 brief template never reached 3 of 4 install channels.**
+  `templates/brief.md` sat at the repo root, outside the plugin source, so the
+  skills CLI / npx / install.sh installs had no such file while `stages.md` told
+  the agent to seed from it. Moved to
+  `plugins/task-pipeline/skills/task-pipeline/templates/brief.md` — inside the
+  skill dir, so every channel ships it.
+- **FIX: stale super-ux chain in `pipeline.example.json`.** Stage 3 still listed
+  only `ux-foundation` + `ux-scenarios`; it now runs the current chain
+  (`/ux` → `ux-foundation` → **`ux-flows`** → `ux-scenarios` → **`/ux-lint`**),
+  matching SKILL.md and `stages.md`. Stage-4 gate now also names `SCR-` screens.
+- **FIX: README documented the old chain** in both languages, and recommended the
+  skills CLI for Claude Code (which shadows the plugin). Both corrected; multiple
+  agents now shown as repeated `--agent` flags.
+- Description now opens with "Use when …" per canon. `ux-contract` stamp updated
+  v2 → v4. Model tiering moved to the current Opus generation (`claude-opus-5`).
+- README gains npm / CI / license badges.
+
+## v0.9.0 — 2026-07-23
+
+Full structural parity with the sibling `super-ux` per the ssheleg skill canon
+(make-skill): the Cursor channel and a templates dir were the last gaps.
+
+- **Cursor channel.** New `cursor/rules/task-pipeline.mdc` — a self-contained,
+  agent-requested rule (`alwaysApply: false` + a trigger `description`, no external
+  links so it survives being copied into any project) that carries the full
+  intake-grill + 9-stage discipline and the super-ux recommendation. Install
+  globally via `npx skills add ssheleg/task-pipeline --agent cursor --global`, or
+  copy per project into `.cursor/rules/`.
+- **Templates dir.** New `templates/brief.md` — the stage-0 intake-brief skeleton
+  this plugin seeds into `docs/superpowers/specs/…-brief.md` (create-if-absent,
+  never overwrite), plus `templates/README.md` mapping template → destination →
+  stage. Spec/plan and `docs/ux/*` skeletons remain owned by superpowers / super-ux.
+- **Validator + packaging.** The validator now checks every `cursor/rules/*.mdc`
+  has `description` + `alwaysApply` frontmatter and that `templates/brief.md`
+  exists; `package.json` `files` ships `cursor` and `templates`. All prior gates
+  (four-way version sync, config conformance, gate types, release shape, links)
+  retained.
+- **Docs.** README gains a Cursor install block and an "Updating everywhere" table
+  (one channel per agent — the plugin+plain duplicate caveat spelled out);
+  `references/artifacts.md` and stage 0 reference the brief template.
+
 ## v0.8.1 — 2026-07-23
 
 - Docs consistency: the SKILL.md super-ux intro now lists the full current chain

package/README.md

@@ -1,5 +1,9 @@
 # task-pipeline
 
+[![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)
+
 Full-cycle task delivery pipeline orchestrator for **Claude Code**. One skill that
 runs any substantial task through an up-front **intake grill** + **9 gated stages** —
 built on the [superpowers](https://github.com/obra/superpowers) skills.
@@ -20,7 +24,7 @@ use. Every gate is typed — **auto** (the orchestrator verifies it, pass/fail)
 | 0 | Intake grill | Fable | shared understanding reached; brief locked | manual |
 | 1 | Docs study | Fable | contracts grounded on current docs | auto |
 | 2 | Brainstorm | Fable | design approved; UI verdict recorded | manual |
-| 3 | Spec | Fable | committed + reviewed; UI: scenarios + CJM traced | manual |
+| 3 | Spec | Fable | committed + reviewed; UI: super-ux chain validated, linter green | manual |
 | 4 | Plan | Fable | parallel-ready, DoD per task | auto |
 | 5 | Dev | Opus | tasks DONE, TDD green per task | auto |
 | 6 | Tests | Opus | full suite green, new code covered | auto |
@@ -54,7 +58,8 @@ is the **recommended** workflow, detected early in the stage-0 grill. If it's
 installed, task-pipeline uses it; if not, it gives you the install line on the spot.
 The spec stage runs it **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
+`ux-flows` (user flows + `screens.md` UI map, Figma frames) → `ux-scenarios`
+(usage scenarios validated against the base, ux-contract v4) → `/ux-lint` (must pass). 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.
@@ -83,10 +88,13 @@ before interface.
 /plugin install task-pipeline@task-pipeline
 ```
 
-**Any agent via the skills CLI (Claude Code, Cursor, Codex, 70+ agents):**
+**Any agent via the skills CLI (Cursor, Codex, OpenCode, 70+ — not Claude Code,
+use the plugin above):**
 ```
-npx skills add ssheleg/task-pipeline
+npx skills add ssheleg/task-pipeline --agent cursor --agent codex --global
 ```
+(one repeated `--agent` per agent; never include `claude-code` while the plugin is
+installed — the plain copy shadows it)
 
 **npm installer (no clone needed):**
 ```
@@ -97,6 +105,15 @@ npx task-pipeline-skill                   # from the npm registry
 on npm; installs the same skill + `/task-pipeline` command into `~/.claude`,
 idempotent, `--force` to overwrite)
 
+**Cursor:**
+```
+npx skills add ssheleg/task-pipeline --agent cursor --global   # global, or…
+```
+…or per project, copy `cursor/rules/task-pipeline.mdc` into the repo's
+`.cursor/rules/`. Cursor has no global rules directory — use the skills CLI for a
+global install, the `.mdc` for per-project, or paste it into Cursor Settings →
+Rules. The rule is self-contained (no external links), so it works copied anywhere.
+
 **Plain skill:**
 ```
 git clone https://github.com/ssheleg/task-pipeline
@@ -106,6 +123,19 @@ cd task-pipeline && ./install.sh
 command into `~/.claude/commands/`; idempotent — rerun skips existing installs,
 `./install.sh --force` overwrites)
 
+## Updating everywhere
+
+Pick **one** channel per agent (running the plugin and the plain/skills-CLI copy
+on the same Claude Code install yields a duplicate skill).
+
+| Agent / channel | Update |
+|---|---|
+| Claude Code (plugin) | `claude plugin marketplace update task-pipeline` → `claude plugin update task-pipeline@task-pipeline` → restart |
+| Any agent (skills CLI) | `npx skills update task-pipeline --global --yes`; to add: repeated `--agent <name>` (never `claude-code` when the plugin is installed) |
+| Cursor | skills CLI (above) with `--agent cursor`, or re-copy the `.mdc` per project |
+| npm | `npx task-pipeline-skill@latest` / `npx github:ssheleg/task-pipeline` (ephemeral — always latest) |
+| Plain skill | `git pull && ./install.sh --force` |
+
 ## Use
 
 Say *"run this through the pipeline"* / *"полный цикл"* / *"прогони по конвейеру"*,
@@ -165,8 +195,10 @@ canonical artifact layout each stage writes to is fixed in
   (web/mobile/CLI/TUI), [super-ux](https://github.com/ssheleg/super-ux) —
   рекомендуемый воркфлоу, детектится ещё на гриле; если установлен — используется,
   если нет — сразу даётся строка установки. Стадия спеки гоняет `/ux` →
-  `ux-foundation` (персоны, JTBD, CJM) → `ux-scenarios` (сценарии по ux-contract
-  v2) до написания плана; спека включает ID сценариев, стадии CJM и UX-паттерны.
+  `ux-foundation` (персоны, JTBD, CJM) → `ux-flows` (флоу + `screens.md` — карта
+  экранов) → `ux-scenarios` (сценарии, ux-contract v4) → `/ux-lint` (линтер должен
+  быть зелёным) до написания плана; спека включает ID сценариев, `SCR-` экраны,
+  стадии CJM и UX-паттерны.
   Сценарии — до интерфейса.
 - Каждая стадия напоминает, какую модель включить (`/model`): 0–4 — Fable,
   5–6 — Opus, 7–9 — наследуется. Это только напоминание — модель переключает

package/cursor/rules/task-pipeline.mdc

@@ -0,0 +1,56 @@
+---
+description: "task-pipeline: run a substantial task through a disciplined, gated delivery cycle — an intake grill that expands the request, then docs→brainstorm→spec→plan→build→tests→lint/deploy→post-deploy→docs. Apply when the user asks to run a task through the pipeline, the full cycle / полный цикл / прогони по конвейеру, or starts any substantial feature/fix/build."
+alwaysApply: false
+---
+
+# task-pipeline — gated delivery cycle (Cursor)
+
+Self-contained rule (Cursor copies this file into projects — no external links).
+Run a substantial task through an up-front **intake grill + 9 gated stages**. No
+stage advances until its **gate** passes. Each gate is `auto` (verify it yourself,
+pass/fail) or `manual` (wait for the user's explicit go).
+
+## Stage 0 — intake grill (do this FIRST)
+
+A one-line task ("build feature X") is not enough to finish autonomously. Grill the
+user up front, then run the rest without mid-flight questions:
+1. One question per turn — never bundle.
+2. Give a recommended answer with every question (+ one-line rationale).
+3. Explore the codebase before asking — if a search/read answers it, do that.
+4. Walk the decision tree depth-first; ask prerequisite decisions first.
+5. Reconcile contradictions; chase dodges ("decide later" → "latest you can decide
+   and still ship?").
+Stop when shared understanding is reached (every branch answered or explicitly
+deferred) and lock the answers into a short brief the user confirms. Only then start.
+
+## Stages 1→9
+
+1. **Docs study** (auto) — ground every external lib/API on current docs, not recall.
+2. **Brainstorm** (manual) — 2–3 approaches + a recommendation; design approved.
+   Record whether the task touches a user-facing surface (UI verdict).
+3. **Spec** (manual) — write and commit the design; lock shared contracts. For UI
+   tasks, run the UX chain FIRST (see super-ux below) and embed it.
+4. **Plan** (auto) — zero-context tasks, exact paths, TDD steps, DoD each,
+   dependency graph + parallel groups, non-overlapping file ownership.
+5. **Dev** (auto) — isolate (worktree), TDD per task (failing test → minimal impl →
+   green → commit); two-stage review (spec compliance, then code quality).
+6. **Tests** (auto) — full suite green (not just new tests); new/changed code
+   covered; no skip/xfail hiding red.
+7. **Lint + deploy** (manual) — lint clean AND suite green before deploy; deploy is
+   outward → explicit user go.
+8. **Post-deploy** (auto) — tail logs / health-check; clean boot or an honest
+   degradation report (never silent success).
+9. **Docs** (auto) — update module docs/runbooks in the SAME change.
+
+Cross-cutting: track tasks, conventional commits, honest degradation (never claim a
+failed/skipped step succeeded), and get explicit go before any outward/irreversible
+action (deploy, publish, repo create).
+
+## super-ux for user-facing tasks (recommended)
+
+If the task touches any UI (web/mobile/CLI/TUI), the WHY→UI→scenario chain comes
+BEFORE interface code. If super-ux is available, use it: foundation (personas,
+JTBD, customer journey maps, user stories) → flows + screens → scenarios (the
+source of truth) → run its linter. Otherwise still design that chain, get it
+approved, and trace every user-facing requirement to a scenario before building.
+Install (Cursor/Claude/others): `npx skills add ssheleg/super-ux`.

package/package.json

@@ -1,13 +1,14 @@
 {
   "name": "task-pipeline-skill",
-  "version": "0.8.1",
-  "description": "Full-cycle task delivery pipeline orchestrator skill for Claude Code — an intake grill + 9 gated stages (docs, brainstorm, spec, plan, build, tests, deploy, post-deploy, docs/wiki) built on the superpowers skills, with a super-ux UX track for user-facing tasks and toggleable release automation. This package is the installer CLI.",
+  "version": "0.10.0",
+  "description": "Full-cycle task delivery pipeline orchestrator skill for Claude Code \u2014 an intake grill + 9 gated stages (docs, brainstorm, spec, plan, build, tests, deploy, post-deploy, docs/wiki) built on the superpowers skills, with a super-ux UX track for user-facing tasks and toggleable release automation. This package is the installer CLI.",
   "bin": {
     "task-pipeline": "bin/task-pipeline.js"
   },
   "files": [
     "bin",
     "plugins",
+    "cursor",
     "README.md",
     "LICENSE",
     "CHANGELOG.md"

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

@@ -1,7 +1,7 @@
 {
   "name": "task-pipeline",
   "description": "Thin orchestrator: an intake grill expands the task, then docs study, brainstorm, spec, plan, subagent build, tests, lint/deploy, post-deploy log check, docs/wiki sync — typed auto/manual gates, per-stage model reminders, a super-ux UX track for user-facing tasks, and toggleable project-configurable release automation. Built on the superpowers skills; generic-portable.",
-  "version": "0.8.1",
+  "version": "0.10.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

@@ -1,6 +1,6 @@
 ---
 name: task-pipeline
-description: "Orchestrates a task through the full end-to-end delivery pipeline — an up-front intake grill that expands the request into a complete brief, then docs study, brainstorm, spec, plan, subagent-driven build, test suite, lint/deploy, post-deploy log check, and docs/wiki sync — as gated stages built on the superpowers skills. Use when the user wants to run a task through the pipeline, asks for the full cycle / полный цикл / прогони по конвейеру, invokes /task-pipeline, or starts any substantial feature, fix, or build that should follow the disciplined cycle rather than ad-hoc coding. Grills the operator first so the rest runs autonomously; recommends super-ux for any user-facing task; reminds which model to switch to per stage; reads host-project conventions for deploy/docs/wiki so it stays project-agnostic."
+description: "Use when running a substantial task through the full end-to-end delivery pipeline — an up-front intake grill that expands the request into a complete brief, then docs study, brainstorm, spec, plan, subagent-driven build, test suite, lint/deploy, post-deploy log check, and docs/wiki sync — as gated stages built on the superpowers skills. Use when the user wants to run a task through the pipeline, asks for the full cycle / полный цикл / прогони по конвейеру, invokes /task-pipeline, or starts any substantial feature, fix, or build that should follow the disciplined cycle rather than ad-hoc coding. Grills the operator first so the rest runs autonomously; recommends super-ux for any user-facing task; reminds which model to switch to per stage; reads host-project conventions for deploy/docs/wiki so it stays project-agnostic."
 ---
 
 # task-pipeline

package/plugins/task-pipeline/skills/task-pipeline/pipeline.example.json

@@ -8,7 +8,10 @@
       "state": "intake",
       "name": "Intake grill",
       "model": "claude-fable-5",
-      "skills": ["grill-me", "grilling"],
+      "skills": [
+        "grill-me",
+        "grilling"
+      ],
       "gate": {
         "type": "manual",
         "check": "grill the operator one question at a time (recommended answer per question; explore codebase/docs before asking) until shared understanding is reached — every decision branch has a recorded answer or explicit deferral, no open contradictions; UI verdict recorded (arms super-ux); decisions locked into a committed task brief the operator confirms before stage 1"
@@ -19,7 +22,10 @@
       "state": "docs-study",
       "name": "Docs study",
       "model": "claude-fable-5",
-      "skills": ["context7", "context7-docs"],
+      "skills": [
+        "context7",
+        "context7-docs"
+      ],
       "gate": {
         "type": "auto",
         "check": "every contract the design will lock is grounded in fetched docs, not recall; unresolvable libraries are flagged in the spec"
@@ -30,7 +36,9 @@
       "state": "brainstorm",
       "name": "Brainstorm",
       "model": "claude-fable-5",
-      "skills": ["superpowers:brainstorming"],
+      "skills": [
+        "superpowers:brainstorming"
+      ],
       "gate": {
         "type": "manual",
         "check": "the user approves the design AND the UI verdict is recorded (does the task touch a user-facing surface — web/mobile/CLI/TUI? this arms the stage-3 UX track)"
@@ -41,10 +49,15 @@
       "state": "spec",
       "name": "Spec",
       "model": "claude-fable-5",
-      "skills": ["super-ux:ux-foundation", "super-ux:ux-scenarios", "superpowers:brainstorming"],
+      "skills": [
+        "super-ux:ux-foundation",
+        "super-ux:ux-flows",
+        "super-ux:ux-scenarios",
+        "superpowers:brainstorming"
+      ],
       "gate": {
         "type": "manual",
-        "check": "spec committed and user-reviewed with all shared contracts locked; for UI tasks additionally: UX track ran FIRST (/ux -> ux-foundation CJM -> ux-scenarios), scenarios validated in docs/ux/scenarios.md, CJM/foundation coverage present, and every user-facing spec requirement traces to a scenario ID — scenarios come BEFORE interface"
+        "check": "UX track ran FIRST for user-facing tasks (/ux -> ux-foundation CJM -> ux-flows screens -> ux-scenarios -> /ux-lint green); spec committed and user-reviewed; every user-facing requirement traces to a scenario ID"
       }
     },
     {
@@ -52,18 +65,23 @@
       "state": "plan",
       "name": "Plan",
       "model": "claude-fable-5",
-      "skills": ["superpowers:writing-plans"],
+      "skills": [
+        "superpowers:writing-plans"
+      ],
       "gate": {
         "type": "auto",
-        "check": "every spec requirement maps to a task; no placeholders; parallel-group tasks share no files; for UI tasks each user-facing task names the scenario ID(s) it implements and its DoD includes satisfying them"
+        "check": "every spec requirement maps to a task; no placeholders; parallel-group tasks share no files; UI tasks name the scenario ID(s) and SCR- screen(s) they implement in their DoD"
       }
     },
     {
       "id": 5,
       "state": "dev",
       "name": "Dev",
-      "model": "claude-opus-4-8",
-      "skills": ["superpowers:using-git-worktrees", "superpowers:subagent-driven-development"],
+      "model": "claude-opus-5",
+      "skills": [
+        "superpowers:using-git-worktrees",
+        "superpowers:subagent-driven-development"
+      ],
       "gate": {
         "type": "auto",
         "check": "all plan tasks DONE (two-stage review: spec compliance, then code quality); full test suite green"
@@ -73,8 +91,10 @@
       "id": 6,
       "state": "tests",
       "name": "Tests",
-      "model": "claude-opus-4-8",
-      "skills": ["superpowers:test-driven-development"],
+      "model": "claude-opus-5",
+      "skills": [
+        "superpowers:test-driven-development"
+      ],
       "gate": {
         "type": "auto",
         "check": "full suite green (not just new tests); new/changed code covered; no skip/xfail smuggling a red suite past the gate"
@@ -85,7 +105,10 @@
       "state": "lint-deploy",
       "name": "Lint + deploy",
       "model": "inherit",
-      "skills": ["host:lint", "host:deploy"],
+      "skills": [
+        "host:lint",
+        "host:deploy"
+      ],
       "gate": {
         "type": "manual",
         "check": "lint clean and full suite green before deploy; deploy is outward and needs explicit operator go"
@@ -96,7 +119,9 @@
       "state": "post-deploy",
       "name": "Post-deploy",
       "model": "inherit",
-      "skills": ["host:health-check"],
+      "skills": [
+        "host:health-check"
+      ],
       "gate": {
         "type": "auto",
         "check": "clean boot confirmed (no error spike, live subsystems healthy), or an honest degradation report with next steps"
@@ -107,7 +132,10 @@
       "state": "docs-wiki",
       "name": "Docs + wiki",
       "model": "inherit",
-      "skills": ["host:module-docs", "wiki-update"],
+      "skills": [
+        "host:module-docs",
+        "wiki-update"
+      ],
       "gate": {
         "type": "auto",
         "check": "docs in sync with code in the same change; wiki synced; dangling links fixed"

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

@@ -33,7 +33,7 @@ design → plan is traceable at a glance.
 
 | Stage | Writes | Consumed by |
 |---|---|---|
-| 0 Intake | `specs/<topic>-brief.md` | stages 2–4 |
+| 0 Intake | `specs/<topic>-brief.md` (seed from the skill's `templates/brief.md`) | stages 2–4 |
 | 3 Spec | `specs/<topic>-design.md` (+ links `docs/ux/*` for UI) | stage 4 |
 | 4 Plan | `plans/<topic>.md` | stage 5 |
 | 3 UX track | `docs/ux/{foundation,flows,screens,scenarios}.md` | stages 4–9 + `/ux-lint` |
@@ -52,6 +52,8 @@ plugins/task-pipeline/
     pipeline.schema.json                      # generic pipeline contract
     pipeline.example.json                     # this plugin's own flow, as config
     references/{stages,model-tiering,conventions,artifacts,companion-skills}.md
+cursor/rules/task-pipeline.mdc                # Cursor channel (self-contained rule)
+plugins/task-pipeline/skills/task-pipeline/templates/brief.md   # stage-0 skeleton (ships on every channel)
 bin/task-pipeline.js                          # npx installer (package task-pipeline-skill)
 package.json
 install.sh                                    # POSIX installer

package/plugins/task-pipeline/skills/task-pipeline/references/model-tiering.md

@@ -6,7 +6,7 @@ lack one, keep your current model; the pipeline still runs.
 | Stages | Recommended | id |
 |---|---|---|
 | 0–4 (intake grill, docs, brainstorm, spec, plan) | Fable 5 | `claude-fable-5` |
-| 5–6 (subagent dev, tests) | Opus 4.8 | `claude-opus-4-8` |
+| 5–6 (subagent dev, tests) | Opus 5 | `claude-opus-5` |
 | 7–9 (lint/deploy, logs, docs) | inherit current | — |
 
 ## Mechanic

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

@@ -45,8 +45,9 @@ stages/agents/types (see SKILL.md → *Bring your own skills*).
   *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,
-  constraints, assumptions, explicitly-deferred items, done-criteria). Stages
-  2–4 build on this brief.
+  constraints, assumptions, explicitly-deferred items, done-criteria). Seed it from
+  the skill's `templates/brief.md` skeleton — but only when absent, never
+  overwrite an existing brief. Stages 2–4 build on this brief.
 - **GATE (manual):** shared understanding reached — every detected branch has a
   recorded answer or an explicit deferral, no open contradictions, and the
   operator confirms the brief. Stop when a re-scan surfaces no new branches
@@ -88,7 +89,7 @@ stages/agents/types (see SKILL.md → *Bring your own skills*).
      screen + state with wireframe and (Figma on) a Figma frame link.
   4. `ux-scenarios` → `docs/ux/scenarios.md` — the **WHAT** (source of truth for
      behavior): scenarios validated per the format contract (`scenario-format.md`,
-     ux-contract v2) — IDs, statuses, `Traces:` to stories/journey stages/flows,
+     ux-contract v4) — IDs, statuses, `Traces:` to stories/journey stages/flows,
      edge/error states enumerated.
   5. **Run the super-ux linter** (`/ux-lint` or `python3 docs/ux/lint.py`) — it
      must pass: no drift, no orphans, no broken traces or stale Figma links.

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

@@ -0,0 +1,12 @@
+# templates
+
+Skeletons task-pipeline seeds into a host project. Only the **brief** is owned by
+this plugin (it is the stage-0 intake artifact); the spec and plan skeletons come
+from the `superpowers` skills, and the `docs/ux/*` skeletons from `super-ux`.
+
+| Template | Seeded to | Stage |
+|---|---|---|
+| `brief.md` | `docs/superpowers/specs/YYYY-MM-DD-<topic>-brief.md` | 0 — intake grill |
+
+Seeding rule (per the ssheleg canon): create a template copy **only when the
+target is absent**; never overwrite an existing brief.

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

@@ -0,0 +1,35 @@
+# 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`.
+> Every field is a resolved decision or an explicit deferral — no open unknowns.
+
+- **Date:** YYYY-MM-DD
+- **Task (one line):** <what the operator asked for, restated>
+- **UI verdict:** yes / no — does this touch a user-facing surface (web/mobile/CLI/TUI)?
+  If yes, the stage-3 super-ux UX track is armed.
+
+## Scope
+
+- **In scope:** …
+- **Out of scope / explicitly deferred:** … (with the reason and, for deferrals,
+  the latest moment the decision can still be made)
+
+## Users & context
+
+- **Who / for what:** … (personas, the job being done)
+- **Where it runs / constraints:** platform, runtime, data, integrations, limits
+
+## Decisions locked (the grill's output)
+
+| # | Decision | Chosen | Rationale |
+|---|---|---|---|
+| 1 | … | … | … |
+
+## Done-criteria
+
+- Observable, verifiable conditions that mean "this task is finished".
+
+## Open assumptions / risks
+
+- Assumption → how it's validated (or flagged risky-untested).