compound-workflow 1.9.1 → 1.9.2

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.
package/README.md CHANGED
@@ -68,6 +68,8 @@ Log session outcomes and spot trends. `/metrics` records a single session. `/ass
68
68
 
69
69
  **`/test-browser`** — Browser-level validation of affected routes. Useful for UI changes where automated tests aren't enough.
70
70
 
71
+ **`/setup-agents`** — Tailor `AGENTS.md` to this project. Detects your stack and installed harnesses, curates the Skill Index, and prompts for anything it can't infer. Re-run whenever harnesses or skills change.
72
+
71
73
  **`/install`** — Re-run setup. Safe to run again after updating the package or adding a new harness.
72
74
 
73
75
  ---
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "compound-workflow",
3
- "version": "1.9.1",
3
+ "version": "1.9.2",
4
4
  "description": "Clarify → plan → execute → verify → capture. One Install action for Cursor, Claude, and OpenCode.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -70,25 +70,43 @@ From these, infer:
70
70
  | `format_command` | `scripts.format` in package.json; prettier config presence |
71
71
  | `dev_server_url` | vite config `server.port`; default `http://localhost:5173` for Vite, `http://localhost:3000` for others |
72
72
  | `worktree_install_command` | `package-lock.json` → `npm ci`; `yarn.lock` → `yarn install`; `pnpm-lock.yaml` → `pnpm install` |
73
+ | `default_branch` | `git symbolic-ref refs/remotes/origin/HEAD` → strip `refs/remotes/origin/`; fallback `main` |
74
+ | `project_tracker` | `.github/` exists → `github`; else `none` |
75
+ | `worktree_dir` | default `.worktrees` |
76
+ | `worktree_copy_files` | glob `.env*` in repo root, excluding `.env.example` and `.env.sample` |
73
77
 
74
- For each value, state whether it was detected or assumed.
78
+ For each value, state whether it was detected or defaulted.
75
79
 
76
80
  ---
77
81
 
78
- ## Phase 2: Prompt for Missing or Undetectable Values
82
+ ## Phase 2: Confirm the Proposed Config
79
83
 
80
- Ask for any values that could not be detected. Ask one at a time.
84
+ Do not prompt field-by-field. Show the resolved config from Phase 1 as a single block and ask one question.
81
85
 
82
- Required:
86
+ **Update mode:** start from the values already in `AGENTS.md`. Only overwrite with a Phase 1 detection when the existing value is empty or clearly stale (e.g. references a command that no longer exists in `package.json`). Flag overrides in the proposed block so the user can see what changed.
83
87
 
84
- - `default_branch` — cannot be reliably detected; ask (suggest `main`)
85
- - `project_tracker` — ask: `github`, `linear`, or none
86
- - `dev_server_url` — confirm detected value or ask
87
- - `worktree_dir` — suggest `.worktrees`
88
- - `worktree_copy_files` — ask which env/config files should be copied into new worktrees (e.g. `.env.local`)
89
- - `harnesses` — show detected list from Phase 1; confirm or correct
88
+ Output format:
90
89
 
91
- **Update mode only:** Show the current values and ask: "These values are already configured — confirm, update, or skip each?"
90
+ ```
91
+ Proposed AGENTS.md config:
92
+
93
+ default_branch: <value> [detected|default|existing]
94
+ project_tracker: <value> [detected|default|existing]
95
+ dev_server_url: <value> [detected|default|existing]
96
+ test_command: <value> [detected|existing]
97
+ test_fast_command: <value> [detected|existing|omit]
98
+ lint_command: <value> [detected|existing|omit]
99
+ typecheck_command: <value> [detected|existing|omit]
100
+ format_command: <value> [detected|existing|omit]
101
+ worktree_dir: <value> [default|existing]
102
+ worktree_install_command: <value> [detected|existing]
103
+ worktree_copy_files: [<files>] [detected|existing]
104
+ harnesses: [<dirs>] [detected]
105
+
106
+ Accept, or reply with `<key>: <value>` lines to override. Blank line accepts.
107
+ ```
108
+
109
+ One round-trip. If the user accepts, proceed to Phase 3. If they override fields, apply the overrides and proceed — do not re-confirm.
92
110
 
93
111
  ---
94
112