@jacques-ai/cli 0.0.7-alpha.1

package/package.json

@@ -0,0 +1,63 @@
+{
+  "name": "@jacques-ai/cli",
+  "version": "0.0.7-alpha.1",
+  "description": "Jacques CLI TUI for Claude Code context monitoring",
+  "main": "dist/cli.js",
+  "type": "module",
+  "bin": {
+    "jacques": "./dist/cli.js"
+  },
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsc --watch",
+    "start": "node dist/cli.js",
+    "test": "node --experimental-vm-modules ../node_modules/jest/bin/jest.js",
+    "convert-mascot": "tsx scripts/convert-mascot.ts",
+    "prebuild": "npm run convert-mascot",
+    "prepublishOnly": "npm run build"
+  },
+  "dependencies": {
+    "@jacques-ai/core": "0.0.7-alpha.1",
+    "@jacques-ai/server": "0.0.7-alpha.1",
+    "commander": "^12.1.0",
+    "ink": "^6.6.0",
+    "react": "^19.2.4",
+    "ws": "^8.18.0"
+  },
+  "devDependencies": {
+    "@types/jest": "^29.5.14",
+    "@types/node": "^22.10.0",
+    "@types/react": "^19.2.10",
+    "@types/ws": "^8.5.13",
+    "jest": "^29.7.0",
+    "jimp": "^0.22.10",
+    "ts-jest": "^29.2.0",
+    "tsx": "^4.7.0",
+    "typescript": "^5.7.0"
+  },
+  "files": [
+    "dist",
+    "hooks",
+    "skills"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/gregory-lime/jacques.git",
+    "directory": "cli"
+  },
+  "homepage": "https://github.com/gregory-lime/jacques#readme",
+  "bugs": {
+    "url": "https://github.com/gregory-lime/jacques/issues"
+  },
+  "license": "MIT",
+  "keywords": [
+    "claude-code",
+    "context-monitor",
+    "ai",
+    "coding-assistant",
+    "mcp"
+  ],
+  "engines": {
+    "node": ">=20.0.0"
+  }
+}

package/skills/jacques-continue/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: jacques-continue
+description: Load the latest handoff document and continue work from a previous session
+---
+
+## Steps
+
+1. Look for handoff files in `.jacques/handoffs/` directory
+2. Find the most recent file (files are named `YYYY-MM-DDTHH-mm-ss-handoff.md`)
+3. Read and process the full content
+4. **Register active plan** (if handoff has a plan path):
+   - Extract the plan file path from the "Plan Status" section
+   - Call the Jacques API to register it as an active plan for cross-session tracking
+
+## Registering Active Plans
+
+If the handoff contains a plan file path (e.g., in "Plan Status" section), register it with Jacques:
+
+```bash
+# Get the current project path and encode it
+PROJECT_PATH=$(pwd)
+ENCODED_PATH=$(echo -n "$PROJECT_PATH" | base64 | tr -d '\n')
+
+# Register the plan as active
+curl -s -X POST "http://localhost:4243/api/projects/$ENCODED_PATH/active-plans" \
+  -H "Content-Type: application/json" \
+  -d "{\"planPath\": \"/path/to/plan.md\"}"
+```
+
+This allows Jacques to track progress across multiple sessions working on the same plan.
+
+## After Loading
+
+You MUST:
+
+1. **Register the active plan** (silently, if plan path exists):
+   - Run the curl command above with the plan path from the handoff
+   - Don't mention this to the user unless it fails
+
+2. **Acknowledge** with the handoff timestamp:
+   > "Loaded handoff from [date/time]. Here's where we are:"
+
+3. **Summarize** the key context (2-3 sentences):
+   - Current task and goal
+   - Progress state (what's done, what's in progress)
+   - Any blockers or warnings to keep in mind
+
+4. **Note the plan file** (if Plan Status section exists):
+   - If the handoff has a "Plan Status" section with a plan file path, note it
+   - You will need to edit this file to mark phases complete as you work
+   - See CLAUDE.md "Jacques" section for plan tracking instructions
+
+5. **Propose the immediate next step**:
+   > "Ready to continue with: [first item from Next Steps]"
+   >
+   > "Would you like to proceed with this, or work on something else?"
+
+## Example Response
+
+> Loaded handoff from 2026-01-31 14:30.
+>
+> **Context**: You were implementing the session handoff system - 6/8 extractors are complete,
+> the orchestrator needs the quality gate added. There's an open issue with token budget math
+> that needs fixing.
+>
+> **Plan file**: `/Users/gole/.claude/plans/iridescent-frolicking-walrus.md`
+>
+> Ready to continue with: **Add quality gate to jacques-orchestrator.md**
+>
+> Shall I proceed with this, or would you prefer to work on something else?
+
+## If No Handoffs Found
+
+If `.jacques/handoffs/` is empty or doesn't exist:
+
+> No handoff documents found for this project.
+>
+> Would you like to:
+> - Tell me about what you were working on, or
+> - Start fresh with a new task?
+
+## Important
+
+- Do NOT immediately start working on tasks
+- Wait for user confirmation before proceeding
+- If the handoff mentions blockers or warnings, mention them upfront
+- The active plan registration happens silently - don't mention it unless it fails

