compound-workflow 1.6.1 → 1.6.3

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "compound-workflow",
-  "version": "1.6.1",
+  "version": "1.6.3",
   "description": "Clarify -> plan -> execute -> verify -> capture workflow: commands, skills, and agents for Claude Code",
   "author": {
     "name": "Compound Workflow"

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "compound-workflow",
-  "version": "1.6.1",
+  "version": "1.6.3",
   "description": "Clarify -> plan -> execute -> verify -> capture workflow for Cursor",
   "author": {
     "name": "Compound Workflow"

package/README.md

@@ -24,18 +24,37 @@ flowchart LR
 
 ## Get Started
 
+**1. Install the package**
+
 ```bash
 npm install compound-workflow
 ```
 
-`npm install` adds the package and automatically configures your repo (`AGENTS.md`, required directories, and native OpenCode wiring).
-If your package manager skips lifecycle scripts, run `npx compound-workflow install` manually.
+**2. Automatic setup**
+
+The package’s `postinstall` script runs and configures your repo: `AGENTS.md`, standard directories, and OpenCode wiring. No separate npx step is needed.
+
+**3. If lifecycle scripts were skipped**
+
+If your package manager didn’t run postinstall, run once:
+
+```bash
+npx compound-workflow install
+```
+
+**4. After updating the package**
+
+To get the latest commands and wiring (e.g. after `npm update compound-workflow` or a new release), run install again so your project’s `opencode.json` is refreshed:
+
+```bash
+npx compound-workflow install
+```
 
-Install configures:
+**What gets configured**
 
-- Workflow template content in `AGENTS.md`
-- Standard workspace directories for plans/todos/docs
-- `opencode.json` managed entries that reference `node_modules/compound-workflow/src/.agents/*`
+- Workflow template in `AGENTS.md`
+- Standard workspace directories (plans, todos, docs)
+- `opencode.json` managed entries pointing at `node_modules/compound-workflow/src/.agents/*`
 
 ## Breaking Change (2.0.0)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "compound-workflow",
-  "version": "1.6.1",
+  "version": "1.6.3",
   "description": "Clarify → plan → execute → verify → capture. One Install action for Cursor, Claude, and OpenCode.",
   "license": "MIT",
   "repository": {

package/scripts/install-cli.mjs

@@ -14,11 +14,11 @@ const __dirname = path.dirname(fileURLToPath(import.meta.url));
 function usage(exitCode = 0) {
   const msg = `
 Usage:
-  npx compound-workflow install [--root <projectDir>] [--dry-run] [--no-config]
+  (automatic) npm install compound-workflow   # runs install via postinstall; no npx needed
+  (manual)    npx compound-workflow install [--root <projectDir>] [--dry-run] [--no-config]
 
-Native-only install: writes opencode.json (loads from package), merges AGENTS.md,
-creates standard docs/todos directories, and prompts for Repo Config Block
-(unless --no-config).
+Install writes opencode.json (from package), merges AGENTS.md, creates standard
+docs/todos directories, and prompts for Repo Config Block (unless --no-config).
 
   --root <dir>  Project directory (default: cwd)
   --dry-run     Print planned changes only
@@ -366,6 +366,7 @@ function main() {
 
   const genScript = path.join(PACKAGE_ROOT, "scripts", "generate-platform-artifacts.mjs");
   if (fs.existsSync(genScript)) {
+    console.log("[compound-workflow] Regenerating manifest from package source...");
     const result = spawnSync(process.execPath, [genScript], {
       cwd: PACKAGE_ROOT,
       stdio: "pipe",

package/scripts/postinstall.mjs

@@ -57,7 +57,7 @@ function run() {
 
   if (result.status !== 0) {
     console.warn(
-      "[compound-workflow] automatic setup failed; run `npx compound-workflow install` in your project."
+      "[compound-workflow] automatic setup failed; re-run `npm install compound-workflow` or run `npx compound-workflow install` in your project."
     );
   }
 }

package/src/.agents/commands/workflow/tech-review.md

@@ -19,10 +19,11 @@ Contract precedence: if this command conflicts with other workflow docs, follow
 ## Execution
 
 1. Resolve the plan document (from argument, context, or discovery).
-2. Load the `technical-review` skill and run it on that plan. The skill runs **Task planning-technical-reviewer(plan_path)** when the environment can run the Task, then synthesizes the verdict and findings queue.
+2. **Run technical review as a subagent (mandatory when supported).** Load the `technical-review` skill and run it on that plan. You **must** attempt the independent pass via a subagent first: run **Task planning-technical-reviewer(plan_path)** (e.g. `mcp_task` with subagent_type and the plan path). Do **not** perform the planning-technical-reviewer pass in-context unless the environment cannot run the Task; if you fall back, you **must** state "planning-technical-reviewer unavailable; running direct technical review (degraded bias resistance)". After the subagent (or fallback) pass, synthesize the verdict and findings queue.
 3. After technical review, if the user agrees to changes, recommend loading `document-review` to update the plan, then proceed to build when ready.
 
 ## Guardrails
 
+- **Subagent mandatory when available.** You must run the planning-technical-reviewer pass as a subagent (Task / mcp_task) when the environment supports it. Do not run in-context unless the environment cannot run the Task; if you do, disclose the degraded mode.
 - Do not modify the plan in this command; technical review is read-only. Apply changes via document-review or user edit.
 - Do not create commits, push branches, or create pull requests.