@benjaminthomas/spec-driven-dev 1.16.0 → 1.16.2

package/README.md

@@ -787,7 +787,7 @@ skips that step rather than failing.
 
 | Skill | Stage | SKILL.md lines | Words | Supporting files |
 |---|---|---:|---:|---:|
-| `spec-setup` | 0 · configure | 298 | 3,141 | 4 |
+| `spec-setup` | 0 · configure | 299 | 3,163 | 4 |
 | `spec-investigate` | 1 · understand | 387 | 3,391 | 1 |
 | `spec-create` | 2 · plan | 198 | 1,806 | 6 |
 | `spec-implement` | 3 · build | 327 | 2,777 | 3 |
@@ -796,7 +796,7 @@ skips that step rather than failing.
 | `spec-checkpoint` | 6 · commit | 140 | 1,168 | 0 |
 | `spec-ship` | 7 · PR | 230 | 1,412 | 0 |
 | `generative-seo` | standalone | 255 | 2,209 | 7 |
-| **Total** | | **2,135** | **18,803** | **23** |
+| **Total** | | **2,136** | **18,825** | **23** |
 
 - **8** skills: **1** setup + **6** workflow stages + **1** standalone
 - **4** tools supported natively (Claude Code, Codex CLI, Cursor, Antigravity), plus an MCP fallback
@@ -849,7 +849,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.16.0 && git push origin v1.16.0`.
+  3. Tag the release and push the tag: `git tag v1.16.1 && git push origin v1.16.1`.
   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

@@ -592,6 +592,14 @@ function configApplies(f, dir) {
   return here === real(base) || c.repos.some((r) => { const p = real(path.resolve(base, expandHome(String(r.path || "")))); return here === p || here.startsWith(p + path.sep); });
 }
 
+// Back up a file without ever overwriting an older backup (that would lose the user's original).
+function backup(file) {
+  let b = `${file}.bak`;
+  if (fs.existsSync(b)) b = `${file}.bak-${new Date().toISOString().replace(/[-:]/g, "").replace("T", "-").slice(0, 15)}`;
+  fs.copyFileSync(file, b);
+  return b;
+}
+
 // The effective config: the team's rules (team.yml in the specs repo) with the personal file on top.
 function readConfig(file) {
   const personal = parseYaml(fs.readFileSync(file, "utf8"));
@@ -979,11 +987,12 @@ function teamInit() {
   const { team, personal: mine } = splitConfig(personal);
   fs.mkdirSync(path.dirname(tf), { recursive: true });
   fs.writeFileSync(tf, TEAM_HEADER + dumpYaml(team));
-  fs.copyFileSync(file, `${file}.bak`);
+  // --fresh: spec-setup wrote this file moments ago in the same run, so a backup would only be clutter.
+  const saved = flag("fresh") ? null : backup(file);
   fs.writeFileSync(file, PERSONAL_HEADER(path.relative(path.dirname(file), tf)) + dumpYaml(mine));
   step(1, "Team rules shared", ink.cyan);
   console.log(`✓ Wrote ${tf} (tracker, git conventions, commands, models, GitRisk, sharing)
-✓ ${file} now keeps only your local settings (the old file is ${path.basename(file)}.bak)
+✓ ${file} now keeps only your local settings${saved ? ` (the old file is saved as ${path.basename(saved)})` : ""}
 Next: commit team.yml in the specs repo. Colleagues who clone it run: spec-driven-dev setup --join=<path to the specs repo>
 or say "run spec-setup" in their AI tool, which finds it and offers to join.`);
 }
@@ -1007,7 +1016,7 @@ function join() {
   if (!have.length) throw new Error(`None of the team's repos (${known.map((r) => r.name).join(", ")}) are cloned in ${workspace}. Clone the ones you work on, then join again (or pass --workspace=<folder>).`);
   const file = path.join(workspace, ".spec-driven.yml");
   if (fs.existsSync(file) && !flag("force")) throw new Error(`${file} already exists. Add --force to replace it with the team's setup (it's backed up first).`);
