get-shit-done-cc 1.9.1 → 1.9.3

package/README.md

@@ -324,50 +324,6 @@ Use for: bug fixes, small features, config changes, one-off tasks.
 
 ## Why It Works
 
-### Codebase Intelligence
-
-GSD learns your codebase patterns automatically. As Claude writes code, a PostToolUse hook indexes exports and imports, detects naming conventions, and builds a semantic understanding of your codebase.
-
-**How it works:**
-
-1. **Automatic learning** — Every time Claude writes or edits a JS/TS file, the hook extracts exports/imports and updates `.planning/intel/index.json`
-2. **Convention detection** — Analyzes exports for naming patterns (camelCase, PascalCase, etc.), identifies directory purposes, detects file suffixes
-3. **Graph database** — Stores entity relationships in SQLite for dependency analysis
-4. **Context injection** — At session start, injects a summary into Claude's context so it knows your codebase structure and conventions
-
-**For existing codebases:**
-
-```
-/gsd:analyze-codebase
-```
-
-Performs a bulk scan of your codebase to bootstrap the intelligence layer. Works standalone — no `/gsd:new-project` required. After initial analysis, hooks continue incremental learning.
-
-**Query the graph:**
-
-```
-/gsd:query-intel dependents src/lib/db.ts   # What depends on this file?
-/gsd:query-intel hotspots                    # Most-depended-on files
-```
-
-**Files created:**
-
-| File | Purpose |
-|------|---------|
-| `.planning/intel/index.json` | File exports and imports index |
-| `.planning/intel/conventions.json` | Detected patterns (naming, directories, suffixes) |
-| `.planning/intel/graph.db` | SQLite database with entity relationships |
-| `.planning/intel/summary.md` | Concise context for session injection |
-
-**Benefits:**
-
-- Claude follows your naming conventions automatically
-- New files go in the right directories
-- Consistency maintained across sessions
-- Query blast radius before refactoring
-- Identify high-impact hotspot files
-- No manual documentation of patterns needed
-
 ### Context Engineering
 
 Claude Code is incredibly powerful *if* you give it the context it needs. Most people don't.
@@ -478,8 +434,6 @@ You're never locked in. The system adapts.
 | Command | What it does |
 |---------|--------------|
 | `/gsd:map-codebase` | Analyze existing codebase before new-project |
-| `/gsd:analyze-codebase` | Bootstrap codebase intelligence for existing projects |
-| `/gsd:query-intel <type>` | Query dependency graph (dependents, hotspots) |
 
 ### Phase Management
 

package/agents/gsd-executor.md

@@ -52,20 +52,6 @@ git check-ignore -q .planning 2>/dev/null && COMMIT_PLANNING_DOCS=false
 Store `COMMIT_PLANNING_DOCS` for use in git operations.
 </step>
 
-<step name="load_codebase_intelligence">
-Check for codebase intelligence:
-
-```bash
-cat .planning/intel/summary.md 2>/dev/null
-```
-
-If exists:
-- Follow detected naming conventions when writing code
-- Place new files in directories that match their purpose
-- Use established patterns (camelCase, PascalCase, etc.)
-
-This context helps maintain codebase consistency during execution.
-</step>
 
 <step name="load_plan">
 Read the plan file provided in your prompt context.

package/agents/gsd-planner.md

@@ -416,9 +416,6 @@ Output: [What artifacts will be created]
 @.planning/ROADMAP.md
 @.planning/STATE.md
 
-# Codebase intelligence (if exists)
-@.planning/intel/summary.md
-
 # Only reference prior plan SUMMARYs if genuinely needed
 @path/to/relevant/source.ts
 </context>
@@ -1039,25 +1036,6 @@ If exists, load relevant documents based on phase type:
 | (default) | STACK.md, ARCHITECTURE.md |
 </step>
 
-<step name="load_codebase_intelligence">
-Check for codebase intelligence:
-
-```bash
-cat .planning/intel/summary.md 2>/dev/null
-```
-
-If exists, this provides:
-- File count and structure overview
-- Detected naming conventions (use these when creating new files)
-- Key directories and their purposes
-- Export patterns
-
-**How to use:**
-- Follow detected naming conventions when planning new exports
-- Place new files in directories that match their purpose
-- Reference existing patterns when describing implementation
-</step>
-
 <step name="identify_phase">
 Check roadmap and existing phases:
 

package/bin/install.js

