luckiest-co 1.0.8 → 1.0.10

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
       "name": "luckiest",
       "source": "./",
       "description": "Plan, go, finish, plus bundled free Luckiest skills that work in Claude Code, web chat, and Cowork.",
-      "version": "0.1.8",
+      "version": "0.1.11",
       "author": { "name": "Luckiest" }
     }
   ]

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "luckiest",
   "description": "Plan, go, finish. Guided planning, progress dashboards, and your luckiest.co tribe inside Claude Code.",
-  "version": "0.1.10",
+  "version": "0.1.11",
   "author": { "name": "Luckiest" }
 }

package/bin/install.js

@@ -75,6 +75,8 @@ if (hasHelp) {
     ${cyan}-l, --local${reset}               Install locally (to ./.claude in current directory)
     ${cyan}-c, --config-dir <path>${reset}   Specify custom Claude config directory
     ${cyan}--sync-only${reset}               Skip install, only sync owned skills from luckiest.co
+    ${cyan}--hook${reset}                    Enable skill usage tracking without prompting
+    ${cyan}--no-hook${reset}                 Skip it (and remove it if a past install added it)
     ${cyan}-h, --help${reset}                Show this help message
 
   ${yellow}Examples:${reset}
@@ -210,6 +212,9 @@ async function syncSkills() {
     console.log(`  ${green}✓${reset} Removed duplicate commands/luckiest (plugin marketplace already provides them)`);
   }
 
+  nudgeStaleInstall(globalDir);
+  nudgeUsageHook(globalDir);
+
   const key = readSavedKey();
   if (!key) {
     console.log(`  ${dim}No luckiest.co connection key saved yet. Run ${cyan}npx luckiest-co${dim} and paste one to sync your owned skills.${reset}`);
@@ -448,6 +453,77 @@ async function shouldRegisterHook() {
   });
 }
 
