compound-workflow 1.5.0 → 1.6.1

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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "compound-workflow",
3
- "version": "1.5.0",
3
+ "version": "1.6.1",
4
4
  "description": "Clarify -> plan -> execute -> verify -> capture workflow: commands, skills, and agents for Claude Code",
5
5
  "author": {
6
6
  "name": "Compound Workflow"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "compound-workflow",
3
- "version": "1.5.0",
3
+ "version": "1.6.1",
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.5.0",
3
+ "version": "1.6.1",
4
4
  "description": "Clarify → plan → execute → verify → capture. One Install action for Cursor, Claude, and OpenCode.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -364,6 +364,19 @@ function main() {
364
364
  const args = parseArgs(process.argv);
365
365
  const targetRoot = realpathSafe(args.root);
366
366
 
367
+ const genScript = path.join(PACKAGE_ROOT, "scripts", "generate-platform-artifacts.mjs");
368
+ if (fs.existsSync(genScript)) {
369
+ const result = spawnSync(process.execPath, [genScript], {
370
+ cwd: PACKAGE_ROOT,
371
+ stdio: "pipe",
372
+ encoding: "utf8",
373
+ });
374
+ if (result.status !== 0) {
375
+ console.error("Failed to regenerate manifest:", result.stderr || result.error || "unknown");
376
+ process.exit(1);
377
+ }
378
+ }
379
+
367
380
  try {
368
381
  GENERATED_MANIFEST = readGeneratedManifest();
369
382
  PACKAGE_COMMAND_ROOT = GENERATED_MANIFEST.commandRoot;
@@ -833,6 +833,8 @@ Write the complete plan file to `docs/plans/YYYY-MM-DD-<type>-<slug>-plan.md`. T
833
833
 
834
834
  Confirm: "Plan written to docs/plans/[filename]"
835
835
 
836
+ **Auto technical review (when Fidelity is Medium or High):** After writing the plan file, if the declared **Fidelity is Medium or High**, automatically run technical review: run **Task planning-technical-reviewer(plan_path)** when the environment can run the Task, or load the `technical-review` skill so the subagent is used when available. Use the plan path just written. If Fidelity is Low, skip this step; the user can still choose "Technical review" from Post-Generation Options or call `/workflow:tech-review` later.
837
+
836
838
  **Non-interactive mode:** When the invocation is non-interactive (e.g., `workflow:plan` run by automation, CI, or with an explicit non-interactive flag/convention), skip AskQuestion calls and do not present Post-Generation Options. For determinism, the repo should define the flag or convention (e.g., in `AGENTS.md` Repo Config Block or a documented env var). Still **declare** Fidelity, Confidence, Solution scope, Spike evaluation, Spikes needed, Research mode, and Open questions in the required announcement format before writing the plan. Use these defaults when user input is unavailable: fidelity = Medium, confidence = Medium, solution_scope = full_remediation, spike evaluation = not-required unless risky-work triggers are present, spikes needed = n/a when spike evaluation is not required, research mode = local + external for Medium/High risk topics else local only. Proceed directly to writing the plan file and then exit or return the plan path as output.
837
839
 
838
840
  **Required in plan frontmatter:** Add these fields to the plan file:
@@ -0,0 +1,28 @@
1
+ ---
2
+ name: tech-review
3
+ invocation: workflow:tech-review
4
+ description: Run technical review on a plan (technical correctness before build). Optional plan path or latest in docs/plans/.
5
+ argument-hint: "[optional: plan path]"
6
+ ---
7
+
8
+ # /workflow:tech-review
9
+
10
+ Run technical review on a feature approach or plan document. Checks technical alignment with architecture, code standards, and quality before build. Does not edit the plan; use `document-review` after technical review to apply agreed changes.
11
+
12
+ Contract precedence: if this command conflicts with other workflow docs, follow `docs/principles/workflow-baseline-principles.md`, then `src/AGENTS.md`, then this command.
13
+
14
+ ## Inputs
15
+
16
+ - **Plan path (optional):** `$ARGUMENTS` — path to the plan file (e.g. `docs/plans/YYYY-MM-DD-<type>-<slug>-plan.md`).
17
+ - If not provided: use the plan from context, or discover the most recent plan in `docs/plans/` (e.g. by date prefix) or `docs/brainstorms/`.
18
+
19
+ ## Execution
20
+
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.
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
+
25
+ ## Guardrails
26
+
27
+ - Do not modify the plan in this command; technical review is read-only. Apply changes via document-review or user edit.
28
+ - Do not create commits, push branches, or create pull requests.
@@ -23,9 +23,8 @@ Primary execution model: run an independent planning-phase pass first using `pla
23
23
 
24
24
  ## Step 1.5: Independent Fresh-Context Pass (Required)
25
25
 
26
- - If `planning-technical-reviewer` exists under `.agents/agents/review/`, run it on the plan first.
27
- - Treat its blocking findings as pre-build blockers.
28
- - If the agent is not available, explicitly state: "planning-technical-reviewer unavailable; running direct technical review (degraded bias resistance)".
26
+ - Run **Task planning-technical-reviewer(plan_path)** when the environment can run the Task; treat its output as the independent pass and its blocking findings as pre-build blockers.
27
+ - If the Task cannot be run (e.g. no subagent/mcp_task support), explicitly state: "planning-technical-reviewer unavailable; running direct technical review (degraded bias resistance)" and perform the review in-context (load the planning-technical-reviewer agent doc and execute that review in this conversation), then synthesize the verdict.
29
28
 
30
29
  ## Step 1.6: Build Findings Queue (Required)
31
30
 
package/src/AGENTS.md CHANGED
@@ -30,9 +30,10 @@ This `.agents` workspace is portable and command-first.
30
30
  4. `/workflow:review` -> validate quality
31
31
  5. `/workflow:compound` -> capture durable learnings
32
32
 
33
- Optional manual step:
33
+ Optional manual steps:
34
34
 
35
35
  - `/workflow:triage` -> explicitly curate/prioritize backlog items before execution when needed
36
+ - `/workflow:tech-review` -> run technical review on a plan (technical correctness before build); optional plan path
36
37
 
37
38
  Continuous improvement:
38
39
 
@@ -43,9 +44,9 @@ Onboarding:
43
44
 
44
45
  - `/install` -> one action: writes opencode.json, merges AGENTS.md, creates dirs, preserves Repo Config Block (run `npx compound-workflow install` in the project)
45
46
 
46
- This workspace currently implements `brainstorm`, `plan`, `triage`, `work`, `review`, `compound`, and optional QA utilities.
47
+ This workspace currently implements `brainstorm`, `plan`, `triage`, `work`, `review`, `tech-review`, `compound`, and optional QA utilities.
47
48
 
48
- Use the canonical command names (`/workflow:plan`, `/workflow:work`, `/workflow:review`, etc.). This template does not ship aliases.
49
+ Use the canonical command names (`/workflow:plan`, `/workflow:work`, `/workflow:review`, `/workflow:tech-review`, etc.). This template does not ship aliases.
49
50
 
50
51
  ## Contract Precedence
51
52
 
@@ -168,7 +169,7 @@ worktree_bootstrap_notes:
168
169
 
169
170
  ## Implemented Components (Current Scope)
170
171
 
171
- - Commands: `workflow:brainstorm`, `workflow:plan`, `workflow:triage`, `workflow:work`, `workflow:review`, `workflow:compound` (under `.agents/commands/workflow/`), plus `test-browser`, `metrics`, `assess`, `install` (root commands)
172
+ - Commands: `workflow:brainstorm`, `workflow:plan`, `workflow:triage`, `workflow:work`, `workflow:review`, `workflow:tech-review`, `workflow:compound` (under `.agents/commands/workflow/`), plus `test-browser`, `metrics`, `assess`, `install` (root commands)
172
173
  - Skills: `brainstorming`, `document-review`, `technical-review`, `compound-docs` (alias: `compound_doc`), `capture-skill`, `file-todos`, `agent-browser`, `git-worktree`, `process-metrics`, `react-ddd-mvc-frontend`, `xstate-actor-orchestration`, `standards`, `pii-protection-prisma`, `financial-workflow-integrity`, `audit-traceability`, `data-foundations`
173
174
  - Agents:
174
175
  - `repo-research-analyst`
@@ -44,6 +44,11 @@
44
44
  "description": "Review a PR/branch/diff with structured findings. Does not implement fixes unless explicitly requested.",
45
45
  "rel": "workflow/review.md"
46
46
  },
47
+ {
48
+ "id": "workflow:tech-review",
49
+ "description": "Run technical review on a plan (technical correctness before build). Optional plan path or latest in docs/plans/.",
50
+ "rel": "workflow/tech-review.md"
51
+ },
47
52
  {
48
53
  "id": "workflow:triage",
49
54
  "description": "Manual triage command to prioritize todo files into an executable ready queue (priority, dependencies, recommended action)",