@@ -181,6 +181,9 @@ function cleanupOrphanedHooks(settings) {
   const orphanedHookPatterns = [
     'gsd-notify.sh',  // Removed in v1.6.x
     'hooks/statusline.js',  // Renamed to gsd-statusline.js in v1.9.0
+    'gsd-intel-index.js',  // Removed in v1.9.2
+    'gsd-intel-session.js',  // Removed in v1.9.2
+    'gsd-intel-prune.js',  // Removed in v1.9.2
   ];
 
   let cleaned = false;
@@ -418,72 +421,6 @@ function install(isGlobal) {
     console.log(`  ${green}✓${reset} Configured update check hook`);
   }
 
-  // Register intel hooks for codebase intelligence
-  const intelIndexCommand = isGlobal
-    ? 'node "$HOME/.claude/hooks/gsd-intel-index.js"'
-    : 'node .claude/hooks/gsd-intel-index.js';
-
-  const intelSessionCommand = isGlobal
-    ? 'node "$HOME/.claude/hooks/gsd-intel-session.js"'
-    : 'node .claude/hooks/gsd-intel-session.js';
-
-  // PostToolUse hook for indexing
-  if (!settings.hooks.PostToolUse) {
-    settings.hooks.PostToolUse = [];
-  }
-
-  const hasIntelIndexHook = settings.hooks.PostToolUse.some(entry =>
-    entry.hooks && entry.hooks.some(h => h.command && h.command.includes('gsd-intel-index'))
-  );
-
-  if (!hasIntelIndexHook) {
-    settings.hooks.PostToolUse.push({
-      hooks: [{
-        type: 'command',
-        command: intelIndexCommand
-      }]
-    });
-    console.log(`  ${green}✓${reset} Configured intel indexing hook`);
-  }
-
-  // SessionStart hook for context injection
-  const hasIntelSessionHook = settings.hooks.SessionStart.some(entry =>
-    entry.hooks && entry.hooks.some(h => h.command && h.command.includes('gsd-intel-session'))
-  );
-
-  if (!hasIntelSessionHook) {
-    settings.hooks.SessionStart.push({
-      hooks: [{
-        type: 'command',
-        command: intelSessionCommand
-      }]
-    });
-    console.log(`  ${green}✓${reset} Configured intel session hook`);
-  }
-
-  // Stop hook for pruning deleted files
-  const intelPruneCommand = isGlobal
-    ? 'node "$HOME/.claude/hooks/gsd-intel-prune.js"'
-    : 'node .claude/hooks/gsd-intel-prune.js';
-
-  if (!settings.hooks.Stop) {
-    settings.hooks.Stop = [];
-  }
-
-  const hasIntelPruneHook = settings.hooks.Stop.some(entry =>
-    entry.hooks && entry.hooks.some(h => h.command && h.command.includes('gsd-intel-prune'))
-  );
-
-  if (!hasIntelPruneHook) {
-    settings.hooks.Stop.push({
-      hooks: [{
-        type: 'command',
-        command: intelPruneCommand
-      }]
-    });
-    console.log(`  ${green}✓${reset} Configured intel prune hook`);
-  }
-
   return { settingsPath, settings, statuslineCommand };
 }
 

package/commands/gsd/help.md

@@ -76,17 +76,6 @@ Map an existing codebase for brownfield projects.
 
 Usage: `/gsd:map-codebase`
 
-**`/gsd:analyze-codebase`**
-Bootstrap codebase intelligence for existing projects.
-
-- Scans all JS/TS files and extracts exports/imports
-- Detects naming conventions, directory patterns, file suffixes
-- Creates `.planning/intel/` with index, conventions, and summary
-- Works standalone (no `/gsd:new-project` required)
-- After initial scan, PostToolUse hook continues incremental learning
-
-Usage: `/gsd:analyze-codebase`
-
 ### Phase Planning
 
 **`/gsd:discuss-phase <number>`**
@@ -339,19 +328,6 @@ Quick switch model profile for GSD agents.
 
 Usage: `/gsd:set-profile budget`
 
-### Codebase Intelligence
-
-**`/gsd:query-intel <type> [path]`**
-Query the codebase intelligence graph database.
-
-- `dependents <file>` — What files depend on this? (blast radius)
-- `hotspots` — Which files have the most dependents?
-
-Requires `/gsd:analyze-codebase` to build the graph first.
-
-Usage: `/gsd:query-intel dependents src/lib/db.ts`
-Usage: `/gsd:query-intel hotspots`
-
 ### Utility Commands
 
 **`/gsd:help`**
@@ -389,10 +365,6 @@ Usage: `/gsd:update`
 │   └── done/             # Completed todos
 ├── debug/                # Active debug sessions
 │   └── resolved/         # Archived resolved issues
