specflow-cc 1.18.0 → 1.18.1

package/CHANGELOG.md

@@ -5,6 +5,15 @@ All notable changes to SpecFlow will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.18.1] - 2026-04-11
+
+### Fixed
+
+- **Installer now copies `bin/`** — the installer previously shipped `agents/`, `templates/`, `commands/`, and `hooks/` into `~/.claude/specflow-cc/` but never copied `bin/`, so any slash command invoking `node bin/sf-tools.cjs ...` failed with `MODULE_NOT_FOUND` in user projects. Affected commands: `/sf:todos`, `/sf:priority`, `/sf:metrics`, `/sf:plan`, `/sf:triage`, `/sf:revise`, `/sf:todo`
+  - Installer now copies `bin/` recursively (excluding `install.js` itself) via the existing `copyWithPathReplacement` helper
+  - All 12 affected command invocations rewritten to use the absolute path `node ~/.claude/specflow-cc/bin/sf-tools.cjs` (auto-rewritten to `./.claude/specflow-cc/` for local installs by the existing path-replacement pass)
+  - New smoke test `tests/install-bin-cli.test.cjs` runs the full installer in a temp project and invokes the installed CLI end-to-end, preventing regression
+
 ## [1.18.0] - 2026-04-08
 
 ### Added

package/bin/install.js

@@ -213,6 +213,20 @@ function install(isGlobal) {
     }
   }
 
+  // Copy bin (CLI tools) — exclude install.js, which is the installer itself
+  const binSrc = path.join(src, 'bin');
+  if (fs.existsSync(binSrc)) {
+    const binDest = path.join(specflowDir, 'bin');
+    copyWithPathReplacement(binSrc, binDest, pathPrefix);
+    const installerCopy = path.join(binDest, 'install.js');
+    if (fs.existsSync(installerCopy)) fs.unlinkSync(installerCopy);
+    if (verifyInstalled(binDest, 'bin')) {
+      console.log(`  ${green}✓${reset} Installed bin (CLI tools)`);
+    } else {
+      failures.push('bin');
+    }
+  }
+
   // Copy hooks
   const hooksSrc = path.join(src, 'hooks');
   if (fs.existsSync(hooksSrc)) {

package/commands/sf/metrics.md

@@ -80,12 +80,12 @@ For each `.specflow/archive/SPEC-*.md`:
 
 ```bash
 # Count todos via CLI tool (format-agnostic, excludes eliminated by default)
-node bin/sf-tools.cjs todo list --raw
+node ~/.claude/specflow-cc/bin/sf-tools.cjs todo list --raw
 ```
 
 This returns the list of open TODO IDs. For `--all` (including eliminated):
 ```bash
-node bin/sf-tools.cjs todo list --all --raw
+node ~/.claude/specflow-cc/bin/sf-tools.cjs todo list --all --raw
 ```
 
 Parse priority breakdown from the JSON output to count by priority level.

package/commands/sf/plan.md

@@ -46,7 +46,7 @@ Exit.
 ## Step 2: Check for Todos
 
 ```bash
-node bin/sf-tools.cjs todo list --raw
+node ~/.claude/specflow-cc/bin/sf-tools.cjs todo list --raw
 ```
 
 **If empty output (no todos):**
@@ -62,13 +62,13 @@ Exit.
 Format detection is handled automatically by the CLI tool.
 
 **If argument is a number (e.g., "1", "2"):**
-Run `node bin/sf-tools.cjs todo list` to get sorted array, pick the Nth item (1-indexed).
+Run `node ~/.claude/specflow-cc/bin/sf-tools.cjs todo list` to get sorted array, pick the Nth item (1-indexed).
 
 **If argument is TODO-XXX format:**
 The target ID is known directly.
 
 **If no argument:**
-Run `node bin/sf-tools.cjs todo list` and display todos, then prompt:
+Run `node ~/.claude/specflow-cc/bin/sf-tools.cjs todo list` and display todos, then prompt:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

package/commands/sf/priority.md

@@ -52,7 +52,7 @@ For each spec, extract:
 ### Load Todos
 
 ```bash
-node bin/sf-tools.cjs todo list
+node ~/.claude/specflow-cc/bin/sf-tools.cjs todo list
 ```
 
 Extract from the JSON array:

package/commands/sf/revise.md

@@ -476,7 +476,7 @@ After recording the Response, if any items were marked "Deferred":
 
 1. For each deferred item, generate next TODO ID:
    ```bash
-   node bin/sf-tools.cjs todo next-id --raw
+   node ~/.claude/specflow-cc/bin/sf-tools.cjs todo next-id --raw
    ```
 2. Create `.specflow/todos/TODO-{XXX}.md` for each deferred item:
    ```markdown

package/commands/sf/todo.md

@@ -60,7 +60,7 @@ Use AskUserQuestion:
 Run the CLI tool to get the next available ID:
 
 ```bash
-node bin/sf-tools.cjs todo next-id --raw
+node ~/.claude/specflow-cc/bin/sf-tools.cjs todo next-id --raw
 ```
 
 This handles both per-file format (TODO-XXX.md) and legacy TODO.md automatically.

package/commands/sf/todos.md

@@ -41,12 +41,12 @@ Call the CLI tool, which handles format detection automatically:
 
 **If `--all` flag was passed:**
 ```bash
-node bin/sf-tools.cjs todo list --all
+node ~/.claude/specflow-cc/bin/sf-tools.cjs todo list --all
 ```
 
 **Otherwise:**
 ```bash
-node bin/sf-tools.cjs todo list
+node ~/.claude/specflow-cc/bin/sf-tools.cjs todo list
 ```
 
 The tool returns a JSON array of `{ id, title, priority, status, complexity, created }` objects, sorted by priority (high > medium > low > unset), then by created date (oldest first).
@@ -135,7 +135,7 @@ Use the format from `templates/todo-index.md`:
 
 <success_criteria>
 - [ ] Initialization verified
-- [ ] TODOs listed via `node bin/sf-tools.cjs todo list` (format-agnostic)
+- [ ] TODOs listed via `node ~/.claude/specflow-cc/bin/sf-tools.cjs todo list` (format-agnostic)
 - [ ] Empty state handled with helpful message
 - [ ] Sorted by priority then date (oldest first within same priority)
 - [ ] Numbered list displayed with Status column

package/commands/sf/triage.md

@@ -146,7 +146,7 @@ For each selected finding:
 ### 6.1 Generate TODO ID
 
 ```bash
-node bin/sf-tools.cjs todo next-id --raw
+node ~/.claude/specflow-cc/bin/sf-tools.cjs todo next-id --raw
 ```
 
 This handles both per-file format and legacy TODO.md automatically (uses Node.js fs/regex — not grep -oP).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specflow-cc",
-  "version": "1.18.0",
+  "version": "1.18.1",
   "description": "Spec-driven development system for Claude Code — quality-first workflow with explicit audit cycles",
   "bin": {
     "specflow-cc": "bin/install.js"