goalbuddy 0.2.14 → 0.2.16

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.
@@ -11,7 +11,7 @@
11
11
  "path": "./plugins/goalbuddy"
12
12
  },
13
13
  "policy": {
14
- "installation": "AVAILABLE",
14
+ "installation": "INSTALLED_BY_DEFAULT",
15
15
  "authentication": "ON_INSTALL"
16
16
  },
17
17
  "category": "Coding"
package/README.md CHANGED
@@ -22,20 +22,20 @@ GoalBuddy is a local Codex companion for work that is too broad to trust to a si
22
22
  npx goalbuddy
23
23
  ```
24
24
 
25
- Then invoke the installed skill inside Codex:
25
+ Or install it globally:
26
26
 
27
- ```text
28
- $goalbuddy
27
+ ```bash
28
+ npm i -g goalbuddy
29
29
  ```
30
30
 
31
- `$goalbuddy` prepares the board and prints the `/goal` command to run next. It does not start `/goal` automatically.
32
-
33
- For native Codex plugin install instead of the skill-only installer:
31
+ Then restart Codex and invoke the installed skill:
34
32
 
35
- ```bash
36
- npx goalbuddy plugin install
33
+ ```text
34
+ $goal-prep
37
35
  ```
38
36
 
37
+ `$goal-prep` prepares the GoalBuddy board and prints the `/goal` command to run next. It does not start `/goal` automatically.
38
+
39
39
  ## Why GoalBuddy Exists
40
40
 
41
41
  Long Codex goals drift. A request like "improve this project" can turn into unbounded edits, stale verification, and premature completion claims.
@@ -78,17 +78,18 @@ The default agents are installed with the skill:
78
78
 
79
79
  ## Install And Check Readiness
80
80
 
81
- Install or refresh the Codex skill and bundled agents:
81
+ Install and enable the native Codex plugin:
82
82
 
83
83
  ```bash
84
84
  npx goalbuddy
85
- npx goalbuddy update
85
+ npm i -g goalbuddy
86
86
  ```
87
87
 
88
- Install and enable the native Codex plugin:
88
+ Use the skill-only fallback if your Codex build does not support plugins:
89
89
 
90
90
  ```bash
91
- npx goalbuddy plugin install
91
+ npx goalbuddy install
92
+ npx goalbuddy update
92
93
  ```
93
94
 
94
95
  Native Codex `/goal` is still an under-development Codex feature. Before relying on the printed command, confirm your local Codex runtime is logged in and has goals enabled:
@@ -114,14 +115,14 @@ npx goalbuddy doctor
114
115
  Use a non-default Codex home:
115
116
 
116
117
  ```bash
117
- npx goalbuddy install --codex-home /path/to/.codex
118
+ npx goalbuddy --codex-home /path/to/.codex
118
119
  ```
119
120
 
120
- `install`, `update`, and `doctor` also support `--json` when an agent or script needs structured output.
121
+ `plugin install`, `install`, `update`, and `doctor` also support `--json` when an agent or script needs structured output.
121
122
 
122
123
  ## Run A Goal
123
124
 
124
- After `$goalbuddy` creates or repairs the board, start the run with the printed command:
125
+ After `$goal-prep` creates or repairs the board, start the run with the printed command:
125
126
 
126
127
  ```text
127
128
  /goal Follow docs/goals/<slug>/goal.md.
@@ -1,11 +1,11 @@
1
1
  ---
2
- name: goalbuddy
3
- description: Use for broad, long-running, stalled, vague, detailed, planned, or unhealthy Codex work that needs a structured /goal intake, autonomous task discovery, role-tagged Scout/Judge/Worker delegation, one active task, durable receipts, and a PM-owned rolling board that maximizes the chance of a successful goal run.
2
+ name: goal-prep
3
+ description: Goal Prep for GoalBuddy. Use for broad, long-running, stalled, vague, detailed, planned, or unhealthy Codex work that needs a structured /goal intake, autonomous task discovery, role-tagged Scout/Judge/Worker delegation, one active task, durable receipts, and a PM-owned rolling board that maximizes the chance of a successful goal run.
4
4
  ---
