create-claude-cabinet 0.10.0 → 0.11.1

package/lib/cli.js

@@ -12,6 +12,214 @@ const { reset } = require('./reset');
 
 const VERSION = require('../package.json').version;
 
+/**
+ * Parse YAML frontmatter from a SKILL.md file (between first two --- lines).
+ * Returns an object with extracted fields, or null if no frontmatter found.
+ * Supports one level of nesting (e.g., directives: { orient: "...", debrief: "..." }).
+ */
+function parseFrontmatter(content) {
+  const match = content.match(/^---\n([\s\S]*?)\n---/);
+  if (!match) return null;
+  const fm = {};
+  let currentKey = null;
+  let currentValue = '';
+  let nestedKey = null;   // Parent key when parsing a nested map
+  let nestedMap = null;    // The nested map being built
+  let nestedSubKey = null; // Current sub-key within the nested map
+  let nestedSubValue = '';
+  let blockScalarKey = null;  // Key when parsing a block scalar (description: >)
+  let blockScalarValue = '';
+  let blockScalarStyle = null; // '>' for folded, '|' for literal
+
+  function flushNested() {
+    if (nestedSubKey && nestedMap) {
+      nestedMap[nestedSubKey] = nestedSubValue.trim();
+      nestedSubKey = null;
+      nestedSubValue = '';
+    }
+    if (nestedKey && nestedMap) {
+      fm[nestedKey] = nestedMap;
+      nestedKey = null;
+      nestedMap = null;
+    }
+  }
+
+  function flushCurrent() {
+    if (currentKey) {
+      fm[currentKey] = currentValue.trim();
+      currentKey = null;
+      currentValue = '';
+    }
+  }
+
+  for (const line of match[1].split('\n')) {
+    // Inside a block scalar (description: > or description: |)?
+    if (blockScalarKey) {
+      if (/^[\s]/.test(line) && line.trim() !== '') {
+        const sep = blockScalarStyle === '|' ? '\n' : ' ';
+        blockScalarValue += (blockScalarValue ? sep : '') + line.trim();
+        continue;
+      }
+      // Blank line inside block scalar — for '|' style, preserve as newline
+      if (line.trim() === '' && blockScalarStyle === '|') {
+        blockScalarValue += '\n';
+        continue;
+      }
+      // Not indented or blank line in '>' mode — end of block scalar
+      fm[blockScalarKey] = blockScalarValue.trim();
+      blockScalarKey = null;
+      blockScalarValue = '';
+      blockScalarStyle = null;
+      // Fall through to parse this line
+    }
+
+    // Inside a nested map?
+    if (nestedKey) {
+      // Nested sub-key (indented key: value)
+      const subKv = line.match(/^  ([a-z][a-z0-9_-]*)\s*:\s*(.*)/);
+      if (subKv) {
+        // Save previous sub-key
+        if (nestedSubKey) {
+          nestedMap[nestedSubKey] = nestedSubValue.trim();
+        }
+        nestedSubKey = subKv[1];
+        nestedSubValue = subKv[2].replace(/^[>|]\s*$/, '');
+        continue;
+      }
+      // First indented line doesn't look like a sub-key — this is a block scalar, not a map
+      if (!nestedSubKey && /^[\s]/.test(line) && line.trim() !== '') {
+        // Convert from nested map mode to block scalar mode
+        blockScalarKey = nestedKey;
+        blockScalarStyle = '>';  // Default to folded
+        blockScalarValue = line.trim();
+        nestedKey = null;
+        nestedMap = null;
+        continue;
+      }
+      // Continuation of nested sub-value (deeply indented)
+      if (nestedSubKey && /^    /.test(line)) {
+        nestedSubValue += ' ' + line.trim();
+        continue;
+      }
+      // Not indented — end of nested map
+      if (nestedSubKey) {
+        nestedMap[nestedSubKey] = nestedSubValue.trim();
+        nestedSubKey = null;
+        nestedSubValue = '';
+      }
+      fm[nestedKey] = nestedMap;
+      nestedKey = null;
+      nestedMap = null;
+      // Fall through to parse this line as a top-level key
+    }
+
+    // Continuation line (indented, for scalar values)
+    if (currentKey && /^[\s]/.test(line)) {
+      currentValue += ' ' + line.trim();
+      continue;
+    }
+
+    flushCurrent();
+
+    // New key-value pair
+    const kvMatch = line.match(/^([a-z][a-z0-9_-]*)\s*:\s*(.*)/);
+    if (kvMatch) {
+      const val = kvMatch[2].trim();
+      // Empty value after colon = start of nested map or block scalar
+      if (val === '' || val === '>' || val === '|') {
+        // Could be a nested map (directives:) or a block scalar (description: >).
+        // Start as nested map; if first indented line has no sub-key, fall back
+        // to block scalar mode.
+        nestedKey = kvMatch[1];
+        nestedMap = {};
+        blockScalarStyle = (val === '|') ? '|' : '>';  // Remember style hint
+        currentKey = null;
+      } else {
+        currentKey = kvMatch[1];
+        currentValue = val;
+      }
+    }
+  }
+  // Flush remaining
+  if (blockScalarKey) {
+    fm[blockScalarKey] = blockScalarValue.trim();
+  }
+  if (nestedSubKey && nestedMap) {
+    nestedMap[nestedSubKey] = nestedSubValue.trim();
+  }
+  if (nestedKey && nestedMap) {
+    fm[nestedKey] = Object.keys(nestedMap).length > 0 ? nestedMap : '';
+  }
+  flushCurrent();
+  return fm;
+}
+
+/**
+ * Generate .claude/skills/_index.json from all installed SKILL.md files.
+ * Consumers (menu, cabinet, audit, plan, execute) read this instead of
+ * scanning and parsing dozens of individual files.
+ */
+function generateSkillIndex(projectDir) {
+  const skillsDir = path.join(projectDir, '.claude', 'skills');
+  if (!fs.existsSync(skillsDir)) return 0;
+
+  const entries = [];
+  const dirs = fs.readdirSync(skillsDir, { withFileTypes: true });
+  for (const dir of dirs) {
+    if (!dir.isDirectory()) continue;
+    const skillFile = path.join(skillsDir, dir.name, 'SKILL.md');
+    if (!fs.existsSync(skillFile)) continue;
+
+    const content = fs.readFileSync(skillFile, 'utf8');
+    const fm = parseFrontmatter(content);
+    if (!fm || !fm.name) continue;
+
+    // Extract first sentence of description (before "Use when:")
+    let shortDesc = (fm.description || '').replace(/\s*Use when:.*$/is, '').trim();
+    // Collapse to first sentence
+    const sentenceEnd = shortDesc.match(/\.\s/);
+    if (sentenceEnd) shortDesc = shortDesc.slice(0, sentenceEnd.index + 1);
+
+    const isCabinet = dir.name.startsWith('cabinet-');
+    const entry = {
+      name: fm.name,
+      path: `.claude/skills/${dir.name}/SKILL.md`,
+      description: shortDesc,
+      type: isCabinet ? 'cabinet' : 'workflow',
+    };
+
+    // Invocability flags
+    if (fm['disable-model-invocation'] === 'true') entry.manual = true;
+    if (fm['user-invocable'] === 'false') entry.userInvocable = false;
+
+    // Standing mandate (for audit/plan/execute/orient/debrief member selection)
+    if (fm['standing-mandate']) {
+      entry.standingMandate = fm['standing-mandate'].split(/,\s*/).map(s => s.trim());
+    }
+
+    // Directives (scoped tasks for orient/debrief/etc.)
+    if (fm.directives && typeof fm.directives === 'object') {
+      entry.directives = fm.directives;
+    }
+
+    entries.push(entry);
+  }
+
+  entries.sort((a, b) => a.name.localeCompare(b.name));
+
+  const index = {
+    skills: entries,
+    generatedAt: new Date().toISOString(),
+    version: VERSION,
+  };
+
+  fs.writeFileSync(
+    path.join(skillsDir, '_index.json'),
+    JSON.stringify(index, null, 2) + '\n'
+  );
+  return entries.length;
+}
+
 const MODULES = {
   'session-loop': {
     name: 'Session Loop (orient + debrief)',
@@ -33,7 +241,7 @@ const MODULES = {
     mandatory: false,
     default: true,
     lean: false,
-    templates: ['scripts/pib-db.js', 'scripts/pib-db-schema.sql', 'scripts/work-tracker-server.mjs', 'scripts/work-tracker-ui.html'],
+    templates: ['scripts/pib-db.js', 'scripts/pib-db-schema.sql', 'scripts/work-tracker-server.mjs', 'scripts/work-tracker-ui.html', 'skills/work-tracker'],
     needsDb: true,
   },
   'planning': {
@@ -59,7 +267,7 @@ const MODULES = {
     default: true,
     lean: true,
     templates: [
-      'skills/audit', 'skills/pulse', 'skills/triage-audit',
+      'skills/audit', 'skills/pulse', 'skills/triage-audit', 'skills/cabinet',
       'cabinet', 'briefing',
       'skills/cabinet-accessibility', 'skills/cabinet-anti-confirmation',
       'skills/cabinet-architecture', 'skills/cabinet-boundary-man',
@@ -736,6 +944,14 @@ async function run() {
     }
   }
 
+  // --- Generate skill index ---
+  if (!flags.dryRun) {
+    const indexCount = generateSkillIndex(projectDir);
+    if (indexCount > 0) {
+      console.log(`  📇 Indexed ${indexCount} skills in .claude/skills/_index.json`);
+    }
+  }
+
   // --- Write metadata ---
   if (!flags.dryRun) {
     createMetadata(projectDir, {

package/package.json

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

package/templates/skills/cabinet/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: cabinet
+description: |
+  List your cabinet members and invoke one by name. Shows who's available,
+  what they specialize in, and lets you call on a specific expert.
+  Use when: "cabinet", "who's on the cabinet", "ask the architect",
+  "what experts do I have", "/cabinet", "get me the [member]".
+---
+
+# /cabinet — Your Expert Cabinet
+
+## Purpose
+
+Show who's in your cabinet and let you consult a specific member. The
+cabinet is your team of domain experts — each one evaluates from a
+different lens. This skill is the front door.
+
+## Workflow
+
+1. **Read the skill index:** Read `.claude/skills/_index.json` and filter
+   to entries where `type === "cabinet"`. This gives you every cabinet
+   member's name and description in one read.
+
+   If the index file doesn't exist (older install), fall back to
+   Glob for `.claude/skills/cabinet-*/SKILL.md` and read frontmatter.
+
+2. **Strip the `cabinet-` prefix** for friendly display — the architect
+   is "architect", not "cabinet-architecture".
+
+3. **Present the roster:**
+
+   ### Your Cabinet
+   | Member | Expertise |
+   |--------|-----------|
+   | architect | System fit and infrastructure leverage |
+   | debugger | Dependency chains, error modes, environment prereqs |
+   | ... | ... |
+
+   Sort alphabetically.
+
+4. **If the user named a specific member** (e.g., "ask the architect",
+   "/cabinet architect", "get me the historian"), skip the roster and
+   invoke that member's skill directly.
+
+5. **If showing the roster**, ask: "Who do you want to consult?"
+   When they pick one, invoke that member's skill.
+
+## Important
+
+- Roster is always discovered dynamically — never hardcoded.
+- Member names are friendly (no `cabinet-` prefix in display).
+- If the user asks for a member that doesn't exist, show the roster
+  and say which name didn't match.

package/templates/skills/cabinet-architecture/SKILL.md

@@ -11,6 +11,14 @@ briefing:
   - _briefing-identity.md
   - _briefing-architecture.md
   - _briefing-jurisdictions.md
+standing-mandate: audit, plan, investigate
+directives:
+  plan: >
+    Evaluate structural fit. Does this plan compose well with existing
+    architecture, or introduce unnecessary coupling or layering violations?
+  investigate: >
+    Guide where to look. Which layers, components, and boundaries are
+    most relevant to this investigation?
 ---
 
 # Architecture Cabinet Member

package/templates/skills/cabinet-boundary-man/SKILL.md

@@ -11,6 +11,11 @@ briefing:
   - _briefing-identity.md
   - _briefing-architecture.md
   - _briefing-jurisdictions.md
+standing-mandate: execute
+directives:
+  execute: >
+    Watch for implicit boundary conditions, unguarded state transitions,
+    and silent exclusions in the code being written.
 ---
 
 # Boundary Man

package/templates/skills/cabinet-data-integrity/SKILL.md

@@ -12,6 +12,7 @@ briefing:
   - _briefing-architecture.md
   - _briefing-jurisdictions.md
   - _briefing-api.md
+standing-mandate: audit
 ---
 
 # Data Integrity Cabinet Member

package/templates/skills/cabinet-debugger/SKILL.md

@@ -9,6 +9,12 @@ user-invocable: false
 briefing:
   - _briefing-identity.md
   - _briefing-architecture.md
+standing-mandate: execute
+directives:
+  execute: >
+    Before code runs, verify prerequisites. Dependencies installed?
+    Environment configured? Migrations needed? Flag anything that will
+    surface as a runtime surprise.
 ---
 
 # Debugger Cabinet Member

package/templates/skills/cabinet-framework-quality/SKILL.md

@@ -12,6 +12,7 @@ user-invocable: false
 briefing:
   - _briefing-architecture.md
   - _briefing-jurisdictions.md
+standing-mandate: audit
 ---
 
 # Framework Quality

package/templates/skills/cabinet-historian/SKILL.md

@@ -10,6 +10,21 @@ user-invocable: false
 briefing:
   - _briefing-identity.md
   - _briefing-architecture.md
+standing-mandate: plan, execute, orient, debrief
+directives:
+  plan: >
+    Check prior art. Have we attempted something similar before? What
+    worked or failed? Surface relevant decisions and patterns.
+  execute: >
+    Flag if this code repeats a known mistake or contradicts an
+    established pattern.
+  orient: >
+    Review the loaded context. Surface 1-3 prior decisions or lessons
+    most relevant to today's likely work. Keep it brief — facts only,
+    no analysis.
+  debrief: >
+    Review this session's decisions and lessons. Verify they were
+    captured to memory. Flag any significant decision that wasn't recorded.
 ---
 
 # Historian Cabinet Member

package/templates/skills/cabinet-organized-mind/SKILL.md

@@ -13,6 +13,12 @@ user-invocable: false
 briefing:
   - _briefing-identity.md
   - _briefing-architecture.md
+standing-mandate: audit, plan
+directives:
+  plan: >
+    Evaluate cognitive load. Will this plan's result be understandable
+    and maintainable? Does it externalize complexity or pile it on the
+    operator?
 ---
 
 # The Organized Mind

package/templates/skills/cabinet-process-therapist/SKILL.md

@@ -11,7 +11,12 @@ briefing:
   - _briefing-identity.md
   - _briefing-cabinet.md
   - _briefing-jurisdictions.md
-standing-mandate: audit
+standing-mandate: audit, seed
+directives:
+  seed: >
+    Before adding new members, evaluate whether existing members are
+    healthy and being used effectively. Are current members overlapping
+    or underperforming?
 files:
   - skills/**/*.md
   - skills/cabinet-*/_prompt-guide.md

package/templates/skills/cabinet-qa/SKILL.md

@@ -11,6 +11,14 @@ briefing:
   - _briefing-identity.md
   - _briefing-architecture.md
   - _briefing-jurisdictions.md
+standing-mandate: plan, execute
+directives:
+  plan: >
+    Evaluate testability. Are acceptance criteria verifiable? What edge
+    cases and failure modes are missing from the plan?
+  execute: >
+    Verify each checkpoint against acceptance criteria. Flag untested
+    paths and regressions.
 ---
 
 # QA Cabinet Member

package/templates/skills/cabinet-record-keeper/SKILL.md

@@ -10,7 +10,12 @@ user-invocable: false
 briefing:
   - _briefing-identity.md
   - _briefing-jurisdictions.md
-standing-mandate: audit
+standing-mandate: audit, debrief
+directives:
+  debrief: >
+    Review this session's changed files. Check if any CLAUDE.md,
+    system-status, briefing, or memory files now contain stale claims.
+    Fix what you find — don't create findings.
 files:
   - CLAUDE.md
   - "**/CLAUDE.md"

package/templates/skills/cabinet-roster-check/SKILL.md

@@ -10,7 +10,11 @@ user-invocable: false
 briefing:
   - _briefing-identity.md
   - _briefing-cabinet.md
-standing-mandate: audit
+standing-mandate: audit, seed
+directives:
+  seed: >
+    Identify coverage gaps. What expertise is the cabinet missing for
+    this project's current technology stack and workflow?
 files:
   - .claude/skills/**/*.md
   - CLAUDE.md

package/templates/skills/cabinet-security/SKILL.md

@@ -11,6 +11,14 @@ briefing:
   - _briefing-architecture.md
   - _briefing-jurisdictions.md
   - _briefing-api.md
+standing-mandate: audit, plan, execute
+directives:
+  plan: >
+    Check for security exposure. Does this plan handle auth, data access,
+    and input validation? Any secrets or credentials at risk?
+  execute: >
+    Watch for hardcoded secrets, missing auth checks, unvalidated input,
+    and accidental data exposure in the code being written.
 ---
 
 # Security Cabinet Member

package/templates/skills/cabinet-speed-freak/SKILL.md

@@ -12,6 +12,7 @@ briefing:
   - _briefing-architecture.md
   - _briefing-jurisdictions.md
 interactive-only: true
+standing-mandate: audit
 ---
 
 # Speed Freak

package/templates/skills/cabinet-system-advocate/SKILL.md

@@ -11,6 +11,14 @@ briefing:
   - _briefing-identity.md
   - _briefing-cabinet.md
 standing-mandate: orient, debrief
+directives:
+  orient: >
+    Review installed skills and recent session activity. Spotlight one
+    underused capability relevant to today's context. One sentence.
+  debrief: >
+    Review what was built this session. Update the feature adoption
+    ledger if new capabilities were added. Note any that need
+    discoverability work.
 topics:
   - feature
   - adoption

package/templates/skills/cabinet-technical-debt/SKILL.md

@@ -10,6 +10,7 @@ user-invocable: false
 briefing:
   - _briefing-identity.md
   - _briefing-architecture.md
+standing-mandate: audit
 ---
 
 # Technical Debt Cabinet Member

package/templates/skills/cabinet-usability/SKILL.md

@@ -10,6 +10,7 @@ briefing:
   - _briefing-identity.md
   - _briefing-jurisdictions.md
 interactive-only: true
+standing-mandate: audit
 ---
 
 # Usability Cabinet Member

package/templates/skills/cabinet-user-advocate/SKILL.md

@@ -16,6 +16,11 @@ briefing:
   - _briefing-architecture.md
   - _briefing-jurisdictions.md
 standing-mandate: orient
+directives:
+  orient: >
+    Review what happened recently. If the system has grown in complexity
+    since the user last got an explanation, flag one thing worth
+    explaining. Otherwise, stay silent.
 topics:
   - why does
   - how does

package/templates/skills/cabinet-workflow-cop/SKILL.md

@@ -9,6 +9,7 @@ user-invocable: false
 briefing:
   - _briefing-identity.md
   - _briefing-jurisdictions.md
+standing-mandate: audit
 ---
 
 # Workflow Cop Cabinet Member

package/templates/skills/cc-upgrade/SKILL.md

@@ -131,9 +131,15 @@ authorized update path for manifest-tracked files.
 
 ### 2.4. Memory Hook Migration (v0.9.x → v0.10+)
 
-**This step runs when upgrading from v0.9.x or earlier** (detected by
-the presence of `memory-session-start.sh` or `memory-post-compact.sh`
-in `.claude/settings.json`).
+**This step runs when upgrading from v0.9.x or earlier.** Detect by
+checking BOTH:
+- `.claude/settings.json` for `memory-session-start.sh` or
+  `memory-post-compact.sh` references
+- `.claude/hooks/` directory for the actual files on disk
+
+Either condition triggers this step. The installer cleans settings.json
+references but does NOT delete the orphaned files (it treats them as
+project-owned since they're no longer in the upstream manifest).
 
 Starting in v0.10, omega's native hooks handle memory capture/recall
 directly (configured in global `~/.claude/settings.json`). The old
@@ -145,13 +151,13 @@ context injection if left in place.
    in `SessionStart` hooks and `memory-post-compact.sh` in `PostCompact`
 2. If found, remove those entries. Keep other hooks (git-guardrails,
    cc-upstream-guard, telemetry) untouched.
-3. Verify omega native hooks are configured: run `omega hooks doctor`.
+3. Check for orphaned files: `ls .claude/hooks/memory-session-start.sh
+   .claude/hooks/memory-post-compact.sh 2>/dev/null`. Delete any that
+   exist — they are dead weight, not project-owned content.
+4. Verify omega native hooks are configured: run `omega hooks doctor`.
    If not configured, the installer's omega-setup already ran
    `omega hooks setup` — verify by checking `~/.claude/settings.json`
    for `fast_hook.py` entries.
-4. The old shell scripts (`hooks/memory-session-start.sh`,
-   `hooks/memory-post-compact.sh`) can be deleted from the project's
-   `.claude/hooks/` directory — they're no longer called.
 
 **Tell the user:** "Memory hooks have been upgraded to omega native.
 You now get 3 additional capabilities: real-time decision capture,

package/templates/skills/debrief/SKILL.md

@@ -180,27 +180,14 @@ Read `phases/update-state.md` for what state files and documentation
 to update. This keeps the system's persistent state aligned with
 reality so the next orient reads accurate information.
 
-**Default (absent/empty):** At minimum check whether `system-status.md`
+**Default (absent/empty):** Check whether `system-status.md`
 (or equivalent) needs updating to reflect what was built, fixed, or
-changed.
-
-Also check **briefing freshness** — did this session's work invalidate
-any claims in the briefing files? Common drift signals:
-- Session installed a new module or capability, but the briefing still
-  says it's not available
-- Session changed architecture (new data store, new framework, new
-  deployment), but the briefing describes the old state
-- Version numbers in `.ccrc.json` or briefing don't match `package.json`
-- Work tracking was set up or changed, but `_briefing-work-tracking.md`
-  doesn't reflect it
-
-If the briefing is stale, update the relevant split file (or the
-monolithic `_briefing.md` if the project hasn't split yet). Don't wait
-for `/audit` to catch this — stale briefings degrade every cabinet
-member's judgment until they're fixed.
-
-Also check the **user-level state** (silently — don't make this a
-conversation unless something needs updating):
+changed. Also check the user-level state below.
+
+#### User-Level State
+
+Check silently — don't make this a conversation unless something
+needs updating:
 
 - **`~/.claude/CLAUDE.md`** — did the user reveal something about
   themselves this session that isn't in their profile? A new role,
@@ -390,14 +377,38 @@ these aren't captured somewhere, they rely on human memory.
 
 **Skip (absent/empty).**
 
-### 12. Discover Custom Phases
+### 12. Cabinet Consultations (core)
+
+Spawn cabinet members whose `standing-mandate` includes `debrief`.
+
+**Discovery:** Read `.claude/skills/_index.json` and filter to entries
+where `standingMandate` includes `"debrief"`. Each matching entry has
+a `directives.debrief` field — this is the scoped task for that member.
+If the index is missing, fall back to reading `cabinet-*/SKILL.md`
+frontmatter for `standing-mandate` and `directives`.
+
+**For each matching member**, spawn an agent with:
+- The member's full SKILL.md (read from the `path` in the index)
+- The session inventory from step 1 (what changed)
+- The member's `directives.debrief` as the task
+
+Spawn in parallel where possible. If a member has no directive for
+`debrief`, skip it — a standing mandate without a directive is a data
+error, not a reason to give the member an open-ended task.
+
+**Cost control:** These are lightweight passes, not full audits. Each
+agent should complete in under 2 minutes. If a member's directive
+produces no findings or changes, it returns silently. Include their
+results in the report only when they surfaced or changed something.
+
+### 13. Discover Custom Phases
 
 After running the core phases above, check for any additional phase
 files in `phases/` that the skeleton doesn't define. These are project-
 specific extensions. Each custom phase file declares its position in
 the workflow. Execute them at their declared position.
 
-### 13. Present Report (presentation)
+### 14. Present Report (presentation)
 
 Read `phases/report.md` for how to present the debrief summary.
 
@@ -429,7 +440,8 @@ skip presentation phases. Core phases always run.
 
 - **Core phases** (always run): inventory, close-work, auto-maintenance,
   update-state, health-checks, record-lessons, upstream-feedback,
-  skill-discovery, cabinet-check, loose-ends, persist work
+  skill-discovery, cabinet-check, loose-ends, cabinet-consultations,
+  persist work
 - **Presentation phases** (skippable): report
 
 A project that wants a quick debrief variant skips the report and

package/templates/skills/execute/SKILL.md

@@ -104,17 +104,21 @@ loop (Steps 4-5) and instead:
 Read `phases/cabinet.md` for which cabinet members to activate during
 execution, any always-on cabinet members, and any project-specific rules.
 
-**Default (absent/empty):** Read `.claude/skills/cabinet-*/SKILL.md`
-and select cabinet members whose convening criteria match:
-- **standing-mandate: execute** — always included
+**Default (absent/empty):** Use `.claude/skills/_index.json` to select
+cabinet members whose convening criteria match:
+- **`standingMandate` includes `"execute"`** — always included
 - **File patterns** — any file in the plan's surface area matches
 - **Topic keywords** — any keyword in the plan description matches
 
+Fall back to reading `cabinet-*/SKILL.md` if the index is missing.
+
 Err toward inclusion. A cabinet member that activates unnecessarily costs
 a few seconds; one that doesn't activate when needed costs rework.
 
 Prepare reusable briefing for agent prompts: read `_briefing.md` once and
-keep the essential facts ready to paste into each agent's prompt.
+keep the essential facts ready to paste into each agent's prompt. When a
+member has a `directives.execute`, include it in the agent prompt to
+sharpen their focus during execution checkpoints.
 
 If no cabinet members exist in the project, skip all checkpoint steps
 (3, 4b, 5) and execute the plan directly. Checkpoints add depth, not

package/templates/skills/investigate/SKILL.md

@@ -44,7 +44,18 @@ Bad questions (too vague — narrow first):
 - "How does the system work?" → Pick a specific subsystem
 - "Is the code good?" → That's /audit, not /investigate
 
-### 2. Observe (Gather Facts)
+### 2. Cabinet Consultations
+
+Before exploring, check if any cabinet members have relevant context.
+Read `.claude/skills/_index.json` and filter to entries where
+`standingMandate` includes `"investigate"` and `directives.investigate`
+exists. Spawn matching members as agents in parallel, passing the
+investigation question from step 1.
+
+If no members match or the index is missing, proceed directly to
+observation.
+
+### 3. Observe (Gather Facts)
 
 Collect raw data without interpreting it. Use the Explore agent or
 direct Grep/Glob/Read calls:
@@ -62,7 +73,7 @@ direct Grep/Glob/Read calls:
 **Output:** A bulleted list of concrete observations. Each observation
 should cite a specific file:line or data point.
 
-### 3. Hypothesize (Form Explanations)
+### 4. Hypothesize (Form Explanations)
 
 Based on observations, form 1-3 hypotheses that explain what you're seeing.
 
@@ -75,7 +86,7 @@ For each hypothesis:
 first explanation. If you only have one hypothesis, you're not investigating
 — you're confirming.
 
-### 4. Test (Verify)
+### 5. Test (Verify)
 
 For each hypothesis, actively seek the confirming AND refuting evidence
 you identified. This may involve:
@@ -87,7 +98,7 @@ you identified. This may involve:
 **Record results per hypothesis:** confirmed, refuted, or inconclusive
 (with what additional data would resolve it).
 
-### 5. Conclude
+### 6. Conclude
 
 Summarize findings in a structured report:
 

package/templates/skills/menu/SKILL.md

@@ -14,33 +14,30 @@ whether they are auto-invocable or manual-only.
 
 ## Workflow
 
-1. **Discover skills:** Use the Glob tool to find all `.claude/skills/*/SKILL.md` files.
+1. **Read the skill index:** Read `.claude/skills/_index.json`. This file
+   is generated by the installer and contains name, description, type,
+   and invocability for every installed skill.
 
-2. **Read frontmatter from each:** For every discovered SKILL.md, use the Read tool
-   to extract the YAML frontmatter (between the `---` delimiters). Parse these fields:
-   - `name` — the skill name (used as `/name` in the table)
-   - `description` — first line or sentence of the description (strip the
-     "Use when:" portion for display)
-   - `disable-model-invocation` — if `true`, the skill is manual-only.
-     If absent or false, Claude can invoke it automatically.
+   If the index file doesn't exist (older install), fall back to
+   discovering skills via Glob + reading individual SKILL.md frontmatter.
 
-3. **Group skills into two categories:**
+2. **Filter and group:**
+   - Exclude entries where `type === "cabinet"` — cabinet members are
+     accessed through `/cabinet`, not listed here.
+   - Group remaining skills into:
 
-   **Auto (Claude uses these when relevant)** — skills where
-   `disable-model-invocation` is absent or false. These trigger automatically
-   when the context matches.
+   **Auto (Claude uses these when relevant)** — skills where `manual`
+   is absent or false.
 
-   **Manual (user invokes these — they have side effects)** — skills where
-   `disable-model-invocation: true`. The user must explicitly invoke these.
+   **Manual (user invokes these — they have side effects)** — skills
+   where `manual` is true.
 
-   Note: `/menu` itself goes in whichever category its own frontmatter indicates.
-
-4. **Format as two tables:**
+3. **Format as two tables:**
 
    ### Auto (Claude uses these when relevant)
-   | Skill | When it triggers |
+   | Skill | What it does |
    |---|---|
-   | `/name` | description (from the "Use when:" part of the description field) |
+   | `/name` | description |
 
    ### Manual (you invoke these — they have side effects)
    | Skill | What it does |
@@ -48,14 +45,12 @@ whether they are auto-invocable or manual-only.
 
    Sort alphabetically within each group.
 
-5. **Suggest relevant skills:** Based on current context (open work items,
+4. **Suggest relevant skills:** Based on current context (open work items,
    queued tasks, recent activity), suggest which skills are most relevant
    right now.
 
 ## Important
 
-- Do NOT hardcode any skill names or descriptions. Every entry must come
-  from reading the actual SKILL.md files at discovery time.
-- If a new skill is added to `.claude/skills/`, it automatically appears
-  in the menu on the next invocation. No updates to this file needed.
+- The index is the primary data source. Only fall back to scanning
+  individual SKILL.md files if `_index.json` is missing.
 - If a SKILL.md has no description, show the skill name with "(no description)".

package/templates/skills/orient/SKILL.md

@@ -29,6 +29,9 @@ related:
   - type: file
     path: .claude/skills/orient/phases/cabinet.md
     role: "Project-specific: which cabinet members to activate"
+  - type: file
+    path: .claude/skills/orient/phases/skills-menu.md
+    role: "Project-specific: what skills to show after briefing"
   - type: file
     path: cabinet/_briefing.md
     role: "Project identity and configuration"
@@ -227,7 +230,30 @@ without being explicitly invoked for each decision.
 
 **Skip (absent/empty).**
 
-### 7. Present Briefing (presentation)
+### 7. Cabinet Consultations (core)
+
+Spawn cabinet members whose `standing-mandate` includes `orient`.
+
+**Discovery:** Read `.claude/skills/_index.json` and filter to entries
+where `standingMandate` includes `"orient"`. Each matching entry has
+a `directives.orient` field — this is the scoped task for that member.
+If the index is missing, fall back to reading `cabinet-*/SKILL.md`
+frontmatter for `standing-mandate` and `directives`.
+
+**For each matching member**, spawn an agent with:
+- The member's full SKILL.md (read from the `path` in the index)
+- The context loaded in step 1 (project state, recent work)
+- The member's `directives.orient` as the task
+
+Spawn in parallel where possible. If a member has no directive for
+`orient`, skip it — a standing mandate without a directive is a data
+error, not a reason to give the member an open-ended task.
+
+**Cost control:** These are lightweight passes, not full audits. Each
+agent should complete in under 1 minute. Include their output in the
+briefing only when they have something to contribute. Silent is fine.
+
+### 8. Present Briefing (presentation)
 
 Read `phases/briefing.md` for how to present the orientation results.
 This phase controls format, sections, tone, and any time-aware or
@@ -237,7 +263,23 @@ context-aware presentation modes.
 in steps 1-6: project state, work items needing attention, any health
 issues found, maintenance results.
 
-### 8. Discover Custom Phases
+### 9. Show Available Skills (core)
+
+After the briefing, show the user what skills are available. This
+serves the same purpose as a menu at a restaurant — you can't order
+what you don't know exists.
+
+**Default (absent/empty):** Invoke the `/menu` skill. This dynamically
+discovers all skills in `.claude/skills/` (both CC upstream and project-
+specific), reads their frontmatter, and presents them grouped by
+auto-invocable vs manual. It also suggests which skills are most
+relevant given current context.
+
+Read `phases/skills-menu.md` for project-specific overrides (e.g.,
+highlighting certain skills, suppressing others, or changing the
+presentation format).
+
+### 10. Discover Custom Phases
 
 After running the core phases above, check for any additional phase
 files in `phases/` that the skeleton doesn't define. These are project-
@@ -245,7 +287,7 @@ specific extensions. Each custom phase file declares its position in the
 workflow (e.g., "runs after work scan, before briefing"). Execute them
 at their declared position.
 
-### 9. Name the Session
+### 11. Name the Session
 
 Rename the session so the sidebar is scannable. Every session that starts
 with `/orient` looks identical in the history — naming fixes this.
@@ -265,6 +307,7 @@ stated a focus, ask.
 | `auto-maintenance.md` | Default: omega memory hygiene | Recurring session-start tasks |
 | `cabinet.md` | Skip | Which cabinet members to activate |
 | `briefing.md` | Default: simple summary | How to present orientation |
+| `skills-menu.md` | Default: invoke /menu | What skills to show and how |
 
 ## Quick Mode
 
@@ -274,7 +317,8 @@ user already knows what they're doing, skip presentation phases. Core
 phases always run because they keep the system healthy.
 
 - **Core phases** (always run): context, data-sync, work-scan,
-  health-checks, auto-maintenance, cabinet
+  health-checks, auto-maintenance, cabinet, cabinet-consultations,
+  skills-menu
 - **Presentation phases** (skippable): briefing
 
 A project that wants a quick orient variant skips the briefing phase
@@ -292,7 +336,6 @@ Examples of phases mature projects add:
 - Command queue processing (check for instructions from external UIs)
 - Deferred item evaluation (re-check trigger conditions on paused work)
 - Time-aware briefing modes (first session of day vs. returning session)
-- Proactive skill suggestions (surface tools relevant to current state)
 - Calendar integration (upcoming events that need preparation)
 
 ## Calibration

package/templates/skills/plan/SKILL.md

@@ -177,13 +177,16 @@ activate during planning, any special rules (e.g., "always include a
 design committee for UI plans"), and any project-specific critique
 workflow.
 
-**Default (absent/empty):** Read `.claude/skills/cabinet-*/SKILL.md`
-and identify cabinet members whose convening criteria match the plan's
-surface area or topic. Spawn each matching cabinet member as a parallel
-agent. Each receives:
+**Default (absent/empty):** Use `.claude/skills/_index.json` to
+identify cabinet members whose convening criteria match the plan's
+surface area or topic (check `standingMandate` for `"plan"`, file
+patterns, and topic keywords). Fall back to reading `cabinet-*/SKILL.md`
+if the index is missing. Spawn each matching member as a parallel agent.
+Each receives:
 - The cabinet member's full SKILL.md content
 - Essential project briefing from `_briefing.md`
 - The draft plan (problem, implementation, surface area, AC)
+- The member's `directives.plan` if it exists (scoped focus for planning)
 - Instructions to evaluate through their lens and return concerns + verdict
 
 **Collect all verdicts.** Apply escalation:

package/templates/skills/seed/SKILL.md

@@ -102,7 +102,21 @@ phase file). Projects override this phase to add domain-specific signals
 compliance cabinet member; a financial project might map payment libraries
 to a financial-integrity cabinet member.
 
-### 2. Evaluate Existing Cabinet Members
+### 2. Cabinet Consultations
+
+Before evaluating gaps, check if any cabinet members have relevant
+context. Read `.claude/skills/_index.json` and filter to entries where
+`standingMandate` includes `"seed"` and `directives.seed` exists.
+Spawn matching members as agents in parallel, passing the scan results
+from step 1.
+
+Include their findings in the evaluation step — a roster-check member
+might identify coverage gaps, a process-therapist might flag unhealthy
+existing members before you add new ones.
+
+If no members match or the index is missing, proceed directly.
+
+### 3. Evaluate Existing Cabinet Members
 
 Read `phases/evaluate-existing.md` for how to compare detected signals
 against the current cabinet members.
@@ -124,7 +138,7 @@ gaps to fill and which staleness to address. Not every technology needs
 a cabinet member — some are too minor, some are well-understood, some are
 covered by existing cabinet members with broader scope.
 
-### 3. Build New Cabinet Members
+### 4. Build New Cabinet Members
 
 Read `phases/build-member.md` for how to collaboratively build a
 new cabinet member with the user.
@@ -149,7 +163,7 @@ built with the user's input — "we use Mantine, we care about keyboard
 navigation, our users are on slow connections" — catches what actually
 matters.
 
-### 4. Maintain Existing Cabinet Members
+### 5. Maintain Existing Cabinet Members
 
 Read `phases/maintain.md` for how to review the health of existing
 cabinet members and recommend changes.

package/templates/skills/work-tracker/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: work-tracker
+description: |
+  Open the work tracking UI. Starts the local server and tells you to
+  open it in the browser. Use to review projects, actions, and plan
+  progress visually. Use when: "work tracker", "show work", "open tracker",
+  "show projects", "show actions", "/work-tracker".
+related:
+  - type: file
+    path: scripts/work-tracker-server.mjs
+    role: "Local HTTP server for work tracker UI"
+  - type: file
+    path: scripts/work-tracker-ui.html
+    role: "Browser-based work tracking interface"
+  - type: file
+    path: scripts/pib-db.js
+    role: "Data layer — projects and actions in pib.db"
+---
+
+# /work-tracker — Work Tracking UI
+
+## Purpose
+
+Open the visual work tracker so the user can review projects, actions,
+and progress in a browser rather than through conversation.
+
+## Steps
+
+1. **Check database exists:**
+   ```bash
+   ls pib.db
+   ```
+   If missing, initialize it:
+   ```bash
+   node scripts/pib-db.js init
+   ```
+
+2. **Start the server:**
+   ```bash
+   node scripts/work-tracker-server.mjs --port 3458
+   ```
+   Run this in the background. If port 3458 is taken, try 3459.
+
+3. **Tell the user** to open `http://localhost:3458` in their browser.
+
+4. **Stay available.** The user may come back with questions about what
+   they see, or ask you to create/update projects and actions based on
+   their review. Use `scripts/pib-db.js` for any mutations they request.
+
+## Notes
+
+- The server must keep running for the UI to work. If the user ends
+  the conversation, the server stops.
+- The UI shows projects filterable by status (active, paused, done,
+  dropped, someday) and their actions.
+- Actions can be created, completed, and edited directly in the browser.

package/templates/hooks/memory-post-compact.sh

@@ -1,43 +0,0 @@
-#!/bin/bash
-# PostCompact hook — capture session context before it's lost
-#
-# Fires on: manual (/compact) and auto (context limit) compaction
-# Output: read-only (observability only, 10K char cap)
-# Design: D1 (absolute venv path), D2 (never block), D3 (graceful degradation)
-
-VENV_PYTHON="$HOME/.claude-cabinet/omega-venv/bin/python3"
-ADAPTER="scripts/cabinet-memory-adapter.py"
-
-# D3: graceful degradation — if venv or adapter missing, exit silently
-if [ ! -x "$VENV_PYTHON" ] || [ ! -f "$ADAPTER" ]; then
-    exit 0
-fi
-
-# Read hook input from stdin (includes compact_summary)
-INPUT=$(cat)
-
-# Call adapter — pipe hook input as stdin for capture
-RESULT=$(echo "$INPUT" | "$VENV_PYTHON" "$ADAPTER" capture 2>/dev/null)
-
-# Log result for observability (PostCompact output is read-only)
-STORED=$(echo "$RESULT" | "$VENV_PYTHON" -c "
-import sys, json
-try:
-    data = json.load(sys.stdin)
-    if data.get('ok'):
-        count = data.get('stored', 0)
-        if count:
-            print(f'cabinet-memory: captured {count} memories from compaction')
-        else:
-            print('cabinet-memory: no memories captured (nothing noteworthy)')
-    else:
-        print(f'cabinet-memory: {data.get(\"error\", \"unknown error\")}')
-except:
-    pass
-" 2>/dev/null)
-
-if [ -n "$STORED" ]; then
-    echo "$STORED"
-fi
-
-exit 0

package/templates/hooks/memory-session-start.sh

@@ -1,59 +0,0 @@
-#!/bin/bash
-# SessionStart hook — surface relevant memories via omega
-#
-# Fires on: startup, resume, compact (not clear — fresh context)
-# Output: relevant memories injected into session context
-# Design: D1 (absolute venv path), D2 (never block), D3 (graceful degradation)
-
-VENV_PYTHON="$HOME/.claude-cabinet/omega-venv/bin/python3"
-ADAPTER="scripts/cabinet-memory-adapter.py"
-
-# D3: graceful degradation — if venv or adapter missing, warn but don't block
-if [ ! -x "$VENV_PYTHON" ] || [ ! -f "$ADAPTER" ]; then
-    echo ""
-    echo "**Note:** Memory module is installed but omega is not available."
-    echo "Semantic memory (decisions, lessons, preferences) is not being captured or recalled."
-    echo "Run \`npx create-claude-cabinet\` to set up the omega venv."
-    exit 0
-fi
-
-# Read hook input from stdin
-INPUT=$(cat)
-
-# Extract source field to skip /clear (fresh context, no memories needed)
-SOURCE=$(echo "$INPUT" | "$VENV_PYTHON" -c "
-import sys, json
-try:
-    data = json.load(sys.stdin)
-    print(data.get('source', 'startup'))
-except:
-    print('startup')
-" 2>/dev/null)
-
-if [ "$SOURCE" = "clear" ]; then
-    exit 0
-fi
-
-# Call adapter — pipe hook input as stdin
-RESULT=$(echo "$INPUT" | "$VENV_PYTHON" "$ADAPTER" welcome 2>/dev/null)
-
-# Extract context from result
-CONTEXT=$(echo "$RESULT" | "$VENV_PYTHON" -c "
-import sys, json
-try:
-    data = json.load(sys.stdin)
-    if data.get('ok') and data.get('context'):
-        print(data['context'])
-except:
-    pass
-" 2>/dev/null)
-
-# Output context to stdout — SessionStart hook stdout becomes session context
-if [ -n "$CONTEXT" ]; then
-    echo ""
-    echo "## Recalled Memories (omega)"
-    echo ""
-    echo "$CONTEXT"
-fi
-
-exit 0