-├── intel/                # Codebase intelligence (auto-populated)
-│   ├── index.json        # File exports and imports
-│   ├── conventions.json  # Detected patterns
-│   └── summary.md        # Context for session injection
 ├── codebase/             # Codebase map (brownfield projects)
 │   ├── STACK.md          # Languages, frameworks, dependencies
 │   ├── ARCHITECTURE.md   # Patterns, layers, data flow

package/commands/gsd/new-project.md

@@ -19,7 +19,6 @@ This is the most leveraged moment in any project. Deep questioning here means be
 - `.planning/PROJECT.md` — project context
 - `.planning/config.json` — workflow preferences
 - `.planning/research/` — domain research (optional)
-- `.planning/intel/` — codebase intelligence (auto-populated by hooks)
 - `.planning/REQUIREMENTS.md` — scoped requirements
 - `.planning/ROADMAP.md` — phase structure
 - `.planning/STATE.md` — project memory
@@ -58,14 +57,7 @@ This is the most leveraged moment in any project. Deep questioning here means be
    fi
    ```
 
-3. **Create intel directory for codebase intelligence:**
-   ```bash
-   mkdir -p .planning/intel
-   ```
-
-   This prepares the directory for the PostToolUse hook to populate with index.json, conventions.json, and summary.md as Claude writes code.
-
-4. **Detect existing code (brownfield detection):**
+3. **Detect existing code (brownfield detection):**
    ```bash
    CODE_FILES=$(find . -name "*.ts" -o -name "*.js" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.swift" -o -name "*.java" 2>/dev/null | grep -v node_modules | grep -v .git | head -20)
    HAS_PACKAGE=$([ -f package.json ] || [ -f requirements.txt ] || [ -f Cargo.toml ] || [ -f go.mod ] || [ -f Package.swift ] && echo "yes")
@@ -305,29 +297,39 @@ All recommended for important projects. Skip for quick experiments.
 questions: [
   {
     header: "Research",
-    question: "Spawn Plan Researcher? (researches domain before planning — adds tokens/time)",
+    question: "Research before planning each phase? (adds tokens/time)",
     multiSelect: false,
     options: [
-      { label: "Yes (Recommended)", description: "Research phase goals before planning" },
-      { label: "No", description: "Skip research, plan directly" }
+      { label: "Yes (Recommended)", description: "Investigate domain, find patterns, surface gotchas" },
+      { label: "No", description: "Plan directly from requirements" }
     ]
   },
   {
     header: "Plan Check",
-    question: "Spawn Plan Checker? (verifies plans before execution — adds tokens/time)",
+    question: "Verify plans will achieve their goals? (adds tokens/time)",
     multiSelect: false,
     options: [
-      { label: "Yes (Recommended)", description: "Verify plans meet phase goals" },
-      { label: "No", description: "Skip plan verification" }
+      { label: "Yes (Recommended)", description: "Catch gaps before execution starts" },
+      { label: "No", description: "Execute plans without verification" }
     ]
   },
   {
     header: "Verifier",
-    question: "Spawn Execution Verifier? (verifies phase completion — adds tokens/time)",
+    question: "Verify work satisfies requirements after each phase? (adds tokens/time)",
+    multiSelect: false,
+    options: [
+      { label: "Yes (Recommended)", description: "Confirm deliverables match phase goals" },
+      { label: "No", description: "Trust execution, skip verification" }
+    ]
+  },
+  {
+    header: "Model Profile",
+    question: "Which AI models for planning agents?",
     multiSelect: false,
     options: [
-      { label: "Yes (Recommended)", description: "Verify must-haves after execution" },
-      { label: "No", description: "Skip post-execution verification" }
+      { label: "Balanced (Recommended)", description: "Sonnet for most agents — good quality/cost ratio" },
+      { label: "Quality", description: "Opus for research/roadmap — higher cost, deeper analysis" },
+      { label: "Budget", description: "Haiku where possible — fastest, lowest cost" }
     ]
   }
 ]
@@ -341,6 +343,7 @@ Create `.planning/config.json` with all settings:
   "depth": "quick|standard|comprehensive",
   "parallelization": true|false,
   "commit_docs": true|false,
+  "model_profile": "quality|balanced|budget",
   "workflow": {
     "research": true|false,
     "plan_check": true|false,
@@ -354,7 +357,7 @@ Create `.planning/config.json` with all settings:
 - Add `.planning/` to `.gitignore` (create if needed)
 
 **If commit_docs = Yes:**
-- Add `.planning/intel/` to `.gitignore` (intel is always local — changes constantly, can be regenerated)
+- No additional gitignore entries needed
 
 **Commit config.json:**
 
@@ -970,7 +973,6 @@ Present completion with next steps:
   - `ARCHITECTURE.md`
   - `PITFALLS.md`
   - `SUMMARY.md`
-- `.planning/intel/` (created empty, populated by hooks during coding)
 - `.planning/REQUIREMENTS.md`
 - `.planning/ROADMAP.md`
 - `.planning/STATE.md`

package/commands/gsd/plan-phase.md

@@ -249,9 +249,6 @@ RESEARCH_CONTENT=$(cat "${PHASE_DIR}"/*-RESEARCH.md 2>/dev/null)
 # Gap closure files (only if --gaps mode)
 VERIFICATION_CONTENT=$(cat "${PHASE_DIR}"/*-VERIFICATION.md 2>/dev/null)
 UAT_CONTENT=$(cat "${PHASE_DIR}"/*-UAT.md 2>/dev/null)
-
-# Codebase intelligence (if exists)
-INTEL_CONTENT=$(cat .planning/intel/summary.md 2>/dev/null)
 ```
 
 ## 8. Spawn gsd-planner Agent
@@ -292,11 +289,6 @@ Fill prompt with inlined content and spawn:
 {verification_content}
 {uat_content}
 
-**Codebase Intel (if exists):**
-<codebase-intel>
-{intel_content}
-</codebase-intel>
-
 </planning_context>
 
 <downstream_consumer>

package/get-shit-done/workflows/execute-plan.md

@@ -598,8 +598,7 @@ Execute each task in the prompt. **Deviations are normal** - handle them automat
    - Continue implementing, applying rules as needed
    - Run the verification
    - Confirm done criteria met
-   - **Update intel entities** for modified files (see `<update_intel_entity>` below)
-   - **Commit the task** (see `<task_commit>` below) - includes entity files in commit
+   - **Commit the task** (see `<task_commit>` below)
    - Track task completion and commit hash for Summary documentation
    - Continue to next task
 
@@ -928,148 +927,6 @@ None - plan executed exactly as written.
 
 </deviation_documentation>
 
-<update_intel_entity>
-
-## Update Codebase Intelligence Entity
-
-**Trigger:** After each task's `<done>` criteria met, BEFORE committing.
-
-This step documents your understanding of modified files. The knowledge base self-evolves as you work.
-
-**1. Get files from the just-completed task:**
-
-Check the task's `<files>` list. If no `<files>` attribute, use `git status --short` to identify modified files.
-
-**2. For each file, determine if significant:**
-
-**Skip these patterns (not worth indexing):**
-```bash
-# Build/generated
-node_modules/*, .next/*, dist/*, build/*, .git/*
-
-# Tests (their targets are more valuable)
-*.test.*, *.spec.*, __tests__/*, __mocks__/*
-
-# Config files (change rarely, low context value)
-package.json, package-lock.json, tsconfig.json, *.config.*, *.config.js, *.config.ts
-
-# Environment and locks
-.env*, *.lock, *.log, yarn.lock, pnpm-lock.yaml
-```
-
-If file matches skip pattern: continue to next file.
-
-**3. Derive entity path:**
-
-```bash
-# Convert file path to entity filename
-# src/lib/auth.ts → src-lib-auth.md
-# app/api/users/route.ts → app-api-users-route.md
-
-FILE_PATH="$1"
-ENTITY_NAME=$(echo "$FILE_PATH" | sed 's|^[./]*||' | tr '/' '-' | sed 's/\.[^.]*$//')
-ENTITY_PATH=".planning/intel/entities/${ENTITY_NAME}.md"
-```
-
-**4. Create intel directory if needed:**
-
-```bash
-mkdir -p .planning/intel/entities
-```
-
-**5. Check if entity exists:**
-
-```bash
-if [ -f "$ENTITY_PATH" ]; then
-  ACTION="update"
-else
-  ACTION="create"
-fi
-```
-
-**6. Create or update entity:**
-
-Use template from `~/.claude/get-shit-done/templates/entity.md`.
-
-Fill fields based on what you just built:
-
-| Field | Source |
-|-------|--------|
-| `path` | Absolute path to file |
-| `type` | Infer: module, component, util, config, api, hook |
-| `updated` | Today's date (YYYY-MM-DD) |
-| `status` | active (unless you're deprecating) |
-| **Purpose** | What you understand this file does |
-| **Exports** | Extract from the code you just wrote |
-| **Dependencies** | `[[slugified-path]]` for internal, plain for external |
-| **Used By** | Add callers if you know them from this session |
-| **Notes** | Gotchas, patterns, warnings discovered |
-
-**If updating existing entity:**
-- Read current content first
-- Preserve Used By entries you didn't touch
-- Update sections that changed
-- Don't remove information unless it's wrong
-
-**7. Write entity file:**
-
-```bash
-# Write the entity content
-cat > "$ENTITY_PATH" << 'EOF'
----
-path: {path}
-type: {type}
-updated: {today}
-status: active
----
-
-# {filename}
-
-## Purpose
-
-{purpose}
-
-## Exports
-
-{exports}
-
-## Dependencies
-
-{dependencies}
-
-## Used By
-
-{used_by}
-
-## Notes
-
-{notes}
-EOF
-```
-
-**8. Verify entity was created/updated:**
-
-```bash
-head -10 "$ENTITY_PATH"
-```
-
-**9. Stage entity file:**
-
-Entity files are staged along with task code files in the task commit.
-
-```bash
-git add "$ENTITY_PATH"
-```
-
-**Error handling:**
-- If entity creation fails: Log warning, continue to task_commit
-- Entity update is NOT blocking - a failed entity shouldn't stop code from being committed
-- Log: `"Warning: Could not update entity for {file}: {reason}"`
-
-**Target size:** Keep entities concise (30-50 lines). Purpose and Exports are most valuable.
-
-</update_intel_entity>
-
 <tdd_plan_execution>
 ## TDD Plan Execution
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "get-shit-done-cc",
-  "version": "1.9.1",
+  "version": "1.9.3",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
   "bin": {
     "get-shit-done-cc": "bin/install.js"
@@ -36,8 +36,7 @@
   },
   "dependencies": {},
   "devDependencies": {
-    "esbuild": "^0.24.0",
-    "sql.js": "^1.12.0"
+    "esbuild": "^0.24.0"
   },
   "scripts": {
     "build:hooks": "node scripts/build-hooks.js",

package/scripts/build-hooks.js

@@ -1,77 +1,27 @@
 #!/usr/bin/env node
 /**
- * Bundle GSD hooks with dependencies for zero-config installation.
- *
- * sql.js includes a WASM binary that must be inlined for portability.
- * This script bundles hooks into self-contained files that work from any cwd.
+ * Copy GSD hooks to dist for installation.
  */
 
-const esbuild = require('esbuild');
 const fs = require('fs');
 const path = require('path');
 
 const HOOKS_DIR = path.join(__dirname, '..', 'hooks');
 const DIST_DIR = path.join(HOOKS_DIR, 'dist');
 
-// Hooks that need bundling (have npm dependencies)
-const HOOKS_TO_BUNDLE = [
-  'gsd-intel-index.js'
-];
-
-// Hooks that are pure Node.js (just copy)
+// Hooks to copy (pure Node.js, no bundling needed)
 const HOOKS_TO_COPY = [
-  'gsd-intel-session.js',
-  'gsd-intel-prune.js',
   'gsd-check-update.js',
   'gsd-statusline.js'
 ];
 
-async function build() {
+function build() {
   // Ensure dist directory exists
   if (!fs.existsSync(DIST_DIR)) {
     fs.mkdirSync(DIST_DIR, { recursive: true });
   }
 
-  // Bundle hooks with dependencies
-  for (const hook of HOOKS_TO_BUNDLE) {
-    const entryPoint = path.join(HOOKS_DIR, hook);
-    const outfile = path.join(DIST_DIR, hook);
-
-    if (!fs.existsSync(entryPoint)) {
-      console.warn(`Warning: ${hook} not found, skipping`);
-      continue;
-    }
-
-    console.log(`Bundling ${hook}...`);
-
-    await esbuild.build({
-      entryPoints: [entryPoint],
-      bundle: true,
-      platform: 'node',
-      target: 'node18',
-      outfile,
-      format: 'cjs',
-      // Inline WASM as base64 for sql.js
-      loader: {
-        '.wasm': 'binary'
-      },
-      // Don't externalize anything - bundle it all
-      external: [],
-      // Minify for smaller package size
-      minify: true,
-      // Keep function names for debugging
-      keepNames: true,
-      // Handle sql.js WASM loading
-      define: {
-        'process.env.NODE_ENV': '"production"'
-      }
-      // Note: shebang preserved from source file by esbuild
-    });
-
-    console.log(`  → ${outfile}`);
-  }
-
-  // Copy pure Node.js hooks (no bundling needed)
+  // Copy hooks to dist
   for (const hook of HOOKS_TO_COPY) {
     const src = path.join(HOOKS_DIR, hook);
     const dest = path.join(DIST_DIR, hook);
@@ -89,7 +39,4 @@ async function build() {
   console.log('\nBuild complete.');
 }
 
-build().catch(err => {
-  console.error('Build failed:', err);
-  process.exit(1);
-});
+build();