5
5
 
6
- # GoalBuddy
6
+ # Goal Prep
7
7
 
8
- `$goalbuddy` prepares a GoalBuddy board. It does not start `/goal` automatically, but the board and starter `/goal` command must be shaped so the next run continues into safe execution by default.
8
+ `$goal-prep` prepares a GoalBuddy board. It does not start `/goal` automatically, but the board and starter `/goal` command must be shaped so the next run continues into safe execution by default.
9
9
 
10
10
  GoalBuddy is for autonomous, long-running Codex work where the PM thread may need to discover the work, define tasks, sequence them, delegate them, execute them, verify them, and keep going without the human decomposing every step.
11
11
 
@@ -19,14 +19,14 @@ raw user intent -> intake compiler -> discovery/plan validation/execution board
19
19
 
20
20
  There are two different modes:
21
21
 
22
- - `$goalbuddy`: prepare intake, `goal.md`, `state.yaml`, and the starter `/goal` command, then stop.
22
+ - `$goal-prep`: prepare intake, `goal.md`, `state.yaml`, and the starter `/goal` command, then stop.
23
23
  - `/goal Follow docs/goals/<slug>/goal.md.`: execute the board, including Scout/Judge/Worker work.
24
24
 
25
- This boundary is strict. `$goalbuddy` is not a lightweight `/goal`; it is a board compiler.
25
+ This boundary is strict. `$goal-prep` is not a lightweight `/goal`; it is a board compiler.
26
26
 
27
- During a `$goalbuddy` turn, do not perform the user's requested work, even if the work looks read-only, preparatory, or obviously useful. Do not refresh or load named skills, inspect implementation files, browse reference repos, research design inspiration, generate design plans, generate images/assets, run app-specific checks, start servers, or edit product files. Put those actions into Scout, Judge, Worker, or PM tasks for the later `/goal` run.
27
+ During a `$goal-prep` turn, do not perform the user's requested work, even if the work looks read-only, preparatory, or obviously useful. Do not refresh or load named skills, inspect implementation files, browse reference repos, research design inspiration, generate design plans, generate images/assets, run app-specific checks, start servers, or edit product files. Put those actions into Scout, Judge, Worker, or PM tasks for the later `/goal` run.
28
28
 
29
- Allowed `$goalbuddy` actions:
29
+ Allowed `$goal-prep` actions:
30
30
 
31
31
  - ask diagnostic intake questions and wait when required;
32
32
  - create or repair only `docs/goals/<slug>/goal.md`, `docs/goals/<slug>/state.yaml`, and `docs/goals/<slug>/notes/`;
@@ -35,7 +35,7 @@ Allowed `$goalbuddy` actions:
35
35
  - print exactly `/goal Follow docs/goals/<slug>/goal.md.`;
36
36
  - ask whether to start `/goal`, refine the board, or stop.
37
37
 
38
- If the prompt names another skill or tool, such as "use the taste skill", "refresh the taste skill", "look at this repo", "use browser", or "generate assets", record that requirement in the charter and seed tasks. Do not load that skill, browse that repo, or generate those assets during `$goalbuddy`.
38
+ If the prompt names another skill or tool, such as "use the taste skill", "refresh the taste skill", "look at this repo", "use browser", or "generate assets", record that requirement in the charter and seed tasks. Do not load that skill, browse that repo, or generate those assets during `$goal-prep`.
39
39
 
40
40
  ## Intake Compiler
41
41
 
@@ -125,7 +125,7 @@ If the raw input is detailed and already contains a plan, the first board task s
125
125
 
126
126
  The target is not literal certainty. It is the highest practical likelihood of a successful goal run: preserve the user's intent, avoid the likely misfire, pick the earliest responsible phase, require proof, and keep advancing safe work until a final audit proves the full outcome.
127
127
 
128
- ## What `$goalbuddy` Does
128
+ ## What `$goal-prep` Does
129
129
 