package/skills/jacques-handoff/SKILL.md

@@ -0,0 +1,147 @@
+---
+name: jacques-handoff
+description: Generate a session handoff document for continuing work in a new session
+---
+
+## CRITICAL: No File Operations
+
+DO NOT use Read, Glob, Grep, Bash, or any tool except Write.
+All necessary information is provided in the "Pre-Extracted Session Context" section below.
+The context was already extracted from CLAUDE.md and the conversation transcript.
+
+If you use any tool besides Write, you are wasting tokens.
+
+---
+
+## Instructions
+
+Generate a comprehensive session handoff document (~1000 tokens) by extracting from the CURRENT conversation context. Be thorough and specific.
+
+**Save to:** `.jacques/handoffs/{YYYY-MM-DDTHH-mm-ss}-handoff.md`
+
+---
+
+## Extraction Priority
+
+1. **Use the Project Info section** - The pre-extracted context includes project information from CLAUDE.md. Use this instead of reading files.
+
+2. **Recall user decisions** - When the user said "yes do that", "no use this instead", "let's go with option 2" - these are KEY DECISIONS to capture.
+
+3. **Use the Plan Context section** - The pre-extracted context includes any active plans. Use this instead of searching for plan files.
+
+---
+
+## Required Sections
+
+### Header
+```markdown
+# Session Handoff
+
+> Project: [name] | Generated: [timestamp]
+```
+
+### Project Context (from pre-extracted context)
+Brief orientation for the next session:
+- What is this project?
+- Tech stack
+- Key directories (2-3 most relevant)
+
+Use the "Project Info" section from the pre-extracted context.
+
+### Current Task (2-3 sentences)
+What specific problem/feature are we working on? What's the end goal?
+
+### Progress Made (DETAILED)
+Group by component/feature. Include:
+- **Numbered items** with clear descriptions
+- **File paths** (absolute) with what was created/modified
+- **Function names** where relevant
+- **Status markers**: [DONE], [PARTIAL], [BLOCKED]
+
+```markdown
+**Completed - [Feature Name]:**
+
+1. **Component Name** (`/absolute/path/file.ts`)
+   - `functionName()` - what it does
+   - Technical detail worth noting
+
+2. **Another Component** (`/absolute/path/other.ts`)
+   - What it does
+```
+
+### User Decisions (IMPORTANT)
+Capture moments when the user chose between approaches:
+
+| Decision | User's Choice | Context |
+|----------|---------------|---------|
+| "Should we use X or Y?" | User chose Y | Because [reason if given] |
+| Architecture question | User's direction | What they wanted |
+
+Look for:
+- "Yes, do that" / "No, try this instead"
+- "Let's go with option X"
+- "I prefer..." / "Use..."
+- Rejections of suggestions
+
+### Plan Status (if active plan exists)
+If there was a plan file or planning discussion:
+
+```markdown
+**Plan:** [filename or inline plan]
+
+Progress:
+☑ Task 1: Description [DONE]
+☑ Task 2: Description [DONE]
+☐ Task 3: Description ← CURRENT POSITION
+□ Task 4: Description [REMAINING]
+□ Task 5: Description [REMAINING]
+
+Notes:
+- Task 2 took longer because [reason]
+- Task 3 is blocked by [issue]
+```
+
+If no plan: "No active plan file."
+
+### Blockers & Bugs
+- Issues hit and their resolution status
+- If none: "None in this session."
+
+### What Didn't Work
+Failed approaches that the next session should NOT repeat:
+- Approach tried → Why it failed
+- If none: "None in this session."
+
+### Warnings & Gotchas
+Things the next session MUST know upfront:
+- API quirks discovered
+- Configuration requirements
+- Edge cases found
+- "Watch out for X"
+
+### Next Steps (numbered, priority order)
+1. **First priority** - specific action with file paths
+2. **Second priority** - another specific action
+3. Continue...
+
+---
+
+## Quality Requirements
+
+- **Be specific**: "`listGoogleDriveFiles()` with pagination" not "added file listing"
+- **Absolute file paths**: For all files mentioned
+- **Function names**: Name actual functions/components
+- **User decisions matter**: Capture what the user chose
+- **~1000 tokens**: Comprehensive but focused
+
+---
+
+## After Saving
+
+IMPORTANT: Output this EXACT message (replace {filename} with the actual filename):
+
+> Handoff saved to `.jacques/handoffs/{filename}`
+>
+> To continue in a new session, run `/jacques-continue`
+
+Do NOT say "jacques-paste" or mention "pasting". The correct skill name is `/jacques-continue`.