goalbuddy 0.2.15 → 0.2.17

package/README.md

@@ -31,10 +31,10 @@ npm i -g goalbuddy
 Then restart Codex and invoke the installed skill:
 
 ```text
-$goalbuddy
+$goal-prep
 ```
 
-`$goalbuddy` prepares the board and prints the `/goal` command to run next. It does not start `/goal` automatically.
+`$goal-prep` prepares the GoalBuddy board and prints the `/goal` command to run next. It does not start `/goal` automatically.
 
 ## Why GoalBuddy Exists
 
@@ -122,7 +122,7 @@ npx goalbuddy --codex-home /path/to/.codex
 
 ## Run A Goal
 
-After `$goalbuddy` creates or repairs the board, start the run with the printed command:
+After `$goal-prep` creates or repairs the board, start the run with the printed command:
 
 ```text
 /goal Follow docs/goals/<slug>/goal.md.
@@ -172,6 +172,7 @@ npx goalbuddy extend
 npx goalbuddy extend github-pr-workflow
 npx goalbuddy extend install github-pr-workflow --dry-run
 npx goalbuddy extend install --all --dry-run
+npx goalbuddy extend install --all
 ```
 
 `goalbuddy extend` shows available extensions plus local install state, activation state, credential requirements, safe-by-default status, and missing environment variables.

package/goalbuddy/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: goalbuddy
-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.
+name: goal-prep
+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.
 ---
 
-# GoalBuddy
+# Goal Prep
 
-`$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.
+`$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.
 
 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.
 
@@ -19,14 +19,14 @@ raw user intent -> intake compiler -> discovery/plan validation/execution board
 
 There are two different modes:
 
-- `$goalbuddy`: prepare intake, `goal.md`, `state.yaml`, and the starter `/goal` command, then stop.
+- `$goal-prep`: prepare intake, `goal.md`, `state.yaml`, and the starter `/goal` command, then stop.
 - `/goal Follow docs/goals/<slug>/goal.md.`: execute the board, including Scout/Judge/Worker work.
 
-This boundary is strict. `$goalbuddy` is not a lightweight `/goal`; it is a board compiler.
+This boundary is strict. `$goal-prep` is not a lightweight `/goal`; it is a board compiler.
 
-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.
+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.
 
-Allowed `$goalbuddy` actions:
+Allowed `$goal-prep` actions:
 
 - ask diagnostic intake questions and wait when required;
 - 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:
 - print exactly `/goal Follow docs/goals/<slug>/goal.md.`;
 - ask whether to start `/goal`, refine the board, or stop.
 
-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`.
+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`.
 
 ## Intake Compiler
 
@@ -125,7 +125,7 @@ If the raw input is detailed and already contains a plan, the first board task s
 
 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.
 
-## What `$goalbuddy` Does
+## What `$goal-prep` Does
 
 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.
 
@@ -157,7 +157,7 @@ Do not:
 
 ## `/goal` Default Bias: Users Want Work Done
 
-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.
+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.
 
 Unless the user explicitly asks for planning only, treat a `/goal` run as a request for work to happen.
 

package/goalbuddy/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
-  display_name: "GoalBuddy"
-  short_description: "Diagnose intent before making reliable goal boards."
-  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."
+  display_name: "Goal Prep"
+  short_description: "Prepare GoalBuddy boards before running /goal."
+  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."
 policy:
   allow_implicit_invocation: true

package/internal/cli/goal-maker.mjs

@@ -19,10 +19,12 @@ const __dirname = dirname(fileURLToPath(import.meta.url));
 const packageRoot = resolve(__dirname, "../..");
 const canonicalProductName = "GoalBuddy";
 const canonicalCliName = "goalbuddy";
-const canonicalSkillName = "goalbuddy";
+const pluginName = "goalbuddy";
+const canonicalSkillName = "goal-prep";
+const canonicalSkillDirectory = "goalbuddy";
 const legacyCliName = "goal-maker";
 const legacySkillName = "goal-maker";
-const skillSource = join(packageRoot, canonicalSkillName);
+const skillSource = join(packageRoot, canonicalSkillDirectory);
 const packageInfo = JSON.parse(readFileSync(join(packageRoot, "package.json"), "utf8"));
 const defaultCodexHome = process.env.CODEX_HOME || join(homedir(), ".codex");
 const defaultCatalogUrl = "https://raw.githubusercontent.com/tolibear/goalbuddy/main/extend/catalog.json";