130
130
  When invoked directly, run intake first. For vague, strategic, improvement-oriented, or open-ended input, run the diagnostic intake and stop before creating or repairing the board until enough material answers are known. For sufficiently clear, planned, recovery, audit, or explicitly-defaulted input, prepare or repair the board and stop for user choice.
131
131
 
@@ -157,7 +157,7 @@ Do not:
157
157
 
158
158
  ## `/goal` Default Bias: Users Want Work Done
159
159
 
160
- This section applies after the user starts `/goal Follow docs/goals/<slug>/goal.md.` It does not apply to the initial `$goalbuddy` board-preparation turn.
160
+ This section applies after the user starts `/goal Follow docs/goals/<slug>/goal.md.` It does not apply to the initial `$goal-prep` board-preparation turn.
161
161
 
162
162
  Unless the user explicitly asks for planning only, treat a `/goal` run as a request for work to happen.
163
163
 
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "GoalBuddy"
3
3
  short_description: "Diagnose intent before making reliable goal boards."
4
- default_prompt: "Use goalbuddy to run diagnostic intake on my rough or detailed goal. If the goal is vague or improvement-oriented, ask one guided question at a time, surface likely blind spots, and do not create files until intent, proof, scope, and board handling are clear or explicitly defaulted. If it is clear or already planned, prepare or repair goal.md, state.yaml, and notes/, then print the /goal Follow command instead of starting /goal automatically."
4
+ default_prompt: "Use goal-prep to run diagnostic intake on my rough or detailed goal. If the goal is vague or improvement-oriented, ask one guided question at a time, surface likely blind spots, and do not create files until intent, proof, scope, and board handling are clear or explicitly defaulted. If it is clear or already planned, prepare or repair goal.md, state.yaml, and notes/, then print the /goal Follow command instead of starting /goal automatically."
5
5
  policy:
6
6
  allow_implicit_invocation: true
@@ -19,10 +19,12 @@ const __dirname = dirname(fileURLToPath(import.meta.url));
19
19
  const packageRoot = resolve(__dirname, "../..");
20
20
  const canonicalProductName = "GoalBuddy";
21
21
  const canonicalCliName = "goalbuddy";
22
- const canonicalSkillName = "goalbuddy";
22
+ const pluginName = "goalbuddy";
23
+ const canonicalSkillName = "goal-prep";
24
+ const canonicalSkillDirectory = "goalbuddy";
23
25
  const legacyCliName = "goal-maker";
24
26
  const legacySkillName = "goal-maker";
25
- const skillSource = join(packageRoot, canonicalSkillName);
27
+ const skillSource = join(packageRoot, canonicalSkillDirectory);
26
28
  const packageInfo = JSON.parse(readFileSync(join(packageRoot, "package.json"), "utf8"));
27
29
  const defaultCodexHome = process.env.CODEX_HOME || join(homedir(), ".codex");
28
30
  const defaultCatalogUrl = "https://raw.githubusercontent.com/tolibear/goalbuddy/main/extend/catalog.json";
@@ -44,7 +46,7 @@ const command = args[0] === "--help" || args[0] === "-h"
44
46
  ? "help"
45
47
  : args[0] && !args[0].startsWith("-")
46
48
  ? args[0]
47
- : "install";
49
+ : "default";
48
50
  const invokedAs = invokedCommandName();
49
51
 
