@benjaminthomas/spec-driven-dev 1.16.1 → 1.16.3

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 | 308 | 3,333 | 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,145** | **18,995** | **23** |
 
 - **8** skills: **1** setup + **6** workflow stages + **1** standalone
 - **4** tools supported natively (Claude Code, Codex CLI, Cursor, Antigravity), plus an MCP fallback

package/bin/cli.mjs

@@ -987,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));
-  const saved = backup(file);
+  // --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 saved as ${path.basename(saved)})
+✓ ${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.`);
 }

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.1",
+  "version": "1.16.3",
   "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.1",
+  "version": "1.16.3",
   "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

@@ -51,7 +51,8 @@ names (a path, or a git URL to clone). If you find one, say so with what it is,
 mark the ones not cloned here and offer their `git clone` command, cloning only on a yes), then run
 `spec-driven-dev setup --join=<specs repo> --repos=<chosen>` (or `npx -y @benjaminthomas/spec-driven-dev …`).
 Don't audit, don't ask about conventions, and never change the team's files: `CONTEXT.md`,
-`team.yml` and `team-repos.yml` are shared. Then run `doctor`, and finish with "You've joined. Say
+`team.yml` and `team-repos.yml` are shared. Then run `doctor`. If any of their repos lack the
+pointer line (Step 4, item 5), offer to add it there. Finish with "You've joined. Say
 *investigate STP-123* to start." Only `team-repos.yml` and no `team.yml` (an older setup): join
 anyway, and tell the user the team's rules aren't shared yet, so the person who set it up should
 run `spec-driven-dev team init`.
@@ -223,8 +224,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*.
@@ -250,10 +252,18 @@ Skip if `{specs_dir}/CONTEXT.md` already exists (offer a refresh instead, see `r
    `npx -y @benjaminthomas/spec-driven-dev risk`) to write `{specs_dir}/context/risk.md`. It uses
    git only, no model, and adds `risk.md` to `.gitignore` because it's regenerated on every run. Skip it for a new project with no history. Mention the hotspot count in the
    report. Set `risk.enabled: off` only if the user doesn't want it.
-5. **Offer, don't do:** ask whether to add this one line to `CLAUDE.md` / `AGENTS.md` (whichever
-   the project uses), so hosts reload the pointer after compaction and in every new session:
-   `For spec work, read specs/CONTEXT.md first, then the "Resume here" block of any unfinished spec.`
-   Add it only on a yes.
+5. **Offer, don't do:** ask whether to add one pointer line to `CLAUDE.md` / `AGENTS.md` (whichever
+   each repo uses), so hosts reload the project memory after compaction and in every new session.
+   - Single repo or monorepo: `For spec work, read specs/CONTEXT.md first, then the "Resume here" block of any unfinished spec.`
+   - Multi-repo: offer it for **every repo in this person's workspace** in one question, not just
+     the current one. Name the specs repo rather than assuming a layout:
+     `For spec work, read CONTEXT.md in the <specs repo name> repo first (usually ../<specs repo name>/CONTEXT.md), then the "Resume here" block of any unfinished spec.`
+   - Skip repos that already have a line mentioning `CONTEXT.md`. It's committed with each repo, so
+     teammates get it when they pull, and nobody adds it twice.
+   Add it only on a yes, and never commit. Each repo is its own commit; list them in the report, in
+   that repo's commit style and onto its base branch (e.g. `git -C reverb-backend commit -m "STP-123:
+   point AI tools to the project memory" AGENTS.md`). If a repo is on a feature branch, say the edit
+   is there and suggest committing it on its own so it doesn't ride along in that PR.
 6. Re-run `npx -y @benjaminthomas/spec-driven-dev doctor` if available. It checks the size limits
    and flags context lines that point to files which no longer exist.
 

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