opencode-ship 1.1.4 → 1.1.5

package/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 All notable changes to `opencode-ship` are recorded here.
 
+## 1.1.5 — `ship-plan` is product-only
+
+> Branch: `feat/1.1.5-ship-plan-prompt`.
+
+- **`ship-plan` prompt is product-only.** `1.1.4` shipped the `ship-plan` primary agent with a generic "ask clarifying questions when tradeoffs need the user's call" prompt and a "tell the user the file path and ask for confirmation before any edits" step. Both leaked workflow concerns into the chat: the model asked "open GitHub issues 0–6 or first Task 0 (commit /final)", "use this Tab (Build is for implementation)", and surfaced permission-glob internals ("`docs/superpowers/plans/` is deny; allowlist is `.opencode/plans/*.md`"). The Plan tab is the **product** half of the workflow; the user is there to talk about the product, not be taught the workflow. The rewrite replaces those lines with a strict contract: the prompt is allowed to ask only product questions (scope, UX, who it is for, what done looks like) and one final product question ("does the plan match the product you want?") before stopping. The prompt never asks how to run the work (issues vs Task N, subagent vs inline, Tab / Build, `ship-deliver`, "what next"), never mentions permission globs / deny lists / allowlists, never creates GitHub issues, never claims OpenCode's native `plan_exit`, and never offers to implement.
+- **Handoff is a file, not a chat menu.** The Plan tab writes `.opencode/plans/<​filename>.md` and stops. A later Build session is told `implement this plan <path>` (or `implement issue N` for the Issue path). The Plan tab does not offer "which approach?" or "subagent vs inline" — those are upstream Superpowers choices that ship does not copy. If a PR needs `Closes #N`, that issue is created by Build (`delivery_issue`), not by Plan.
+- **Subagent dispatch is internal.** `ship-plan` keeps its `task: explore` / `general` allowlist so it can dispatch read-only investigators and write scratch notes, but the prompt no longer asks the user whether to use subagents. The decision is made by the planning agent itself from the size of the request.
+- **`tests/package/neutral-consumer.test.mjs` regression.** The post-init probe now asserts the new prompt lines are present and the old workflow-leaking lines are absent. The 1.1.3 stale-record removal path is unchanged, so `opencode-ship update` from prior 1.1.x installs still cleans the leftover `*` wildcards the same way it did before this release.
+
 ## 1.1.4 — `ship-plan` primary planning agent
 
 > Branch: `feat/1.1.4-ship-plan`.

package/README.md

@@ -2,7 +2,7 @@
 
 > npm-distributed OpenCode installer and delivery plugin: a single command materialises the lifecycle plugin, reviewer/verifier agents, and skills into any consumer repository, with a recoverable lock and never silently overwrites managed files.
 >
-> **Status:** `1.1.4` is on `npm dist-tag latest` and adds a write-capable `ship-plan` primary planning agent. OpenCode's built-in lowercase `plan` Tab is now disabled by the installer (the native experimental Plan mode is env-only and cannot be activated from a repo-local install); `ship-plan` writes Markdown only under `.opencode/plans/*.md` and never touches source files. `1.1.3` supersedes the `1.1.2 stabilization` line by dropping the broken `permission: { "*": "deny" }` wildcard and adding a stale-pointer removal path so `update` cleans the orphan key on the first run. The `1.1.0` tag is immutable. Consumers of `opencode-delivery@0.1.x` should run `pnpm dlx opencode-ship@latest init` from the same checkout; migration recognises the legacy artifacts and adopts them when their bytes match.
+> **Status:** `1.1.5` is on `npm dist-tag latest` and tightens the `ship-plan` primary planning agent so the Plan tab is product-only: it asks about the product, writes `.opencode/plans/*.md`, and stops. It never asks the user how to run the work (issues vs Task N, subagent vs inline, Tab / Build, `ship-deliver`), never mentions permission globs, and never offers to implement. From 1.1.4 `ship-plan` is the write-capable planning agent; OpenCode's built-in lowercase `plan` Tab is disabled. `1.1.3` supersedes the `1.1.2 stabilization` line by dropping the broken `permission: { "*": "deny" }` wildcard and adding a stale-pointer removal path so `update` cleans the orphan key on the first run. The `1.1.0` tag is immutable. Consumers of `opencode-delivery@0.1.x` should run `pnpm dlx opencode-ship@latest init` from the same checkout; migration recognises the legacy artifacts and adopts them when their bytes match.
 >
 > Consumers should use `opencode-ship@1.1.0` (or `@latest`) until `1.1.1` ships. The previous `1.0.0` is on `next`; consumers who pinned to `1.0.x` will continue to receive updates on that channel.
 

package/THIRD_PARTY_NOTICES.md

@@ -1,6 +1,6 @@
 # Third-Party Notices
 
-`opencode-ship@1.1.4` ships the complete Matt Pocock and Superpowers
+`opencode-ship@1.1.5` ships the complete Matt Pocock and Superpowers
 methodology under the MIT license, plus the Ship-owned installer,
 plugin, agents, and skills. The complete immutable pin list is in
 `vendor/sources.json`; the upstream snapshots are under

package/assets/agents/ship-plan.md

@@ -35,32 +35,36 @@ permission:
 
 # Ship Plan
 
-You are the primary planning agent for this repo. Use this Tab (Build is for implementation).
+You are the primary planning agent. You talk about the product. You never talk about the workflow.
 
 ## What you do
 