50
52
  main().catch((error) => {
@@ -55,6 +57,9 @@ main().catch((error) => {
55
57
  async function main() {
56
58
  maybePrintLegacyNotice();
57
59
  switch (command) {
60
+ case "default":
61
+ installPlugin();
62
+ break;
58
63
  case "install":
59
64
  case "update":
60
65
  await installAll();
@@ -133,11 +138,12 @@ function usage() {
133
138
  console.log(`Codex ${canonicalProductName}
134
139
 
135
140
  Usage:
141
+ ${canonicalCliName} [--codex-home <path>] [--json]
142
+ ${canonicalCliName} plugin install [--source <marketplace-source>] [--codex-home <path>] [--json]
136
143
  ${canonicalCliName} install [--codex-home <path>] [--force] [--json]
137
144
  ${canonicalCliName} update [--codex-home <path>] [--json]
138
145
  ${canonicalCliName} agents [--codex-home <path>] [--force]
139
146
  ${canonicalCliName} doctor [--codex-home <path>] [--goal-ready]
140
- ${canonicalCliName} plugin install [--source <marketplace-source>] [--codex-home <path>] [--json]
141
147
  ${canonicalCliName} extend [--catalog-url <url-or-path>] [--kind <kind>] [--json]
142
148
  ${canonicalCliName} extend <id> [--catalog-url <url-or-path>] [--json]
143
149
  ${canonicalCliName} extend install <id> [--catalog-url <url-or-path>] [--dry-run] [--force] [--json]
@@ -145,7 +151,10 @@ Usage:
145
151
  ${canonicalCliName} extend doctor [<id>] [--codex-home <path>] [--json]
146
152
 
147
153
  Default:
148
- ${canonicalCliName} Installs the skill and bundled agent definitions.
154
+ ${canonicalCliName} Installs and enables the native Codex plugin.
155
+
156
+ Skill-only fallback:
157
+ ${canonicalCliName} install Installs the legacy skill payload and bundled agent definitions.
149
158
 
150
159
  Compatibility:
151
160
  ${legacyCliName} remains a temporary alias and prints the new npx command for human-facing use.
@@ -357,7 +366,7 @@ Default source:
357
366
 
358
367
  function installPlugin() {
359
368
  const source = optionValue("--source") || "tolibear/goalbuddy";
360
- const pluginSource = join(packageRoot, "plugins", canonicalSkillName);
369
+ const pluginSource = join(packageRoot, "plugins", pluginName);
361
370
  const pluginManifestPath = join(pluginSource, ".codex-plugin", "plugin.json");
362
371
  if (!existsSync(pluginManifestPath)) {
363
372
  throw new Error(`Plugin manifest not found: ${pluginManifestPath}`);
@@ -377,7 +386,7 @@ function installPlugin() {
377
386
 
378
387
  const report = {
379
388
  installed: true,
380
- plugin: `${canonicalSkillName}@${canonicalSkillName}`,
389
+ plugin: `${pluginName}@${pluginName}`,
381
390
  version: pluginManifest.version,
382
391
  codex_home: codexHome(),
383
392
  marketplace_source: source,
@@ -400,13 +409,13 @@ function installPlugin() {
400
409
  }
401
410
 
402
411
  function pluginCacheRoot(version) {
403
- return join(codexHome(), "plugins", "cache", canonicalSkillName, canonicalSkillName, version);
412
+ return join(codexHome(), "plugins", "cache", pluginName, pluginName, version);
404
413
  }
405
414
 
406
415
  function enablePluginConfig() {
407
416
  const configPath = join(codexHome(), "config.toml");
408
417
  mkdirSync(dirname(configPath), { recursive: true });
409
- const header = `[plugins."${canonicalSkillName}@${canonicalSkillName}"]`;
418
+ const header = `[plugins."${pluginName}@${pluginName}"]`;
410
419
  const existing = existsSync(configPath) ? readFileSync(configPath, "utf8") : "";
411
420
  const updated = upsertTomlEnabled(existing, header);
412
421
  writeFileSync(configPath, updated);
@@ -787,7 +796,7 @@ function extendDoctor() {
787
796
  }
788
797
 
789
798
  function installedSkillRoot() {
790
- return join(codexHome(), "skills", canonicalSkillName);
799
+ return join(codexHome(), "skills", canonicalSkillDirectory);
791
800
  }
792
801
 
793
802
  function legacyInstalledSkillRoot() {
@@ -1080,7 +1089,7 @@ function printInstallReport(report) {
1080
1089
 
1081
1090
  console.log("");
1082
1091
  console.log("Next:");
1083
- console.log(" $goalbuddy");
1092
+ console.log(` $${canonicalSkillName}`);
1084
1093
  console.log(` ${canonicalCliName} extend`);
1085
1094
  console.log(` ${legacyCliName} remains a temporary compatibility alias.`);
1086
1095
  }
@@ -0,0 +1,29 @@
1
+ #!/usr/bin/env node
2
+ import { spawnSync } from "node:child_process";
3
+ import { dirname, join } from "node:path";
4
+ import { fileURLToPath } from "node:url";
5
+
6
+ const __dirname = dirname(fileURLToPath(import.meta.url));
7
+ const cliPath = join(__dirname, "goal-maker.mjs");
8
+ const globalInstall = process.env.npm_config_global === "true"
9
+ || process.env.npm_config_location === "global";
10
+
11
+ if (!globalInstall || process.env.GOALBUDDY_SKIP_POSTINSTALL) {
12
+ process.exit(0);
13
+ }
14
+
15
+ const result = spawnSync(process.execPath, [cliPath, "plugin", "install"], {
16
+ encoding: "utf8",
17
+ env: process.env,
18
+ stdio: "inherit",
19
+ });
20
+
21
+ if (result.status === 0) {
22
+ process.exit(0);
23
+ }
24
+
25
+ console.error("");
26
+ console.error("GoalBuddy installed globally, but Codex plugin setup did not complete.");
27
+ console.error("Run this after Codex is available:");
28
+ console.error(" goalbuddy");
29
+ process.exit(0);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "goalbuddy",
3
- "version": "0.2.14",
3
+ "version": "0.2.16",
4
4
  "description": "Turn open-ended Codex goals into a GoalBuddy Scout/Judge/Worker board with receipts, verification, and optional extensions.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -21,9 +21,10 @@
21
21
  "goalbuddy/templates"
22
22
  ],
23
23
  "scripts": {
24
- "check": "node --check internal/cli/goal-maker.mjs goalbuddy/scripts/*.mjs && node --test internal/test/*.test.mjs",
24
+ "check": "node --check internal/cli/*.mjs goalbuddy/scripts/*.mjs && node --test internal/test/*.test.mjs",
25
25
  "test": "node --test internal/test/*.test.mjs",
26
26
  "pack:dry-run": "npm pack --dry-run",
27
+ "postinstall": "node internal/cli/postinstall.mjs",
27
28
  "publish:check": "node internal/cli/check-publish-version.mjs && npm run pack:dry-run",
28
29
  "prepublishOnly": "node internal/cli/check-publish-version.mjs"
29
30
  },
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "goalbuddy",
3
- "version": "0.2.14",
3
+ "version": "0.2.16",
4
4
  "description": "Turn broad Codex work into verified GoalBuddy boards with Scout, Judge, Worker, receipts, and optional extensions.",
5
5
  "author": {
6
6
  "name": "tolibear",
@@ -36,9 +36,7 @@
36
36
  "privacyPolicyURL": "https://github.com/tolibear/goalbuddy#privacy",
37
37
  "termsOfServiceURL": "https://github.com/tolibear/goalbuddy#license",
38
38
  "defaultPrompt": [
39
- "Prepare a GoalBuddy board for this goal",
40
- "Audit this GoalBuddy board and continue safely",
41
- "Install GoalBuddy extensions and verify setup"
39
+ "$goal-prep prepare a GoalBuddy board for this goal"
42
40
  ],
43
41
  "brandColor": "#2563EB",
44
42
  "composerIcon": "./assets/goalbuddy-icon.svg",
@@ -1,6 +1,6 @@
1
1
  # GoalBuddy Codex Plugin
2
2
 
3
- GoalBuddy packages the canonical `$goalbuddy` skill as a Codex plugin so teams can install the reusable workflow as a plugin while keeping the npm CLI for local setup, doctor checks, and extension management.
3
+ GoalBuddy packages the canonical `$goal-prep` skill as a Codex plugin so teams can install the reusable workflow as a plugin while keeping the npm CLI for local setup, doctor checks, and extension management.
4
4
 
5
5
  ## What It Contains
6
6
 
@@ -19,18 +19,24 @@ npx goalbuddy doctor
19
19
 
20
20
  ## Native Codex Install
21
21
 
22
- Install and enable the plugin with the GoalBuddy CLI:
22
+ Install and enable GoalBuddy:
23
23
 
24
24
  ```bash
25
- npx goalbuddy plugin install
25
+ npx goalbuddy
26
26
  ```
27
27
 
28
- This adds the `tolibear/goalbuddy` marketplace, caches the packaged plugin, and enables `goalbuddy@goalbuddy` for Codex. The npm CLI remains useful for `doctor`, project-local agent setup, and optional GoalBuddy extension management.
28
+ Or install the npm package globally:
29
+
30
+ ```bash
31
+ npm i -g goalbuddy
32
+ ```
33
+
34
+ The marketplace manifest is included for Codex discovery, but current Codex CLI builds only register the marketplace with `codex plugin marketplace add`; the npm CLI also caches and enables the plugin.
29
35
 
30
36
  For local CLI testing before npm publish:
31
37
 
32
38
  ```bash
33
- node internal/cli/goal-maker.mjs install --catalog-url extend/catalog.json
39
+ node internal/cli/goal-maker.mjs --catalog-url extend/catalog.json
34
40
  node internal/cli/goal-maker.mjs doctor
35
41
  ```
36
42
 
@@ -1,11 +1,11 @@
1
1
  ---
2
- name: goalbuddy
3
- description: Use for broad, long-running, stalled, vague, detailed, planned, or unhealthy Codex work that needs a structured /goal intake, autonomous task discovery, role-tagged Scout/Judge/Worker delegation, one active task, durable receipts, and a PM-owned rolling board that maximizes the chance of a successful goal run.
2
+ name: goal-prep
3
+ description: Goal Prep for GoalBuddy. Use for broad, long-running, stalled, vague, detailed, planned, or unhealthy Codex work that needs a structured /goal intake, autonomous task discovery, role-tagged Scout/Judge/Worker delegation, one active task, durable receipts, and a PM-owned rolling board that maximizes the chance of a successful goal run.
4
4
  ---
5
5
 
6
- # GoalBuddy
6
+ # Goal Prep
7
7
 
8
- `$goalbuddy` prepares a GoalBuddy board. It does not start `/goal` automatically, but the board and starter `/goal` command must be shaped so the next run continues into safe execution by default.
8
+ `$goal-prep` prepares a GoalBuddy board. It does not start `/goal` automatically, but the board and starter `/goal` command must be shaped so the next run continues into safe execution by default.
9
9
 
10
10
  GoalBuddy is for autonomous, long-running Codex work where the PM thread may need to discover the work, define tasks, sequence them, delegate them, execute them, verify them, and keep going without the human decomposing every step.
11
11
 
@@ -19,14 +19,14 @@ raw user intent -> intake compiler -> discovery/plan validation/execution board
19
19
 
20
20
  There are two different modes:
21
21
 
22
- - `$goalbuddy`: prepare intake, `goal.md`, `state.yaml`, and the starter `/goal` command, then stop.
22
+ - `$goal-prep`: prepare intake, `goal.md`, `state.yaml`, and the starter `/goal` command, then stop.
23
23
  - `/goal Follow docs/goals/<slug>/goal.md.`: execute the board, including Scout/Judge/Worker work.
24
24
 
25
- This boundary is strict. `$goalbuddy` is not a lightweight `/goal`; it is a board compiler.
25
+ This boundary is strict. `$goal-prep` is not a lightweight `/goal`; it is a board compiler.
26
26
 
27
- During a `$goalbuddy` turn, do not perform the user's requested work, even if the work looks read-only, preparatory, or obviously useful. Do not refresh or load named skills, inspect implementation files, browse reference repos, research design inspiration, generate design plans, generate images/assets, run app-specific checks, start servers, or edit product files. Put those actions into Scout, Judge, Worker, or PM tasks for the later `/goal` run.
27
+ During a `$goal-prep` turn, do not perform the user's requested work, even if the work looks read-only, preparatory, or obviously useful. Do not refresh or load named skills, inspect implementation files, browse reference repos, research design inspiration, generate design plans, generate images/assets, run app-specific checks, start servers, or edit product files. Put those actions into Scout, Judge, Worker, or PM tasks for the later `/goal` run.
28
28
 
29
- Allowed `$goalbuddy` actions:
29
+ Allowed `$goal-prep` actions:
30
30
 
31
31
  - ask diagnostic intake questions and wait when required;
32
32
  - create or repair only `docs/goals/<slug>/goal.md`, `docs/goals/<slug>/state.yaml`, and `docs/goals/<slug>/notes/`;
@@ -35,7 +35,7 @@ Allowed `$goalbuddy` actions:
35
35
  - print exactly `/goal Follow docs/goals/<slug>/goal.md.`;
36
36
  - ask whether to start `/goal`, refine the board, or stop.
37
37
 
38
- If the prompt names another skill or tool, such as "use the taste skill", "refresh the taste skill", "look at this repo", "use browser", or "generate assets", record that requirement in the charter and seed tasks. Do not load that skill, browse that repo, or generate those assets during `$goalbuddy`.
38
+ If the prompt names another skill or tool, such as "use the taste skill", "refresh the taste skill", "look at this repo", "use browser", or "generate assets", record that requirement in the charter and seed tasks. Do not load that skill, browse that repo, or generate those assets during `$goal-prep`.
39
39
 
40
40
  ## Intake Compiler
41
41
 
@@ -125,7 +125,7 @@ If the raw input is detailed and already contains a plan, the first board task s
125
125
 
126
126
  The target is not literal certainty. It is the highest practical likelihood of a successful goal run: preserve the user's intent, avoid the likely misfire, pick the earliest responsible phase, require proof, and keep advancing safe work until a final audit proves the full outcome.
127
127
 
128
- ## What `$goalbuddy` Does
128
+ ## What `$goal-prep` Does
129
129
 
130
130
  When invoked directly, run intake first. For vague, strategic, improvement-oriented, or open-ended input, run the diagnostic intake and stop before creating or repairing the board until enough material answers are known. For sufficiently clear, planned, recovery, audit, or explicitly-defaulted input, prepare or repair the board and stop for user choice.
131
131
 
@@ -157,7 +157,7 @@ Do not:
157
157
 
158
158
  ## `/goal` Default Bias: Users Want Work Done
159
159
 
160
- This section applies after the user starts `/goal Follow docs/goals/<slug>/goal.md.` It does not apply to the initial `$goalbuddy` board-preparation turn.
160
+ This section applies after the user starts `/goal Follow docs/goals/<slug>/goal.md.` It does not apply to the initial `$goal-prep` board-preparation turn.
161
161
 
162
162
  Unless the user explicitly asks for planning only, treat a `/goal` run as a request for work to happen.
163
163
 
@@ -1,6 +1,6 @@
1
1
  interface:
2
2
  display_name: "GoalBuddy"
3
3
  short_description: "Diagnose intent before making reliable goal boards."
4
- default_prompt: "Use goalbuddy to run diagnostic intake on my rough or detailed goal. If the goal is vague or improvement-oriented, ask one guided question at a time, surface likely blind spots, and do not create files until intent, proof, scope, and board handling are clear or explicitly defaulted. If it is clear or already planned, prepare or repair goal.md, state.yaml, and notes/, then print the /goal Follow command instead of starting /goal automatically."
4
+ default_prompt: "Use goal-prep to run diagnostic intake on my rough or detailed goal. If the goal is vague or improvement-oriented, ask one guided question at a time, surface likely blind spots, and do not create files until intent, proof, scope, and board handling are clear or explicitly defaulted. If it is clear or already planned, prepare or repair goal.md, state.yaml, and notes/, then print the /goal Follow command instead of starting /goal automatically."
5
5
  policy:
6
6
  allow_implicit_invocation: true