compound-workflow 1.7.1 → 1.7.2

package/.cursor-plugin/plugin.json

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

package/package.json

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

package/scripts/install-cli.mjs

@@ -343,10 +343,12 @@ function writePluginManifests(targetRoot, dryRun, isSelfInstall) {
   if (!cursorManifest || !claudeManifest) return;
 
   // Cursor supports full manifest with commands/agents/skills path overrides.
+  // For commands/agents, use .cursor/ directories where symlinks are created
+  // so Cursor can discover them properly. Skills still use source path.
   const cursorOut = {
     ...cursorManifest,
-    commands: `${pathsBase}/commands`,
-    agents: `${pathsBase}/agents`,
+    commands: "./.cursor/commands",
+    agents: "./.cursor/agents",
     skills: `${pathsBase}/skills`,
   };
   // Claude Code only accepts name, description, author in plugin.json.

package/src/.agents/commands/test-browser.md

@@ -6,7 +6,7 @@ argument-hint: "[PR number, branch name, or 'current' for current branch]"
 
 # Browser Test Command
 
-<command_purpose>Run end-to-end browser tests on pages affected by a PR or branch changes using agent-browser CLI.</command_purpose>
+Run end-to-end browser tests on pages affected by a PR or branch changes using agent-browser CLI.
 
 ## CRITICAL: Use agent-browser CLI Only
 

package/src/.agents/commands/workflow-brainstorm.md

@@ -7,8 +7,9 @@ argument-hint: "[feature idea or problem to explore]"
 
 # Brainstorm a Feature or Improvement
 
-**Note: The current year is 2026.** Use this when dating brainstorm
-documents.
+Explore requirements and approaches through collaborative dialogue before planning implementation.
+
+**Note: The current year is 2026.** Use this when dating brainstorm documents.
 
 Brainstorming helps answer **WHAT** to build through collaborative
 dialogue. It precedes `/workflow:plan`, which answers **HOW** to build

package/src/.agents/commands/workflow-plan.md

@@ -7,6 +7,8 @@ argument-hint: "[feature description, bug report, improvement idea, or brainstor
 
 # Create a plan for a new feature or bug fix
 
+Transform feature descriptions into well-structured project plans using an explicit fidelity and confidence model.
+
 ## Introduction
 
 **Note: The current year is 2026.** Use this when dating plans and searching for recent documentation.