task-pipeline-skill 1.4.2 → 1.4.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,22 @@
1
1
  # Changelog
2
2
 
3
+ ## v1.4.4 — 2026-07-30
4
+
5
+ ### Added
6
+ - **`displayName`** ("Task Pipeline") in both manifests — `name` stays kebab-case
7
+ because it namespaces components; the picker shows this instead.
8
+
9
+ ## v1.4.3 — 2026-07-30
10
+
11
+ ### Fixed
12
+ - **`argument-hint` in the slash command was unquoted.** In YAML a bare
13
+ `[a | b]` is a flow sequence, not a string, so the hint parsed as a *list*.
14
+ Found by `claude plugin validate --strict`, the upstream schema checker, which
15
+ now runs in CI on both this plugin and its marketplace manifest.
16
+ - **`homepage` and `repository` sat at the top level of `marketplace.json`,
17
+ where Claude Code does not recognize them.** They are plugin-entry fields;
18
+ moved there, so the values reach the plugin listing instead of being ignored.
19
+
3
20
  ## v1.4.2 — 2026-07-30
4
21
 
5
22
  ### Fixed
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "task-pipeline-skill",
3
- "version": "1.4.2",
3
+ "version": "1.4.4",
4
4
  "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.",
5
5
  "bin": {
6
6
  "task-pipeline": "bin/task-pipeline.js"
@@ -1,7 +1,8 @@
1
1
  {
2
2
  "name": "task-pipeline",
3
+ "displayName": "Task Pipeline",
3
4
  "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.",
4
- "version": "1.4.2",
5
+ "version": "1.4.4",
5
6
  "author": {
6
7
  "name": "ssheleg"
7
8
  },
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  description: Run a task through task-pipeline — an intake grill that expands the request, then docs → brainstorm → spec → plan → build → tests → deploy → post-deploy → docs/wiki → acceptance.
3
- argument-hint: <one-line task description>
3
+ argument-hint: "<one-line task description>"
4
4
  ---
5
5
  Use the `task-pipeline` skill to run the task below through all gated stages —
6
6
  **stage 0 intake grill** → docs study → brainstorm → spec → plan → subagent