-1. Read the user's request and any context files they cite (`@file`).
-2. Explore the codebase with `bash` (read-only git / ls / cat / gh issue / gh pr) and `task explore` agents. Never `cat` secrets.
-3. Ask clarifying questions through `question` when tradeoffs need the user's call.
-4. Write your plan to a single Markdown file under `.opencode/plans/<filename>.md`. Filename: lowercase, dashes, no spaces, ends in `.md` (e.g. `2026-08-20-customer-final-ux.md`).
-5. Tell the user the file path and ask for confirmation before any edits after the first write.
+1. Read the user's request and any `@file` context they cite.
+2. Explore with read-only bash (git / ls / cat / gh issue view / gh pr view) and `task explore` / `task general`. Never `cat` secrets. You decide when to dispatch those subagents; never ask the user whether to use them.
+3. Ask product questions only, one per turn via `question`: scope, UX, who it is for, what done looks like. When you must choose, recommend in one sentence.
+4. Write the plan to `.opencode/plans/<​filename>.md`. Filename: lowercase, dashes, no spaces, ends in `.md` (e.g. `2026-08-20-customer-final-ux.md`).
+5. Tell the user the file path. Ask one question: whether the plan matches the product they want. Then stop.
 
 ## What you never do
 
-- Never edit source files, configs, tests, or anything outside `.opencode/plans/*.md`.
+- Never edit anything outside `.opencode/plans/*.md`.
 - Never run mutating bash (`git commit`, `git push`, `npm install`, `rm`, `pnpm add`, …).
-- Never claim you have OpenCode's native `plan_exit` workflow. This is a replacement for the read-only native Plan Tab, not the experimental one.
-- Never invoke `task plan` or `task build`. Build runs the plan, not you.
+- Never ask how to run the work: no GitHub issues vs Task N, no Tab / Build, no subagent vs inline, no `ship-deliver`, no "what next".
+- Never mention permission globs, deny lists, allowlists, or why a path was denied.
+- Never create GitHub issues. A later Build session does that if a PR needs `Closes #N`.
+- Never claim OpenCode's native `plan_exit`. This is a replacement for the read-only native Plan Tab, not the experimental one.
+- Never invoke `task plan` or `task build`. Build runs the plan, in a different session.
+- Never offer to implement.
 
 ## Style
 
-- Write for the cheap builder model that will execute the plan. Be concrete: file paths, function names, the exact commit messages you'll commit to.
+- Write for a later session that will be told `implement this plan <path>`. Be concrete: file paths, function names, the exact commit messages.
 - Prefer small, vertical slices over big-bang rewrites.
-- Quote the source lines you'll touch.
-- When you must choose, recommend and justify in one sentence. Don't enumerate "alternatives" in the file.
+- Quote the source lines you will touch.
+- Pick one approach in the file; do not enumerate alternatives.
 
 ## Hard rules
 
-- One question per turn via `question`. Don't batch.
+- One question per turn via `question`. Product only.
 - If a write fails, surface the error verbatim. Do not retry silently.
-- Don't claim a file is written until `bash` confirms it.
+- Do not claim a file is written until `bash` confirms it.

package/dist/cli.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-// opencode-ship CLI v1.1.4
+// opencode-ship CLI v1.1.5
 var __defProp = Object.defineProperty;
 var __getOwnPropNames = Object.getOwnPropertyNames;
 var __esm = (fn, res) => function __init() {
@@ -110,7 +110,7 @@ import { fileURLToPath as fileURLToPath2 } from "node:url";
 var PACKAGE_VERSION, TEMPLATE_SET;
 var init_version = __esm({
   "src/version.js"() {
-    PACKAGE_VERSION = "1.1.4";
+    PACKAGE_VERSION = "1.1.5";
     TEMPLATE_SET = `v${PACKAGE_VERSION}`;
   }
 });
@@ -5249,7 +5249,7 @@ async function assembleLock({ repoRoot, plan, lock, configPlan, rootPlan, profil
     manager: {
       schemaVersion: CURRENT_LOCK_SCHEMA,
       name: "opencode-ship",
-      version: "1.1.4",
+      version: "1.1.5",
       templateSet: TEMPLATE_SET_ID,
       profile: resolvedProfile,
       appliedAt: (/* @__PURE__ */ new Date()).toISOString(),

package/dist/core.js

@@ -1,4 +1,4 @@
-// opencode-ship/core v1.1.4
+// opencode-ship/core v1.1.5
 
 // src/adapter.js
 import { readFile, writeFile, mkdir, rename } from "node:fs/promises";

package/dist/plugin.js

@@ -1,4 +1,4 @@
-// opencode-ship v1.1.4
+// opencode-ship v1.1.5
 var __defProp = Object.defineProperty;
 var __getOwnPropNames = Object.getOwnPropertyNames;
 var __esm = (fn, res) => function __init() {
@@ -19328,7 +19328,7 @@ function selectRuntimeAdapter({ config: config2, shipAdapter, legacyAdapter }) {
 import { readFileSync as readFileSync4, existsSync as existsSync27 } from "node:fs";
 import { dirname as dirname12, resolve as resolve21 } from "node:path";
 import { fileURLToPath } from "node:url";
-var PACKAGE_VERSION = "1.1.4";
+var PACKAGE_VERSION = "1.1.5";
 var TEMPLATE_SET = `v${PACKAGE_VERSION}`;
 
 // src/plugin.js

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-ship",
-  "version": "1.1.4",
+  "version": "1.1.5",
   "private": false,
   "description": "npm-distributed OpenCode installer that materializes the delivery plugin, reviewer/verifier agents, skills, ship config and lock into any consumer repository.",
   "license": "MIT",