compound-workflow 1.6.2 → 1.6.3

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.
Files changed (4) hide show
  1. package/.claude-plugin/plugin.json +1 -1
  2. package/.cursor-plugin/plugin.json +1 -1
  3. package/package.json +1 -1
  4. package/src/.agents/commands/workflow/tech-review.md +2 -1
package/.claude-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "compound-workflow",
3
- "version": "1.6.2",
3
+ "version": "1.6.3",
4
4
  "description": "Clarify -> plan -> execute -> verify -> capture workflow: commands, skills, and agents for Claude Code",
5
5
  "author": {
6
6
  "name": "Compound Workflow"
package/.cursor-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "compound-workflow",
3
- "version": "1.6.2",
3
+ "version": "1.6.3",
4
4
  "description": "Clarify -> plan -> execute -> verify -> capture workflow for Cursor",
5
5
  "author": {
6
6
  "name": "Compound Workflow"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "compound-workflow",
3
- "version": "1.6.2",
3
+ "version": "1.6.3",
4
4
  "description": "Clarify → plan → execute → verify → capture. One Install action for Cursor, Claude, and OpenCode.",
5
5
  "license": "MIT",
6
6
  "repository": {
package/src/.agents/commands/workflow/tech-review.md CHANGED
@@ -19,10 +19,11 @@ Contract precedence: if this command conflicts with other workflow docs, follow
19
19
  ## Execution
20
20
 
21
21
  1. Resolve the plan document (from argument, context, or discovery).
22
- 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.
22
+ 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.
23
23
  3. After technical review, if the user agrees to changes, recommend loading `document-review` to update the plan, then proceed to build when ready.
24
24
 
25
25
  ## Guardrails
26
26
 
27
+ - **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.
27
28
  - Do not modify the plan in this command; technical review is read-only. Apply changes via document-review or user edit.
28
29
  - Do not create commits, push branches, or create pull requests.