-  if (fs.existsSync(file)) fs.copyFileSync(file, `${file}.bak`);
+  if (fs.existsSync(file)) console.log(`  Backed up your old settings to ${path.basename(backup(file))}`);
   const mine = { version: 1, layout: have.length > 1 ? "multi-repo" : "single", repos: have.map((n) => ({ path: n })), specs_dir: path.relative(workspace, specsDir) || ".", pipeline: { after_approval: opt("after-approval") || "stop" } };
   if (mine.layout === "single") { delete mine.repos; }
   fs.writeFileSync(file, PERSONAL_HEADER(path.relative(workspace, path.join(specsDir, "team.yml"))) + dumpYaml(mine));

package/bin/team.mjs

@@ -49,7 +49,7 @@ export function dumpYaml(obj, indent = "") {
   const scalar = (v) => (typeof v === "string" ? (/^[\w./@~-]+$/.test(v) && !/^(on|off|yes|no|true|false|null|\d.*)$/i.test(v) ? v : JSON.stringify(v)) : String(v));
   let out = "";
   for (const [k, v] of Object.entries(obj)) {
-    if (v === undefined || v === null || (isObj(v) && !Object.keys(v).length)) continue;
+    if (v === undefined || v === null || v === "" || (isObj(v) && !Object.keys(v).length)) continue; // "" means unset
     if (Array.isArray(v)) {
       out += `${indent}${k}:\n`;
       for (const item of v) {
@@ -57,7 +57,7 @@ export function dumpYaml(obj, indent = "") {
         const body = dumpYaml(item, `${indent}    `).replace(/^\s+/, "");
         out += `${indent}  - ${body}`;
       }
-    } else if (isObj(v)) out += `${indent}${k}:\n${dumpYaml(v, `${indent}  `)}`;
+    } else if (isObj(v)) { const body = dumpYaml(v, `${indent}  `); if (body) out += `${indent}${k}:\n${body}`; }
     else out += `${indent}${k}: ${scalar(v)}\n`;
   }
   return out;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@benjaminthomas/spec-driven-dev",
-  "version": "1.16.0",
+  "version": "1.16.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.16.0",
+  "version": "1.16.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",

package/plugin/skills/spec-setup/SKILL.md

@@ -223,8 +223,9 @@ for the rest.
    under `repos:` where they differ from the top level.
 2. If it's inside a repo, tell the user it's meant to be committed (so teammates get the same
    rules) — don't commit it yourself.
-   **Multi-repo with specs in a repo:** run `spec-driven-dev team init` right after writing the
-   file. It moves the team's rules (tracker, git conventions, commands, models, GitRisk, sharing)
+   **Multi-repo with specs in a repo:** run `spec-driven-dev team init --fresh` right after writing
+   the file (`--fresh` skips the backup, since you wrote the file this run; leave it off when
+   splitting a config that existed before). It moves the team's rules (tracker, git conventions, commands, models, GitRisk, sharing)
    into `{specs_dir}/team.yml`, which is committed with the specs, and leaves only local paths in
    `.spec-driven.yml`. Tell the user to commit `team.yml`, and that colleagues then just say
    "run spec-setup" and choose *Join*.

package/plugin/skills/spec-setup/references/audit.md

@@ -40,7 +40,10 @@ never ask again.
 
 ## 3. Discovery questions (one round)
 
-Show the draft map first, with each line marked **detected** (with its source) or **guess**. Then
+Show the draft map first. Give it a **Source** column and fill it on every line: **detected**
+with the file or command it came from (`AGENTS.md:12`, `git log`), or **guess**. One note for the
+whole table isn't enough. Count anything you report (spec folders, repos, files) with a command,
+never by eye. Then
 ask only what the code can't answer, as **plain text in one message**, after the setup choices have
 been answered. These are open questions, so
 never put them in a menu or multiple-choice tool (a menu needs two or more real options, and these