cc-sidebar 0.1.5 → 0.1.7

package/README.md

@@ -128,7 +128,7 @@ cc-sidebar includes skills that integrate with Claude Code:
 
 | Skill | Trigger | What it does |
 |-------|---------|--------------|
-| `/brain-dump` | `/brain-dump` | Interview to extract tasks from messy thoughts, creates plan + todos |
+| `/clarify` | `/clarify` | Interview to clarify tasks, creates plan + todos (works for new or existing tasks) |
 | `/prioritize` | `/prioritize` | Re-prioritize all sidebar tasks as a staff engineer |
 | `sidebar-awareness` | (always on) | Gives Claude context about sidebar data files |
 
@@ -142,7 +142,7 @@ cp -r ~/.bun/install/global/node_modules/cc-sidebar/skills/* ~/.claude/skills/
 Or install individually:
 
 ```bash
-cp -r ~/.bun/install/global/node_modules/cc-sidebar/skills/brain-dump ~/.claude/skills/
+cp -r ~/.bun/install/global/node_modules/cc-sidebar/skills/clarify ~/.claude/skills/
 cp -r ~/.bun/install/global/node_modules/cc-sidebar/skills/prioritize ~/.claude/skills/
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-sidebar",
-  "version": "0.1.5",
+  "version": "0.1.7",
   "description": "Visual sidebar for managing todos, tasks, and context alongside Claude Code",
   "author": "Tyler Nishida",
   "license": "MIT",
@@ -24,7 +24,8 @@
   "files": [
     "src",
     "skills",
-    "commands"
+    "commands",
+    "scripts"
   ],
   "scripts": {
     "start": "bun run src/cli.ts",

package/scripts/statusline.sh

@@ -0,0 +1,61 @@
+#!/bin/bash
+# Claude Code statusline script for claude-sidebar
+# Receives JSON from Claude Code via stdin, extracts key metrics, writes to shared file
+#
+# Install: Add to ~/.claude/settings.json:
+# { "statusline": { "script": "/path/to/claude-sidebar/scripts/statusline.sh" } }
+
+set -e
+
+# Read JSON from stdin
+input=$(cat)
+
+# Extract context window data
+CTX_SIZE=$(echo "$input" | jq -r '.context_window.context_window_size // 200000')
+USAGE=$(echo "$input" | jq -r '.context_window.current_usage // {}')
+INPUT_TOKENS=$(echo "$USAGE" | jq -r '(.input_tokens // 0) + (.cache_creation_input_tokens // 0) + (.cache_read_input_tokens // 0)')
+OUTPUT_TOKENS=$(echo "$input" | jq -r '.context_window.current_usage.output_tokens // 0')
+
+# Calculate context percentage (input + output tokens)
+TOTAL_TOKENS=$((INPUT_TOKENS + OUTPUT_TOKENS))
+if [ "$CTX_SIZE" -gt 0 ]; then
+  CTX_PERCENT=$((TOTAL_TOKENS * 100 / CTX_SIZE))
+else
+  CTX_PERCENT=0
+fi
+
+# Extract cost and duration
+COST=$(echo "$input" | jq -r '.cost.total_cost_usd // 0')
+DURATION_MS=$(echo "$input" | jq -r '.cost.total_duration_ms // 0')
+DURATION_MIN=$((DURATION_MS / 60000))
+
+# Extract model
+MODEL=$(echo "$input" | jq -r '.model.display_name // "Unknown"')
+
+# Get project directory and git info
+PROJECT_DIR=$(echo "$input" | jq -r '.workspace.project_dir // ""')
+BRANCH=""
+REPO=""
+if [ -n "$PROJECT_DIR" ] && [ -d "$PROJECT_DIR" ]; then
+  cd "$PROJECT_DIR" 2>/dev/null || true
+  BRANCH=$(git branch --show-current 2>/dev/null || echo "")
+  REPO=$(basename "$PROJECT_DIR")
+fi
+
+# Ensure directory exists
+mkdir -p ~/.claude-sidebar
+
+# Write processed data
+cat > ~/.claude-sidebar/statusline.json << EOF
+{
+  "contextPercent": $CTX_PERCENT,
+  "contextTokens": $TOTAL_TOKENS,
+  "contextSize": $CTX_SIZE,
+  "costUsd": $COST,
+  "durationMin": $DURATION_MIN,
+  "model": "$MODEL",
+  "branch": "$BRANCH",
+  "repo": "$REPO",
+  "updatedAt": "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
+}
+EOF

package/skills/{brain-dump → clarify}/SKILL.md

@@ -1,36 +1,43 @@
 ---
-name: brain-dump
+name: clarify
 description: |
-  Transform thoughts into structured todos and a plan - works for one task or many.
+  Clarify tasks through conversation - works for new ideas or existing sidebar tasks.
 
-  Use when: (1) You have a mess of ideas and need to organize them into actionable tasks,
-  (2) You want to clarify a single task through conversation before adding it,
-  (3) You need both a plan document and sidebar todos from any input.
+  Use when: (1) You have thoughts/ideas that need clarification before becoming actionable,
+  (2) You want to clarify a single task through conversation,
+  (3) The sidebar sends a task for clarification (via `c` key).
 
-  Triggers: "/brain-dump", "brain dump", "organize my thoughts", "extract todos from this".
+  Triggers: "/clarify", "clarify this", "let me explain this task".
 
   Requires: Claude Code sidebar for todo integration, Atomic Plans for plan output.
 ---
 
-# Brain-Dump Skill
+# Clarify Skill
 
-Transform thoughts into structured, actionable todos with an accompanying plan. Works for one task or many - the process is the same.
+Clarify tasks through structured conversation. Works for both new ideas (creates todos) and existing sidebar tasks (updates them).
 
 ## Invocation
 
-- `/brain-dump` - Start interviewing immediately
-- `/brain-dump [text]` - Process provided text (single task or many), then ask clarifying questions
+- `/clarify` - Start interviewing from scratch
+- `/clarify [text]` - Clarify provided text (single task or many)
+- `/clarify --task-id <id> [task content]` - Clarify existing sidebar task (sent by sidebar `c` key)
 
 ## Process
 
 Follow these steps in order:
 
-### 1. Locate Configuration
+### 1. Detect Mode
+
+Check if invoked with `--task-id`:
+- **With task ID**: Updating an existing sidebar task
+- **Without task ID**: Creating new todo(s) from scratch
+
+### 2. Locate Configuration
 
 Check the project's CLAUDE.md for the Atomic Plans folder path. Look for a section like:
 
 ```markdown
-## Brain-Dump Configuration
+## Clarify Configuration
 Plan folder: /path/to/plans
 ```
 
@@ -46,13 +53,13 @@ Or check if Atomic Plans is already configured:
 2. After they provide a path, ask: "Would you like me to add this to CLAUDE.md so I remember next time?"
 3. If yes, append the configuration to CLAUDE.md
 
-### 2. Interview Phase
+### 3. Interview Phase
 
-The goal is to extract actionable, project-relevant tasks through conversation.
+The goal is to fully understand the task(s) through conversation.
 
-**IMPORTANT: Never short-circuit the process.** Whether the user provides one clear task or a chaotic mess of ideas, always interview to clarify. A "single clear task" still benefits from clarification - edge cases, implementation approach, constraints, etc. Don't ask "is this just one task?" - just proceed with clarification.
+**IMPORTANT: Never short-circuit the process.** Whether the user provides one clear task or a chaotic mess of ideas, always interview to clarify. A "single clear task" still benefits from clarification - edge cases, implementation approach, constraints, etc.
 
-**If the user provided text with the command** (`/brain-dump [text]`):
+**If the user provided text with the command** (`/clarify [text]`):
 - Skip the opening question - they already told you what's on their mind
 - Go straight to AskUserQuestion to clarify specifics:
   - Ambiguous parts that need clarification
@@ -61,29 +68,89 @@ The goal is to extract actionable, project-relevant tasks through conversation.
   - Missing context: priorities, dependencies
   - Anything else you need to fully understand the task(s)
 
-**If no text was provided** (`/brain-dump` alone):
+**If no text was provided** (`/clarify` alone):
 - Start with a plain text invitation (NOT AskUserQuestion):
 
   "What's on your mind? Tell me everything - tasks, concerns, ideas,
-  whatever's floating around. I'll help organize it."
+  whatever's floating around. I'll help clarify and organize it."
 
 - Let the user ramble freely in their response
 - THEN use AskUserQuestion to clarify specifics about what they said
 
+**Interview guidelines:**
+- Don't ask obvious questions - if something is clear from the task description, skip it
+- Be thorough - keep interviewing until you have complete clarity
+- Always include "Anything else I should know?" as a final question
+
 **Key questions to consider** (use AskUserQuestion for these):
 - What's the most important thing here?
 - Are there dependencies between these tasks?
 - What constraints should I know about?
 - Is there anything blocking progress on any of these?
-- Anything else I should know?
 
 **Scope filtering:**
 If the user mentions things unrelated to the current project (personal tasks, other projects), ask:
 "Some of this seems unrelated to [current project]. Should I include those tasks anyway, or focus only on [project]-related work?"
 
-### 3. Extract and Prioritize Todos
+### 4. Create Plan
+
+Create a new plan in the Atomic Plans folder with:
+
+**Filename:** `NNN-clarify-[topic].md` where NNN is the next number in sequence.
+
+**Content:**
+```markdown
+---
+plan: NNN
+title: [Topic]
+state: active
+created: YYYY-MM-DD
+updated: YYYY-MM-DD
+---
+
+# [Topic]
+
+## Intent
+[Summary of what the user wants to accomplish]
+
+## Specs
+[Detailed specifications gathered during interview]
 
-From the interview, identify discrete, actionable tasks. Each todo should be:
+## Context
+[Key decisions, constraints, and context gathered during interview]
+
+## Next
+- [ ] Execute the task(s)
+```
+
+### 5. Update or Create Todos
+
+**If updating existing task** (has `--task-id`):
+
+Update the existing task in the sidebar:
+
+```bash
+node << 'SCRIPT'
+const fs = require('fs');
+const crypto = require('crypto');
+const path = require('path');
+const sidebarDir = path.join(require('os').homedir(), '.claude-sidebar');
+const hash = crypto.createHash('sha256').update(process.cwd()).digest('hex').slice(0, 12);
+const tasksPath = path.join(sidebarDir, 'projects', hash, 'tasks.json');
+let tasks = JSON.parse(fs.readFileSync(tasksPath, 'utf-8'));
+const task = tasks.find(t => t.id === 'TASK_ID_HERE');  // REPLACE with actual task ID
+if (task) {
+  task.clarified = true;
+  task.planPath = 'PLAN_FILENAME.md';  // REPLACE with actual plan filename
+  fs.writeFileSync(tasksPath, JSON.stringify(tasks, null, 2));
+  console.log('Task clarified and linked to plan');
+}
+SCRIPT
+```
+
+**If creating new todos** (no `--task-id`):
+
+Extract discrete, actionable tasks from the interview. Each todo should be:
 - **Specific**: Clear what needs to be done
 - **Actionable**: Can be worked on independently
 - **Scoped**: Relevant to the current project (unless user said otherwise)
@@ -95,20 +162,9 @@ Assign each task a numeric priority (1 = most important). Consider:
 - **Impact**: High-value features over nice-to-haves
 - **Effort**: Quick wins can be prioritized to build momentum
 
-Mark the top 3 most important tasks as "recommended" (shown with ★ in sidebar).
-
-### 4. Write Todos to Sidebar
+Mark the top 3 most important tasks as "recommended" (shown with star in sidebar).
 
-Write the extracted todos to the **project-specific** tasks file.
-
-**IMPORTANT:** Tasks are stored per-project using a hash of the working directory:
-```
-~/.claude-sidebar/projects/<hash>/tasks.json
-```
-
-**IMPORTANT: Read first, then append.** Do not clobber existing todos.
-
-Use this exact script to write todos (it handles the project hash automatically):
+Write todos to the **project-specific** tasks file:
 
 ```bash
 node << 'SCRIPT'
@@ -129,7 +185,7 @@ let existing = [];
 try { existing = JSON.parse(fs.readFileSync(tasksPath, 'utf-8')); } catch {}
 
 // Plan filename (just the filename, not full path)
-const planPath = "NNN-brain-dump-topic.md";  // REPLACE with actual plan filename
+const planPath = "NNN-clarify-topic.md";  // REPLACE with actual plan filename
 
 // New todos - REPLACE THIS ARRAY with extracted tasks
 // Each task needs: content, priority (1=highest), recommended (true for top 3)
@@ -142,7 +198,7 @@ const newTodos = [
   id: crypto.randomUUID(),
   content: task.content,
   createdAt: new Date().toISOString(),
-  clarified: true,           // Brain-dump IS the clarification process
+  clarified: true,           // Clarify IS the clarification process
   priority: task.priority,   // Numeric priority (1 = most important)
   recommended: task.recommended,  // Top 3 get star indicator
   planPath: planPath         // Links task to the plan file
@@ -155,101 +211,90 @@ console.log('Added ' + newTodos.length + ' todos to sidebar');
 SCRIPT
 ```
 
-### 5. Create Plan
-
-Create a new plan in the Atomic Plans folder with:
-
-**Filename:** `NNN-brain-dump-[topic].md` where NNN is the next number in sequence.
-
-**Content:**
-```markdown
----
-plan: NNN
-title: Brain Dump - [Topic]
-state: active
-created: YYYY-MM-DD
-updated: YYYY-MM-DD
----
-
-# Brain Dump - [Topic]
+### 6. Present and Prompt
 
-## Intent
-[Summary of what the user wants to accomplish]
+After creating/updating todos and plan:
 
-## Extracted Todos
-[List the todos that were created]
+1. Show a summary of what was created/updated
+2. Ask: **"Execute this task now, or save for later?"**
+   - If execute → work on the task immediately
+   - If save → confirm the task is clarified and stop
 
-## Context from Interview
-[Key decisions, constraints, and context gathered during interview]
-
-## Next
-- [ ] Work through todos in sidebar
+**Example for existing task:**
 ```
+Clarified your task and created plan 007-auth-refactor.md
 
-### 6. Present and Wait
-
-After creating todos and plan:
-
-1. Show a summary of what was created:
-   - Number of todos added to sidebar
-   - Link to the plan file
+Task: Refactor authentication module
+Specs: JWT-based, 24hr expiry, refresh tokens...
 
-2. **Do not auto-execute.** Let the user decide what to do next:
-   - Work through todos one by one (select in sidebar, press Enter)
-   - Use clarify mode (`c` key) to add specs to unclarified todos
-   - Use `/ralph-loop` to batch process all todos
+Execute this task now, or save for later?
+```
 
-Example closing message:
+**Example for new tasks:**
 ```
-Created 5 todos in your sidebar and plan 007-brain-dump-auth-refactor.md
+Created 3 todos in your sidebar and plan 008-api-improvements.md
 
 Your todos:
-1. Extract auth logic into separate module
-2. Add unit tests for token validation
-3. Update API endpoints to use new auth module
-4. Document the new auth flow
-5. Remove deprecated auth code
+1. Add rate limiting to API endpoints
+2. Implement request validation
+3. Add API documentation
 
-What would you like to do next?
+Execute the first task now, or save for later?
 ```
 
 ## Relationship to Other Features
 
 | Feature | Purpose | When to Use |
 |---------|---------|-------------|
-| Brain-dump | Clarify + add todos from chat | When you want to describe tasks conversationally (one or many) |
-| Clarify mode (`c` key) | Clarify existing sidebar todo | When task is already in sidebar and needs specs before executing |
+| `/clarify` | Interview and clarify task(s) | When you need to think through a task before doing it |
+| Sidebar `c` key | Invokes `/clarify --task-id` | Quick way to clarify a queued task |
 | `/prioritize` | Re-evaluate and reorder all tasks | When context changes or you want fresh prioritization |
-| Ralph-loop | Batch process todos autonomously | After brain-dump, to work through all todos |
+| Ralph-loop | Batch process todos autonomously | After clarifying, to work through all todos |
 
 ## Example Sessions
 
-### Single Task Example
+### From Sidebar (existing task)
 ```
-User: /brain-dump I need to add shift+enter support for multiline input in the sidebar
+[User presses 'c' on task "Add user authentication"]
+
+Sidebar sends: /clarify --task-id abc123 Add user authentication
+
+Claude: [Uses AskUserQuestion]
+- What auth method? (JWT, session, OAuth?)
+- Any specific security requirements?
+- Which routes need protection?
+
+User: [Answers]
 
-Claude: [Uses AskUserQuestion to clarify]
+Claude: [Creates plan, updates task with clarified=true]
+
+Clarified your task and created plan 005-user-auth.md
+
+Execute this task now, or save for later?
+```
+
+### From Chat (new task)
+```
+User: /clarify I need to add shift+enter support for multiline input
+
+Claude: [Uses AskUserQuestion]
 - Which input modes need this? (adding new todos, editing existing, both?)
 - Should Enter still submit, with Shift+Enter for newlines?
-- Any other keyboard shortcuts you want to add while we're in there?
 
-User: [Answers questions]
+User: [Answers]
 
 Claude: [Creates todo, writes to sidebar, creates plan]
 
 Created 1 todo in your sidebar and plan 009-multiline-input.md
 
-Your todos:
-1. Add shift+enter for multiline input in add/edit modes
-
-Work on this now, or save for later?
+Execute this task now, or save for later?
 ```
 
-### Multiple Tasks Example
+### From Chat (multiple tasks)
 ```
-User: /brain-dump
+User: /clarify
 
-Claude: What's on your mind? Tell me everything - tasks, concerns, ideas.
+Claude: What's on your mind? Tell me everything.
 
 User: ugh so much. the auth is a mess, we're using like 3 different
 patterns. also need to update the docs. oh and there's that bug with
@@ -259,7 +304,7 @@ Claude: [Uses AskUserQuestion]
 - Which auth pattern should we standardize on?
 - Is the session timeout bug blocking anything?
 
-User: [Answers questions]
+User: [Answers]
 
 Claude: [Creates todos, writes to sidebar, creates plan]
 
@@ -267,9 +312,9 @@ Created 4 todos in your sidebar and plan 010-auth-cleanup.md
 
 Your todos:
 1. Standardize auth on JWT pattern
-2. Fix session timeout bug in middleware
+2. Fix session timeout bug
 3. Update auth documentation
 4. Remove deprecated OAuth1 code
 
-What would you like to do next?
+Execute the first task now, or save for later?
 ```

package/src/components/RawSidebar.tsx

@@ -711,47 +711,8 @@ export class RawSidebar {
       const sortedTasks = this.getSortedTasks();
       const task = sortedTasks[this.state.selectedIndex];
       if (task) {
-        const clarifyPrompt = `CLARIFY MODE
-
-TASK ID: ${task.id}
-TASK: ${task.content}
-
-Interview me about this task using AskUserQuestion. Ask about anything relevant: technical implementation, UI/UX, edge cases, concerns, tradeoffs, constraints, dependencies, etc.
-
-Guidelines:
-- Don't ask obvious questions - if something is clear from the task description, don't ask about it
-- Be thorough - keep interviewing until you have complete clarity
-- Always include "Anything else I should know?" as a final question
-
-After the interview:
-1. Write specs to an Atomic Plan file (check project CLAUDE.md for plan folder path)
-2. Update the task in the sidebar using this script:
-
-\`\`\`bash
-node << 'SCRIPT'
-const fs = require('fs');
-const crypto = require('crypto');
-const path = require('path');
-const sidebarDir = path.join(require('os').homedir(), '.claude-sidebar');
-const hash = crypto.createHash('sha256').update(process.cwd()).digest('hex').slice(0, 12);
-const tasksPath = path.join(sidebarDir, 'projects', hash, 'tasks.json');
-let tasks = JSON.parse(fs.readFileSync(tasksPath, 'utf-8'));
-const task = tasks.find(t => t.id === '${task.id}');
-if (task) {
-  task.clarified = true;
-  task.planPath = 'PLAN_FILENAME.md';  // REPLACE with actual plan filename
-  fs.writeFileSync(tasksPath, JSON.stringify(tasks, null, 2));
-  console.log('Task updated with clarified=true and planPath');
-}
-SCRIPT
-\`\`\`
-
-3. Ask me: "Execute this task now, or save for later?"
-   - If I say execute → work on the task
-   - If I say save → just confirm the task is clarified and stop`;
-
-        sendToClaudePane(clarifyPrompt);
-        // Don't activate - let the task stay in queue until user decides
+        // Invoke the clarify skill with task ID
+        sendToClaudePane(`/clarify --task-id ${task.id} ${task.content}`);
         this.render();
         focusClaudePane();
       }

package/src/persistence/store.ts

@@ -52,7 +52,7 @@ export interface Task {
   id: string;
   content: string;
   createdAt: string;
-  clarified?: boolean;      // Was this task clarified via interview/brain-dump?
+  clarified?: boolean;      // Was this task clarified via /clarify skill?
   priority?: number;        // Sort order (lower = higher priority, 1 = most important)
   recommended?: boolean;    // Claude's top picks (shown with star)
   planPath?: string;        // Filename of associated Atomic Plan