+// Identifies our hook entry across installs even when the absolute path changed.
+const isOurHookEntry = (entry) =>
+  (entry?.hooks || []).some((h) => String(h?.command || '').includes('report-skill-usage.mjs'));
+
+function usageHookRegistered(claudeDir) {
+  try {
+    const settings = JSON.parse(fs.readFileSync(path.join(claudeDir, 'settings.json'), 'utf8'));
+    return (settings.hooks?.PostToolUse || []).some(isOurHookEntry);
+  } catch {
+    return false;
+  }
+}
+
+/**
+ * Tell, don't act. --sync-only runs unattended at session start, so there's no
+ * terminal to ask at and registering there would mean silently editing
+ * settings.json on a call the user never typed. Instead, say the tracking is off
+ * once and let them opt in deliberately. Silent when it's already handled, so
+ * this adds nothing to the common session-start path.
+ */
+function nudgeUsageHook(globalClaudeDir) {
+  if (hasMarketplacePlugin(globalClaudeDir)) return; // plugin registers its own
+  if (usageHookRegistered(globalClaudeDir)) return;
+  console.log(`  ${dim}Skill usage tracking is off. Run ${cyan}npx luckiest-co@latest --hook${dim} to turn it on.${reset}`);
+}
+
+/**
+ * Numeric semver-ish compare. Returns >0 when a is newer than b.
+ * String compare would read "0.1.10" as older than "0.1.9", which is exactly
+ * the version pair this shipped on.
+ */
+function compareVersions(a, b) {
+  const pa = String(a).split('.').map((n) => parseInt(n, 10) || 0);
+  const pb = String(b).split('.').map((n) => parseInt(n, 10) || 0);
+  for (let i = 0; i < Math.max(pa.length, pb.length); i += 1) {
+    const diff = (pa[i] || 0) - (pb[i] || 0);
+    if (diff !== 0) return diff;
+  }
+  return 0;
+}
+
+function readPluginVersion(root) {
+  try {
+    return JSON.parse(fs.readFileSync(path.join(root, '.claude-plugin', 'plugin.json'), 'utf8')).version || null;
+  } catch {
+    return null;
+  }
+}
+
+/**
+ * Tell people when their installed copy is behind.
+ *
+ * Both update paths are pull-based, so someone who installed once can sit on an
+ * old copy indefinitely with nothing to tell them. Sync runs every session, and
+ * `npx luckiest-co@latest` always fetches the newest package, so the version
+ * this process is running from is by definition current — comparing it against
+ * the copy on disk needs no server call.
+ *
+ * Silent when current, when nothing is installed to compare against, or when
+ * the marketplace plugin is in charge (that copy updates through Claude's own
+ * plugin menu, not this installer).
+ */
+function nudgeStaleInstall(globalClaudeDir) {
+  if (hasMarketplacePlugin(globalClaudeDir)) return;
+  const installed = readPluginVersion(globalClaudeDir);
+  const current = readPluginVersion(path.join(__dirname, '..'));
+  if (!installed || !current) return;
+  if (compareVersions(current, installed) <= 0) return;
+  console.log(`  ${dim}Your Luckiest install is ${cyan}v${installed}${dim}, latest is ${cyan}v${current}${dim}. Run ${cyan}npx luckiest-co@latest${dim} to update.${reset}`);
+}
+
 /**
  * Register the PostToolUse(Skill) telemetry hook in the user's settings.json.
  *
@@ -464,9 +540,6 @@ async function shouldRegisterHook() {
 function registerUsageHook(claudeDir, globalClaudeDir, consented) {
   const hookPath = path.join(claudeDir, 'hooks', 'report-skill-usage.mjs');
   const settingsPath = path.join(claudeDir, 'settings.json');
-  // Identifies our entry across installs even when the absolute path changed.
-  const isOurs = (entry) =>
-    (entry?.hooks || []).some((h) => String(h?.command || '').includes('report-skill-usage.mjs'));
 
   let settings = {};
   if (fs.existsSync(settingsPath)) {
@@ -481,7 +554,7 @@ function registerUsageHook(claudeDir, globalClaudeDir, consented) {
 
   settings.hooks = settings.hooks || {};
   const existing = Array.isArray(settings.hooks.PostToolUse) ? settings.hooks.PostToolUse : [];
-  const others = existing.filter((e) => !isOurs(e));
+  const others = existing.filter((e) => !isOurHookEntry(e));
   const hadOurs = others.length !== existing.length;
 
   // Declining is also an instruction to remove a hook a past install added.

package/commands/finish.md

@@ -4,6 +4,33 @@ description: Wrap up, what shipped, what changed, what's next.
 
 Read `references/vocabulary.md` first and follow it for all output in this command: plain language, no em dashes, no internal terms, one next-step recommendation at the end.
 
+Asking the user a question: this command tells you to use the AskUserQuestion tool
+so the user can click instead of typing. That tool only exists in Claude Code. In
+web chat and Cowork it is not there, and waiting for it will stall the command.
+
+So, every time this command says to use AskUserQuestion:
+
+- If the tool is available, use it exactly as written.
+- If it is not, ask the same question in plain chat as a numbered list of the
+  same options, and tell the user to reply with a number or type their own
+  answer. Treat a typed answer the same as the "Other" free-text choice.
+
+The options, their order, and their wording stay the same either way. Only the
+delivery changes. Never skip a question, never answer it on the user's behalf,
+and never merge several questions into one just because they are text.
+
+For example, "Here's your plan, good to go?" with options "Good to go" and
+"Make changes" becomes:
+
+```
+Here's your plan, good to go?
+
+1. Good to go
+2. Make changes
+
+Reply with a number, or tell me what to change.
+```
+
 ## Step 1: Check that everything is done
 
 Derive the project key as described in `references/project-key.md`. Pass this same `project` value on both luckiest plan tool calls in this command (`status` here and `finish` in Step 3), so you close this project's plan and not another one.

package/commands/go.md

@@ -4,6 +4,33 @@ description: Run your plan, one task at a time, checked as it goes.
 
 Read `references/vocabulary.md` first and follow it for all output in this command: plain language, no em dashes, no internal terms, one next-step recommendation at the end.
 
+Asking the user a question: this command tells you to use the AskUserQuestion tool
+so the user can click instead of typing. That tool only exists in Claude Code. In
+web chat and Cowork it is not there, and waiting for it will stall the command.
+
+So, every time this command says to use AskUserQuestion:
+
+- If the tool is available, use it exactly as written.
+- If it is not, ask the same question in plain chat as a numbered list of the
+  same options, and tell the user to reply with a number or type their own
+  answer. Treat a typed answer the same as the "Other" free-text choice.
+
+The options, their order, and their wording stay the same either way. Only the
+delivery changes. Never skip a question, never answer it on the user's behalf,
+and never merge several questions into one just because they are text.
+
+For example, "Here's your plan, good to go?" with options "Good to go" and
+"Make changes" becomes:
+
+```
+Here's your plan, good to go?
+
+1. Good to go
+2. Make changes
+
+Reply with a number, or tell me what to change.
+```
+
 ## Step 1: Load the plan
 
 Derive the project key as described in `references/project-key.md`. Pass this same `project` value on every luckiest plan tool call in this command (`status`, `apply`, `verify`, `pause`), so you run this project's plan and not another one.

package/commands/plan.md

@@ -4,6 +4,33 @@ description: Plan your next piece of work. Guided questions, then a plan Claude
 
 Read `references/vocabulary.md` first and follow it for all output in this command: plain language, no em dashes, no internal terms, one next-step recommendation at the end.
 
+Asking the user a question: this command tells you to use the AskUserQuestion tool
+so the user can click instead of typing. That tool only exists in Claude Code. In
+web chat and Cowork it is not there, and waiting for it will stall the command.
+
+So, every time this command says to use AskUserQuestion:
+
+- If the tool is available, use it exactly as written.
+- If it is not, ask the same question in plain chat as a numbered list of the
+  same options, and tell the user to reply with a number or type their own
+  answer. Treat a typed answer the same as the "Other" free-text choice.
+
+The options, their order, and their wording stay the same either way. Only the
+delivery changes. Never skip a question, never answer it on the user's behalf,
+and never merge several questions into one just because they are text.
+
+For example, "Here's your plan, good to go?" with options "Good to go" and
+"Make changes" becomes:
+
+```
+Here's your plan, good to go?
+
+1. Good to go
+2. Make changes
+
+Reply with a number, or tell me what to change.
+```
+
 ## Step 1: Gather context
 
 Check whether `.luckiest/BRIEF.md` exists in the current project. If it exists, read it and use it as context for the interview below (what they're building, who it's for, what winning looks like). If it does not exist, continue without it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luckiest-co",
-  "version": "1.0.8",
+  "version": "1.0.10",
   "description": "Luckiest for Claude Code: plan, go, finish. Your luckiest.co skills and tribe, inside Claude.",
   "bin": {
     "luckiest-co": "./bin/install.js"