create-claude-cabinet 0.6.5 → 0.6.6

package/lib/cli.js

@@ -72,7 +72,7 @@ const MODULES = {
       'skills/cabinet-usability', 'skills/cabinet-workflow-cop',
       'scripts/merge-findings.js', 'scripts/load-triage-history.js',
       'scripts/triage-server.mjs', 'scripts/triage-ui.html',
-      'scripts/finding-schema.json', 'scripts/resolve-committees.js',
+      'scripts/finding-schema.json', 'scripts/resolve-committees.cjs',
     ],
   },
   'lifecycle': {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-cabinet",
-  "version": "0.6.5",
+  "version": "0.6.6",
   "description": "Claude Cabinet — opinionated process scaffolding for Claude Code projects",
   "bin": {
     "create-claude-cabinet": "bin/create-claude-cabinet.js"

package/templates/README.md

@@ -297,7 +297,7 @@ when you outgrow them.
 5. **Customize committees** (optional):
    Create a `committees-project.yaml` in `.claude/cabinet/` to add custom
    members or committees. The upstream `committees.yaml` is installed
-   automatically. Run `node scripts/resolve-committees.js` to see the
+   automatically. Run `node scripts/resolve-committees.cjs` to see the
    merged result.
 
 6. **Run your first audit:** `/audit` — it discovers cabinet members, runs

package/templates/briefing/_briefing-cabinet-template.md

@@ -4,7 +4,7 @@
 
 *Which cabinet members are active in this project and how they're organized into committees.
 Reference `committees.yaml` (upstream) and `committees-project.yaml` (project
-customizations) for the canonical grouping. Run `node scripts/resolve-committees.js`
+customizations) for the canonical grouping. Run `node scripts/resolve-committees.cjs`
 to see the merged result.*
 
 ## Portfolio Rules

package/templates/cabinet/committees.yaml

@@ -5,7 +5,7 @@
 #
 # Consumed by:
 #   - /audit skill (committee selection menu)
-#   - scripts/resolve-committees.js (merges with committees-project.yaml)
+#   - scripts/resolve-committees.cjs (merges with committees-project.yaml)
 #
 # Cross-portfolio cabinet members are NOT in any committee. They activate via
 # standing-mandate in their SKILL.md frontmatter and run on every audit:

package/templates/scripts/{resolve-committees.js → resolve-committees.cjs}

@@ -2,10 +2,10 @@
 'use strict';
 
 /**
- * resolve-committees.js — Merge upstream committees.yaml with project committees-project.yaml
+ * resolve-committees.cjs — Merge upstream committees.yaml with project committees-project.yaml
  *
  * Usage:
- *   node scripts/resolve-committees.js [path-to-claude-dir]
+ *   node scripts/resolve-committees.cjs [path-to-claude-dir]
  *
  * Default path: .claude
  *

package/templates/skills/audit/SKILL.md

@@ -111,7 +111,7 @@ project. Adjust.
 Read `phases/member-selection.md` for which cabinet members to run.
 
 **Default (absent/empty):** Discover all cabinet members from
-`skills/cabinet-*/SKILL.md`. Run `node scripts/resolve-committees.js` to
+`skills/cabinet-*/SKILL.md`. Run `node scripts/resolve-committees.cjs` to
 get the merged committee list (upstream `cabinet/committees.yaml` merged
 with project `cabinet/committees-project.yaml`). Present the merged
 committees and let the user choose which to run. If neither committees

package/templates/skills/audit/phases/member-selection.md

@@ -5,7 +5,7 @@ reads this file before spawning cabinet member agents.
 
 When this file is absent or empty, the default behavior is: discover all
 cabinet members from `skills/cabinet-*/SKILL.md`, run
-`node scripts/resolve-committees.js` to merge upstream `cabinet/committees.yaml`
+`node scripts/resolve-committees.cjs` to merge upstream `cabinet/committees.yaml`
 with project `cabinet/committees-project.yaml`, present merged committees,
 otherwise run all. Cross-portfolio members always run regardless of selection.
 To explicitly skip member selection (and run no audit), write only `skip: true`.
@@ -28,7 +28,7 @@ Discover all cabinet members in `skills/cabinet-*/SKILL.md`.
 Run every one. Good for small projects with few cabinet members.
 
 ### Committee-Based Selection
-Run `node scripts/resolve-committees.js` to merge upstream
+Run `node scripts/resolve-committees.cjs` to merge upstream
 `cabinet/committees.yaml` with project `cabinet/committees-project.yaml`.
 Present merged committees to the user.
 

package/templates/skills/cabinet-cc-health/SKILL.md

@@ -131,7 +131,7 @@ empty").
 
 ### 2. Cabinet Member Activation Patterns
 
-Run `node scripts/resolve-committees.js` to get the merged committee list
+Run `node scripts/resolve-committees.cjs` to get the merged committee list
 (upstream `committees.yaml` + project `committees-project.yaml`). Also
 validate that any members listed in `committees-project.yaml` actually
 exist as `cabinet-*` directories. Cross-reference against:

package/templates/skills/debrief/SKILL.md

@@ -262,7 +262,7 @@ relevant expertise ever activates because nobody ran `/seed`.
 touched. Did the work involve a framework, library, data store, or
 infrastructure that isn't covered by any existing cabinet member? Compare
 against the cabinet members in `.claude/skills/cabinet-*/` and the
-merged committees (run `node scripts/resolve-committees.js`).
+merged committees (run `node scripts/resolve-committees.cjs`).
 
 Examples of what to catch:
 - Session used Mantine components but there's no framework-quality
@@ -273,7 +273,7 @@ Examples of what to catch:
 
 **Check B — Dormant cabinet member that should be active.** Are there
 cabinet members installed in the project that aren't in any committee
-(check merged output from `node scripts/resolve-committees.js`), but based on the last few sessions, probably should be? A
+(check merged output from `node scripts/resolve-committees.cjs`), but based on the last few sessions, probably should be? A
 cabinet member sitting dormant while the project does exactly the kind of
 work it's designed to review is a waste.