@@ -364,7 +366,7 @@ Default source:
 
 function installPlugin() {
   const source = optionValue("--source") || "tolibear/goalbuddy";
-  const pluginSource = join(packageRoot, "plugins", canonicalSkillName);
+  const pluginSource = join(packageRoot, "plugins", pluginName);
   const pluginManifestPath = join(pluginSource, ".codex-plugin", "plugin.json");
   if (!existsSync(pluginManifestPath)) {
     throw new Error(`Plugin manifest not found: ${pluginManifestPath}`);
@@ -384,7 +386,7 @@ function installPlugin() {
 
   const report = {
     installed: true,
-    plugin: `${canonicalSkillName}@${canonicalSkillName}`,
+    plugin: `${pluginName}@${pluginName}`,
     version: pluginManifest.version,
     codex_home: codexHome(),
     marketplace_source: source,
@@ -404,16 +406,20 @@ function installPlugin() {
   console.log("");
   console.log("Restart Codex, then use:");
   console.log(`  $${canonicalSkillName}`);
+  console.log("");
+  console.log("Optional extensions:");
+  console.log(`  npx ${canonicalCliName} extend`);
+  console.log(`  npx ${canonicalCliName} extend install --all`);
 }
 
 function pluginCacheRoot(version) {
-  return join(codexHome(), "plugins", "cache", canonicalSkillName, canonicalSkillName, version);
+  return join(codexHome(), "plugins", "cache", pluginName, pluginName, version);
 }
 
 function enablePluginConfig() {
   const configPath = join(codexHome(), "config.toml");
   mkdirSync(dirname(configPath), { recursive: true });
-  const header = `[plugins."${canonicalSkillName}@${canonicalSkillName}"]`;
+  const header = `[plugins."${pluginName}@${pluginName}"]`;
   const existing = existsSync(configPath) ? readFileSync(configPath, "utf8") : "";
   const updated = upsertTomlEnabled(existing, header);
   writeFileSync(configPath, updated);
@@ -794,7 +800,7 @@ function extendDoctor() {
 }
 
 function installedSkillRoot() {
-  return join(codexHome(), "skills", canonicalSkillName);
+  return join(codexHome(), "skills", canonicalSkillDirectory);
 }
 
 function legacyInstalledSkillRoot() {
@@ -1087,7 +1093,7 @@ function printInstallReport(report) {
 
   console.log("");
   console.log("Next:");
-  console.log("  $goalbuddy");
+  console.log(`  $${canonicalSkillName}`);
   console.log(`  ${canonicalCliName} extend`);
   console.log(`  ${legacyCliName} remains a temporary compatibility alias.`);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "goalbuddy",
-  "version": "0.2.15",
+  "version": "0.2.17",
   "description": "Turn open-ended Codex goals into a GoalBuddy Scout/Judge/Worker board with receipts, verification, and optional extensions.",
   "type": "module",
   "bin": {

package/plugins/goalbuddy/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "goalbuddy",
-  "version": "0.2.15",
+  "version": "0.2.17",
   "description": "Turn broad Codex work into verified GoalBuddy boards with Scout, Judge, Worker, receipts, and optional extensions.",
   "author": {
     "name": "tolibear",
@@ -36,9 +36,7 @@
     "privacyPolicyURL": "https://github.com/tolibear/goalbuddy#privacy",
     "termsOfServiceURL": "https://github.com/tolibear/goalbuddy#license",
     "defaultPrompt": [
-      "Prepare a GoalBuddy board for this goal",
-      "Audit this GoalBuddy board and continue safely",
-      "Install GoalBuddy extensions and verify setup"
+      "$goal-prep prepare a GoalBuddy board for this goal"
     ],
     "brandColor": "#2563EB",
     "composerIcon": "./assets/goalbuddy-icon.svg",

package/plugins/goalbuddy/README.md

@@ -1,6 +1,6 @@
 # GoalBuddy Codex Plugin
 
-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.
+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.
 
 ## What It Contains
 

package/plugins/goalbuddy/skills/goalbuddy/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: goalbuddy
-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.
+name: goal-prep
+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.
 ---
 
-# GoalBuddy
+# Goal Prep
 
-`$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.
+`$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.
 
 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.
 
@@ -19,14 +19,14 @@ raw user intent -> intake compiler -> discovery/plan validation/execution board
 
 There are two different modes:
 
-- `$goalbuddy`: prepare intake, `goal.md`, `state.yaml`, and the starter `/goal` command, then stop.
+- `$goal-prep`: prepare intake, `goal.md`, `state.yaml`, and the starter `/goal` command, then stop.
 - `/goal Follow docs/goals/<slug>/goal.md.`: execute the board, including Scout/Judge/Worker work.
 
-This boundary is strict. `$goalbuddy` is not a lightweight `/goal`; it is a board compiler.
+This boundary is strict. `$goal-prep` is not a lightweight `/goal`; it is a board compiler.
 
-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.
+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.
 
-Allowed `$goalbuddy` actions:
+Allowed `$goal-prep` actions:
 
 - ask diagnostic intake questions and wait when required;
 - 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:
 - print exactly `/goal Follow docs/goals/<slug>/goal.md.`;
 - ask whether to start `/goal`, refine the board, or stop.
 
-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`.
+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`.
 
 ## Intake Compiler
 
@@ -125,7 +125,7 @@ If the raw input is detailed and already contains a plan, the first board task s
 
 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.
 
-## What `$goalbuddy` Does
+## What `$goal-prep` Does
 
 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.
 
@@ -157,7 +157,7 @@ Do not:
 
 ## `/goal` Default Bias: Users Want Work Done
 
-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.
+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.
 
 Unless the user explicitly asks for planning only, treat a `/goal` run as a request for work to happen.
 

package/plugins/goalbuddy/skills/goalbuddy/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
-  display_name: "GoalBuddy"
-  short_description: "Diagnose intent before making reliable goal boards."
-  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."
+  display_name: "Goal Prep"
+  short_description: "Prepare GoalBuddy boards before running /goal."
+  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."
 policy:
   allow_implicit_invocation: true