sdtk-kit 1.3.1 → 1.4.0

package/README.md

@@ -23,8 +23,9 @@ After install, all five SDTK CLI tools — plus the unified `sdtk` orchestrator
 # Set up the chosen runtime for the whole suite in one command
 sdtk init --runtime claude   # or --runtime codex
 
-# Generate a 17-file spec scaffold for your first feature
-sdtk-spec generate --feature-key MY_FEATURE
+# Generate the 17-file SDLC scaffold for your product/MVP (or a single feature)
+# (both --key and --name are required; --feature-key/--feature-name still work)
+sdtk-spec generate --key SHOPEASE --name "ShopEase MVP"
 ```
 
 ## Unified init: `sdtk init`
@@ -118,7 +119,7 @@ are the mechanism that puts `sdtk`, `sdtk-spec`, `sdtk-code`, `sdtk-ops`,
 - **Major version bumps** in any sub-toolkit require a coordinated `sdtk-kit` major-bump and re-publish.
 - If you need exact version control per toolkit, use standalone packages instead.
 
-Current dependency ranges (as of sdtk-kit v1.3.1):
+Current dependency ranges (as of sdtk-kit v1.3.2):
 
 | Package          | Version |
 |------------------|---------|
@@ -131,10 +132,40 @@ Current dependency ranges (as of sdtk-kit v1.3.1):
 ## Updating
 
 ```bash
-npm update -g sdtk-kit
+npm update -g sdtk-kit          # or: npm install -g sdtk-kit@latest
+sdtk --version                  # confirm sdtk-kit + per-kit versions
 ```
 
-This updates all sub-toolkits within their caret ranges.
+This updates all sub-toolkits within their caret ranges. Two things to remember:
+
+- **npm only updates the CLI code.** To refresh the skills already installed in a
+  project, re-run `init` with `--force` there: `sdtk init --runtime <r> --force`
+  (without `--force`, existing skill files are kept). `--force` re-copies
+  toolkit-managed files but never your own files — back up a customized
+  `*.config.json` first.
+- **`init` never deletes.** When a release stops writing a directory an older
+  version created, remove the leftover yourself after inspecting it
+  (e.g. `Remove-Item -Recurse -Force .\.agents`), then re-run `sdtk init --force`.
+
+If `npm install` fails right after a publish with `ETARGET No matching version
+found`, your local metadata cache is stale — run `npm cache verify` then
+`npm install -g sdtk-kit@latest --prefer-online`.
+
+### Maintainers: publish order
+
+When releasing, **publish the sub-kits before the umbrella**, and verify each is
+live before publishing `sdtk-kit`. The umbrella pins its sub-kits with caret
+ranges, so if `sdtk-kit` is published before a sub-kit it requires, anyone
+installing in that window hits `ETARGET`.
+
+```bash
+# in the sub-kit (e.g. sdtk-design-kit)
+npm publish
+npm view sdtk-design-kit@<version> version   # confirm it is live
+# then in sdtk-kit
+npm publish
+npm view sdtk-kit@<version> version
+```
 
 ## Uninstalling
 

package/bin/sdtk.js

@@ -24,6 +24,7 @@ function helpText() {
     "",
     "Usage:",
     "  sdtk init --runtime <claude|codex> [options]   Initialise all five toolkits",
+    "  sdtk update [--check-only]                     Update all five toolkit CLIs",
     "  sdtk --help                                    Show this help",
     "  sdtk --version                                 Show versions",
     "",
@@ -42,6 +43,9 @@ function helpText() {
     "  --keep-going               Continue past a failing toolkit (default: fail-fast).",
     "  --verbose                  Verbose per-toolkit output.",
     "",
+    "update options:",
+    "  --check-only               Print the planned npm command without running it.",
+    "",
     "Runs: sdtk-spec → sdtk-ops → sdtk-code → sdtk-design (all with --runtime)",
     "      → sdtk-wiki (its own non-runtime init; installs no skills).",
     "",
@@ -91,6 +95,12 @@ function main(argv) {
     return cmdInit(argv.slice(1));
   }
 
+  if (command === "update") {
+    // eslint-disable-next-line global-require
+    const { cmdUpdate } = require("../src/commands/update");
+    return cmdUpdate(argv.slice(1));
+  }
+
   console.error(`sdtk: unknown command '${command}'.`);
   console.error("Run `sdtk --help` for usage.");
   return 2;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sdtk-kit",
-  "version": "1.3.1",
+  "version": "1.4.0",
   "description": "Install all five SDTK toolkits in one command. Meta-package for sdtk-spec-kit, sdtk-code-kit, sdtk-ops-kit, sdtk-design-kit, and sdtk-wiki-kit.",
   "type": "commonjs",
   "bin": {
@@ -30,7 +30,7 @@
     "sdtk-code-kit": "^0.3.0",
     "sdtk-ops-kit": "^0.2.4",
     "sdtk-design-kit": "^0.3.2",
-    "sdtk-wiki-kit": "^0.2.0"
+    "sdtk-wiki-kit": "^0.3.0"
   },
   "engines": {
     "node": ">=18.13.0"

package/src/commands/update.js

@@ -0,0 +1,32 @@
+"use strict";
+
+const { execSync } = require("child_process");
+
+const UPDATE_CMD = "npm install -g sdtk-kit@latest";
+
+function cmdUpdate(argv) {
+  const checkOnly = argv.includes("--check-only");
+
+  if (checkOnly) {
+    console.log("Planned update command:");
+    console.log(`  ${UPDATE_CMD}`);
+    console.log("\nThis will update all five SDTK toolkit CLIs to the latest published versions.");
+    console.log("After updating, run `sdtk init --runtime <runtime> --force` in each project");
+    console.log("to refresh managed skills and project files to the new version.");
+    return 0;
+  }
+
+  console.log(`Running: ${UPDATE_CMD}\n`);
+  try {
+    execSync(UPDATE_CMD, { stdio: "inherit" });
+    console.log("\nUpdate complete.");
+    console.log("Run `sdtk --version` to confirm new versions.");
+    console.log("Run `sdtk init --runtime <runtime> --force` in each project to refresh managed files.");
+    return 0;
+  } catch (err) {
+    process.stderr.write(`sdtk update failed: ${err.message}\n`);
+    return 1;
+  }
+}
+
+module.exports = { cmdUpdate };