@infinitedusky/indusk-mcp 1.9.1 → 1.9.4

package/dist/bin/commands/init.js

@@ -17,18 +17,21 @@ function run(cmd, options) {
         return "";
     }
 }
-function ensureGitignoreMcpJson(projectRoot) {
+function ensureGitignore(projectRoot) {
     const gitignorePath = join(projectRoot, ".gitignore");
+    const entries = ["# MCP config (contains auth tokens)", ".mcp.json"];
     if (existsSync(gitignorePath)) {
         const content = readFileSync(gitignorePath, "utf-8");
-        if (content.includes(".mcp.json"))
+        if (content.includes(".mcp.json")) {
+            console.info("  skip: .gitignore (.mcp.json already ignored)");
             return;
-        writeFileSync(gitignorePath, `${content.trimEnd()}\n\n# MCP config (contains auth tokens)\n.mcp.json\n`);
+        }
+        writeFileSync(gitignorePath, `${content.trimEnd()}\n\n${entries.join("\n")}\n`);
         console.info("  updated: .gitignore (added .mcp.json)");
     }
     else {
-        writeFileSync(gitignorePath, "# MCP config (contains auth tokens)\n.mcp.json\n");
-        console.info("  created: .gitignore (with .mcp.json)");
+        writeFileSync(gitignorePath, `${entries.join("\n")}\n`);
+        console.info("  create: .gitignore (with .mcp.json)");
     }
 }
 function createCgcIgnore(projectRoot) {
@@ -43,6 +46,9 @@ function createCgcIgnore(projectRoot) {
         "dist/",
         "build/",
         ".git/",
+        ".jj/",
+        ".indusk/",
+        ".claude/",
         "*.png",
         "*.jpg",
         "*.svg",
@@ -664,13 +670,12 @@ export async function init(projectRoot, options = {}) {
     }
     // 8. Create .cgcignore and manage git excludes
     createCgcIgnore(projectRoot);
+    // .mcp.json contains auth tokens — always gitignore it regardless of mode
+    ensureGitignore(projectRoot);
     if (local) {
         console.info("\n[Git Excludes]");
         writeGitInfoExclude(projectRoot);
     }
-    else {
-        ensureGitignoreMcpJson(projectRoot);
-    }
     // 9. Run on_init hooks from enabled extensions
     console.info("\n[Extension Hooks]");
     const { getEnabledExtensions } = await import("../../lib/extension-loader.js");
@@ -753,12 +758,52 @@ export async function init(projectRoot, options = {}) {
     writeConfig(projectRoot, config);
     console.info(`\n[Config]`);
     console.info(`  create: .indusk/config.json (mode: ${config.mode})`);
+    // Create initial handoff so /catchup runs full orientation on first session
+    const handoffPath = join(projectRoot, ".claude/handoff.md");
+    if (!existsSync(handoffPath) || force) {
+        const today = new Date().toISOString().split("T")[0];
+        const handoffContent = [
+            "# Handoff",
+            "",
+            `**Date:** ${today}`,
+            "**Session:** Fresh init — first session orientation needed",
+            "",
+            "## Catchup Status",
+            "- [ ] mcp-ready",
+            "- [ ] handoff",
+            "- [ ] lessons",
+            "- [ ] health",
+            "- [ ] context",
+            "- [ ] plans",
+            "- [ ] skills",
+            "- [ ] extensions",
+            "- [ ] graph",
+            "",
+            "## What Was Being Worked On",
+            "`indusk init` just set up this project. No prior session.",
+            "",
+            "## Where It Stopped",
+            "Init complete. Agent needs full orientation (lessons, context, skills, extensions, graph).",
+            "",
+            "## What's Next",
+            "1. Run `/catchup` to orient the agent (reads lessons, context, skills, extensions, graph)",
+            "2. Edit CLAUDE.md with project details",
+            "3. Start planning: `/planner your-first-feature`",
+            "",
+            "## Open Issues",
+            "None — fresh project.",
+            "",
+        ].join("\n");
+        writeFileSync(handoffPath, handoffContent);
+        console.info("\n[Handoff]");
+        console.info("  create: .claude/handoff.md (first-session orientation)");
+    }
     // Summary
     console.info("\nDone!");
     console.info("\n⚠  Restart Claude Code to load the updated MCP server and skills.");
     console.info("\nNext steps:");
     console.info("  1. Set up infrastructure (if not done): indusk infra start");
-    console.info("  2. Restart Claude Code");
+    console.info("  2. Restart Claude Code — /catchup will auto-orient the agent");
     console.info("  3. Edit CLAUDE.md with your project details");
-    console.info("  4. Start planning: /plan your-first-feature");
+    console.info("  4. Start planning: /planner your-first-feature");
 }

package/extensions/excalidraw/skill.md

@@ -41,7 +41,7 @@ That's it. No tokens, no config files, no environment variables.
 
 ## When to Create Diagrams
 
-- **During `/plan` research or brief**: sketch the proposed architecture to make it concrete
+- **During `/planner` research or brief**: sketch the proposed architecture to make it concrete
 - **During `/work` teach mode**: visualize what a phase is building before and after
 - **During debugging**: draw the request flow to identify where things break
 - **During retrospective**: before/after architecture comparison

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@infinitedusky/indusk-mcp",
-	"version": "1.9.1",
+	"version": "1.9.4",
 	"description": "InDusk development system — skills, MCP tools, and CLI for structured AI-assisted development",
 	"type": "module",
 	"files": [

package/skills/catchup.md

@@ -78,7 +78,7 @@ Call `extensions_status` to see what extensions are enabled and their capabiliti
 Call `get_skill_summaries` to load the name, description, and type of every installed skill. This returns a compact summary — you do NOT need to read each skill file individually. The full skill content loads automatically when the user invokes a slash command.
 
 Skill types:
-- **process** — workflow skills with slash commands (plan, work, verify, context, document, retrospective)
+- **process** — workflow skills with slash commands (planner, work, verify, context, document, retrospective)
 - **extension** — tool integrations (cgc, composable-env, excalidraw, etc.)
 - **domain** — technology-specific best practices (typescript, testing, etc.)
 

package/skills/{plan.md → planner.md}

@@ -1,5 +1,5 @@
 ---
-name: plan
+name: planner
 description: Create and advance plans. Every plan follows the same document lifecycle — research, brief, ADR, impl, retrospective. Knows how to write each one, what order they go in, and how to pick up where things left off.
 argument-hint: "[workflow] [plan name] — workflow: feature (default), bugfix, refactor, spike"
 ---
@@ -29,15 +29,15 @@ General-purpose research (insights useful across plans) also lives in `research/
 
 ## Workflow Types
 
-The first argument to `/plan` can optionally be a workflow type that controls which documents are created:
+The first argument to `/planner` can optionally be a workflow type that controls which documents are created:
 
 | Command | Workflow | Documents |
 |---------|----------|-----------|
-| `/plan bugfix auth-expiry` | bugfix | brief + impl only |
-| `/plan refactor extract-auth` | refactor | brief + impl (with boundary map) |
-| `/plan spike redis-options` | spike | research only |
-| `/plan feature payment-flow` | feature | full lifecycle (default) |
-| `/plan payment-flow` | feature | same — no type defaults to feature |
+| `/planner bugfix auth-expiry` | bugfix | brief + impl only |
+| `/planner refactor extract-auth` | refactor | brief + impl (with boundary map) |
+| `/planner spike redis-options` | spike | research only |
+| `/planner feature payment-flow` | feature | full lifecycle (default) |
+| `/planner payment-flow` | feature | same — no type defaults to feature |
 
 Parse the input: if the first word is `bugfix`, `refactor`, `spike`, or `feature`, use that workflow. Otherwise, default to `feature`. The remaining words become the plan name (kebab-cased).
 

package/skills/retrospective.md

@@ -21,7 +21,7 @@ The retrospective skill replaces the freeform "write a retrospective" step with
 ## When to Use
 
 - After `/work` completes all impl phases and the status is `completed`
-- When `/plan {name}` detects the impl is completed and the next step is retrospective
+- When `/planner {name}` detects the impl is completed and the next step is retrospective
 - Directly via `/retrospective {plan-name}`
 
 ## The Audit Checklist

package/skills/toolbelt.md

@@ -17,7 +17,7 @@ To see which MCP servers and extensions are active, call `extensions_status`.
 ## How the Skills Work Together
 
 ```
-/plan → creates planning docs (research, brief, ADR, impl)
+/planner → creates planning docs (research, brief, ADR, impl)
                 ↓
 /work → executes impl checklist, phase by phase
          each phase has four gates:
@@ -139,7 +139,7 @@ While executing impl items:
 
 Gates prevent skipping important work. Three enforcement levels, set via `gate_policy` in impl frontmatter or `.claude/settings.json`:
 
-| Mode | Writing the impl (`/plan`) | Executing the impl (`/work`) |
+| Mode | Writing the impl (`/planner`) | Executing the impl (`/work`) |
 |------|---------------------------|------------------------------|
 | **`strict`** | Every gate must have a real item. No `(none needed)`. | Every item must be completed. No skipping. |
 | **`ask`** (default) | Every gate must have a real item. No `(none needed)`. | Skip only with conversation proof: `(none needed — asked: "..." — user: "...")` |

package/skills/work.md

@@ -70,7 +70,7 @@ Three modes, configured via `gate_policy` in the impl frontmatter or `.claude/se
 
 | Mode | Behavior |
 |------|----------|
-| **`strict`** | No overrides at any stage. Every gate must have a real item when the impl is written (`/plan`), and every item must be completed during `/work`. No `(none needed)`, no `skip-reason:`, no conversation proof. |
+| **`strict`** | No overrides at any stage. Every gate must have a real item when the impl is written (`/planner`), and every item must be completed during `/work`. No `(none needed)`, no `skip-reason:`, no conversation proof. |
 | **`ask`** (default) | Every gate must have a real item when the impl is written. During `/work`, the agent must ask the user before skipping, and include proof of the conversation in the skip format. Hooks enforce both stages. |
 | **`auto`** | Gates can be pre-filled with `(none needed)` or `skip-reason:` at write time. During `/work`, the agent can skip without asking. Use when running autonomously. |
 
@@ -118,7 +118,7 @@ In `ask` mode, skipped gates MUST include proof that the conversation happened:
 
 The hook validates that both `asked:` and `user:` are present with non-empty quoted content. Bare `(none needed)` or `skip-reason:` without conversation proof will be **blocked by the hook**.
 
-| Mode | At write time (`/plan`) | At execution time (`/work`) |
+| Mode | At write time (`/planner`) | At execution time (`/work`) |
 |------|------------------------|---------------------------|
 | `strict` | No opt-outs — real items required | No skipping — everything completed |
 | `ask` | No opt-outs — real items required | Skip only with conversation proof |
@@ -148,7 +148,7 @@ The hook validates that both `asked:` and `user:` are present with non-empty quo
     - Update impl status to `completed`
     - Summarize what was done
     - If this plan included an ADR, confirm CLAUDE.md's Key Decisions was updated
-    - Let the user know the plan is ready for a retrospective if they want one (`/plan {name}` will pick up at the retrospective stage)
+    - Let the user know the plan is ready for a retrospective if they want one (`/planner {name}` will pick up at the retrospective stage)
 
 ## Teach Mode