@benjaminthomas/spec-driven-dev 1.11.1 → 1.11.2

package/README.md

@@ -63,9 +63,11 @@ start a new session and continue where you left off.
 npx @benjaminthomas/spec-driven-dev@latest
 ```
 
-This one command downloads the tool, installs the skills, and sets up the project. It asks its
-questions in your terminal, so run it in a real terminal, not through another tool. If there's no
-terminal to answer in, it says so and uses the detected values.
+This one command downloads the tool, installs the skills, and sets up the project. In a terminal
+window it asks its setup questions there. Run it with `!` inside Claude Code (or any other place
+without a terminal to answer in) and it installs the skills for the AI tools it finds, then tells
+you to say **"run spec-setup"**, which asks the same questions in the chat. It never writes the
+settings file from guesses.
 
 > **Why not `npm install -g`?** npm doesn't let a package ask questions while it installs, and an
 > install doesn't know which project it's for. That's why setup is a separate step you run inside
@@ -579,8 +581,9 @@ STP-123" or "ship it" picks the right skill.
 Update to 1.5.1 or later (`npx @benjaminthomas/spec-driven-dev@latest --version`). Earlier versions
 crashed on Node 14 or 16, which nvm often switches to inside older projects, and wrote a config
 silently when there was no terminal. Now it runs on Node 14+. With no terminal to answer in (a `!`
-command in Claude Code, an editor task, piped input), it stops, changes nothing, and tells you to run
-it in a terminal window or pass flags such as `--layout=multi-repo --repos=…`.
+command in Claude Code, an editor task, piped input), it installs the skills and hands the questions
+to your AI tool: say "run spec-setup" there. `spec-driven-dev setup` on its own still needs a
+terminal, or flags such as `--layout=multi-repo --repos=…`.
 
 **Setup didn't ask me about repos.**
 It only asks about repos for a multi-repo or monorepo layout. If it detected `single`, type
@@ -802,7 +805,7 @@ plugin/evals/                 `claude plugin eval` cases
   1. Increase `version` in both `package.json` and `plugin/.claude-plugin/plugin.json` (the check fails if
      they differ).
   2. Add a `CHANGELOG.md` entry, then commit and push.
-  3. Tag the release and push the tag: `git tag v1.11.1 && git push origin v1.11.1`.
+  3. Tag the release and push the tag: `git tag v1.11.2 && git push origin v1.11.2`.
   4. Watch the **publish** run in the repo's Actions tab. When it's green, the new version is on
      npm. Claude Code plugin users get it from the marketplace once the commit is on `main`.
 

package/bin/cli.mjs

@@ -48,13 +48,19 @@ if (flag("version") || flag("v")) {
 // No terminal to answer in (e.g. `!` in Claude Code, an IDE task, a pipe) and nothing passed explicitly:
 // stop rather than write a config from guesses.
 const ANSWER_FLAGS = ["risk", "yes", "y", "layout", "repos", "packages", "tools", "workspace", "after-approval", "skills", "global", "no-setup", "project"];
-if (["install", "setup", "settings"].includes(command) && !process.stdin.isTTY && !args.some((a) => ANSWER_FLAGS.some((f) => a === `--${f}` || a.startsWith(`--${f}=`)))) {
+const NO_TTY = !process.stdin.isTTY && !args.some((a) => ANSWER_FLAGS.some((f) => a === `--${f}` || a.startsWith(`--${f}=`)));
+// Installing the skills needs no answers, so the default command still does that without a terminal
+// (e.g. `!` in Claude Code) and hands the questions to the spec-setup skill, which asks them in the chat.
+const HANDOFF = command === "install" && NO_TTY;
+if (["setup", "settings"].includes(command) && NO_TTY) {
   console.log(`✗ No interactive terminal, so ${command === "settings" ? "the settings menu can't open" : "setup can't ask its questions"}. Nothing was changed.
 
   This happens when it runs through another program: a "!" command in Claude Code, an editor task,
   or piped input. Either:
     • run it yourself in a terminal window (Terminal, iTerm, or your editor's terminal panel):
-        npx @benjaminthomas/spec-driven-dev@latest ${command === "install" ? "" : command}
+        npx @benjaminthomas/spec-driven-dev@latest ${command}${command === "setup" ? `
+    • or, in your AI tool (Claude Code, Cursor, Codex), say "run spec-setup": it asks the same
+      questions in the chat` : ""}
     • or give the answers as flags, for example:
         npx @benjaminthomas/spec-driven-dev@latest ${command === "settings" ? "settings --risk=off" : "setup --layout=multi-repo --repos=~/Projects/frontend,~/Projects/backend"}
       (add --yes to accept everything it detects)`);
@@ -137,7 +143,8 @@ async function install() {
     }
     console.log(`✓ ${skills.length} skills → ${dest}`);
   }
-  if (!dests.length) console.log("• No tools selected — nothing installed.");
+  if (!dests.length) console.log(HANDOFF ? "• No AI coding tools found (Claude Code, Cursor, Codex or Antigravity). Install one, or pass --tools=claude,cursor." : "• No tools selected — nothing installed.");
+  return dests.length;
 }
 
 // ---------- discovery ----------
@@ -788,12 +795,20 @@ try {
   else if (command === "risk") risk();
   else if (command === "settings") await settings();
   else if (command === "risk-eval") await riskEvalCmd();
-  else if (command === "install") {
+  else if (command === "install" && HANDOFF) {
+    console.log("No interactive terminal (for example a \"!\" command in Claude Code), so this installs the skills\nwith the detected defaults and leaves the setup questions to your AI tool.\n");
+    const n = await install();
+    if (n) console.log(`
+Next: in your AI tool, say "run spec-setup". It asks the setup questions in the chat
+(single repo, monorepo or multi-repo, tracker, branches) and writes .spec-driven.yml.
+If your AI tool doesn't recognise it yet, start a new session so it loads the new skills.
+To answer in a terminal instead, open Terminal or iTerm and run: npx @benjaminthomas/spec-driven-dev setup`);
+  } else if (command === "install") {
     await install();
     if (!flag("no-setup") && (await askConfirm("Set up this project now?", true))) await setup();
   } else if (command === "setup") await setup();
   else throw new Error(`Unknown command "${command}" — use install (default), setup, settings, doctor, status, context, risk, or risk-eval`);
-  if (["install", "setup"].includes(command)) console.log('\nNext: in your AI tool, say "investigate <ticket>" or "create a spec".');
+  if (["install", "setup"].includes(command) && !HANDOFF) console.log('\nNext: in your AI tool, say "investigate <ticket>" or "create a spec".');
 } catch (e) {
   console.error(`✗ ${e.message}`);
   process.exitCode = 1;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@benjaminthomas/spec-driven-dev",
-  "version": "1.11.1",
+  "version": "1.11.2",
   "description": "Spec-driven AI development workflow (investigate → spec → implement → verify → review → ship) as Agent Skills for Claude Code, Cursor, Codex CLI and Antigravity.",
   "type": "module",
   "bin": {

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ticket-to-pr",
-  "version": "1.11.1",
+  "version": "1.11.2",
   "description": "Parallel-batch spec-driven feature workflow (spec-setup, spec-investigate, spec-create, spec-implement, spec-verify, spec-review, spec-checkpoint, spec-ship) plus a portable SEO/GEO operations skill (generative-seo) for any codebase.",
   "author": {
     "name": "Benjamin Thomas",