planmode

The open source package manager for AI plans, rules, and prompts.

Website: planmode.org Repository: github.com/kaihannonen/planmode.org

Install

npm install -g planmode

Quick start

# Search for packages
planmode search nextjs

# Install a plan (adds to plans/ and updates CLAUDE.md)
planmode install nextjs-tailwind-starter

# Install a rule (goes to .claude/rules/)
planmode install typescript-strict

# Run a templated prompt
planmode run rest-api-generator --resource users --framework express

# See what's installed
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 installed and working (claude command available)
• Planmode installed globally: npm install -g planmode

Setup

# 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:

claude mcp add --transport stdio planmode -- planmode-mcp

Or add it directly to your Claude Code MCP config (~/.claude/settings.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

planmode mcp remove

Package types

| Type | What it is | Where it lives | Lifecycle | |------|-----------|---------------|-----------| | Plan | Multi-step implementation guide | plans/*.md | Active during task | | Rule | Always-on constraint | .claude/rules/*.md | Permanent | | Prompt | Fire-once instruction | prompts/*.md | Single use |

Commands

| Command | Description | |---------|-------------| | planmode install <pkg> | Install a package | | planmode uninstall <pkg> | Remove a package | | planmode search <query> | Search the registry | | planmode run <prompt> | Run a templated prompt | | planmode list | List installed packages | | planmode info <pkg> | Show package details | | planmode update [pkg] | Update packages | | 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:

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:

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

Planmode leverages Claude Code's native @import system. When you install a plan:

1. The CLI fetches .md files from the registry
2. Drops them into the correct directory (plans/, .claude/rules/, or prompts/)
3. Adds @plans/<name>.md to your CLAUDE.md

Claude Code is already the runtime. Planmode handles discovery, versioning, and distribution.

Browse packages

Visit planmode.org/packages to discover plans, rules, and prompts.

License

MIT