planmode 0.2.0 → 0.2.2

package/README.md

@@ -30,6 +30,97 @@ planmode run rest-api-generator --resource users --framework express
 planmode list
 ```
 
+## Use with Claude Code (MCP)
+
+Planmode includes an MCP server that lets Claude Code search, install, preview, and manage packages directly from your conversations — no need to leave the chat.
+
+### Prerequisites
+
+- [Claude Code CLI](https://docs.anthropic.com/en/docs/claude-code) installed and working (`claude` command available)
+- Planmode installed globally: `npm install -g planmode`
+
+### Setup
+
+```bash
+# Automatic — registers the MCP server with Claude Code
+planmode mcp setup
+```
+
+This runs `claude mcp add --transport stdio planmode -- planmode-mcp` under the hood. You only need to do this once.
+
+### Manual setup
+
+If you prefer to register manually, or if the automatic setup doesn't work:
+
+```bash
+claude mcp add --transport stdio planmode -- planmode-mcp
+```
+
+Or add it directly to your Claude Code MCP config (`~/.claude/settings.json`):
+
+```json
+{
+  "mcpServers": {
+    "planmode": {
+      "command": "planmode-mcp",
+      "transport": "stdio"
+    }
+  }
+}
+```
+
+### Verify it works
+
+After setup, start a Claude Code session and ask:
+
+> "Search planmode for a Next.js starter plan"
+
+Claude should call the `planmode_search` tool and return results from the registry.
+
+### Available MCP tools
+
+Once connected, Claude has access to these tools:
+
+| Tool | What it does |
+|------|-------------|
+| `planmode_search` | Search the registry for packages |
+| `planmode_info` | Get detailed package metadata |
+| `planmode_preview` | Read a package's content before installing |
+| `planmode_install` | Install a package into the current project |
+| `planmode_uninstall` | Remove an installed package |
+| `planmode_list` | List all installed packages |
+| `planmode_read` | Read the content of an installed package |
+| `planmode_update` | Update installed packages |
+| `planmode_init` | Scaffold a new package |
+| `planmode_publish` | Publish a package to the registry |
+| `planmode_validate` | Validate a planmode.yaml manifest |
+| `planmode_run` | Render a templated prompt with variables |
+| `planmode_doctor` | Run a health check on installed packages |
+| `planmode_test` | Validate a package before publishing |
+| `planmode_record_start` | Start recording git commits for plan generation |
+| `planmode_record_stop` | Stop recording and generate a plan |
+| `planmode_snapshot` | Generate a plan from existing project setup |
+
+Installed packages are also exposed as MCP resources that Claude can browse automatically.
+
+### Example prompts
+
+Ask Claude things like:
+
+- "Search planmode for a Next.js starter plan"
+- "Show me what the typescript-strict rule contains"
+- "Install the docker-compose-stack plan"
+- "Preview the rest-api-generator prompt before installing"
+- "Run a health check on my planmode packages"
+- "Create a new planmode rule called my-coding-standards"
+- "Record my work and generate a plan from my commits"
+
+### Remove
+
+```bash
+planmode mcp remove
+```
+
 ## Package types
 
 | Type | What it is | Where it lives | Lifecycle |
@@ -52,6 +143,33 @@ planmode list
 | `planmode init` | Create a new package |
 | `planmode publish` | Publish to the registry |
 | `planmode login` | Configure GitHub auth |
+| `planmode mcp setup\|remove` | Register/remove MCP server with Claude Code |
+| `planmode doctor` | Check project health and file integrity |
+| `planmode test` | Validate a package before publishing |
+| `planmode record start\|stop` | Generate a plan from git commits |
+| `planmode snapshot` | Generate a plan from existing project setup |
+
+## Create plans from your work
+
+### Record mode
+
+Start a recording, work normally, then generate a plan from your commits:
+
+```bash
+planmode record start
+# ... do your work, make commits ...
+planmode record stop --name my-setup-plan --author myusername
+```
+
+### Snapshot mode
+
+Analyze an existing project and generate a plan that recreates the setup:
+
+```bash
+planmode snapshot --name nextjs-prisma-setup --author myusername
+```
+
+This reads `package.json`, detects config files (TypeScript, ESLint, Tailwind, Prisma, Docker, etc.), captures the directory structure, and creates a step-by-step plan.
 
 ## How it works
 

package/dist/index.js

@@ -2289,7 +2289,7 @@ var snapshotCommand = new Command15("snapshot").description("Analyze the current
 
 // src/index.ts
 var program = new Command16();
-program.name("planmode").description("The open source package manager for AI plans, rules, and prompts.").version("0.2.0");
+program.name("planmode").description("The open source package manager for AI plans, rules, and prompts.").version("0.2.2");
 program.addCommand(installCommand);
 program.addCommand(uninstallCommand);
 program.addCommand(searchCommand);

package/dist/mcp.js

@@ -1740,7 +1740,7 @@ function errorResult(prefix, err) {
 }
 var server = new McpServer({
   name: "planmode",
-  version: "0.2.0"
+  version: "0.2.2"
 });
 server.registerTool(
   "planmode_search",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "planmode",
-  "version": "0.2.0",
+  "version": "0.2.2",
   "description": "The open source package manager for AI plans, rules, and prompts.",
   "type": "module",
   "bin": {

package/src/index.ts

@@ -20,7 +20,7 @@ const program = new Command();
 program
   .name("planmode")
   .description("The open source package manager for AI plans, rules, and prompts.")
-  .version("0.2.0");
+  .version("0.2.2");
 
 program.addCommand(installCommand);
 program.addCommand(uninstallCommand);

package/src/mcp.ts

@@ -83,7 +83,7 @@ function errorResult(prefix: string, err: Error): ReturnType<typeof textResult>
 
 const server = new McpServer({
   name: "planmode",
-  version: "0.2.0",
+  version: "0.2.2",
 });
 
 // ── Tools ──