multi-manus-planning

Multi-Manus Planning

Multi-project Manus-style planning with coordinator pattern for Claude Code.

A Claude Code skill that extends the planning-with-files pattern with support for multiple projects, separate planning/source paths, and cross-machine sync via git.

What's Different?

Feature	planning-with-files	multi-manus-planning
Projects	Single (CWD)	Multiple via coordinator
Planning location	CWD only	Configurable (e.g., Obsidian vault)
Source path	Same as planning	Separate (code can live elsewhere)
Cross-machine	Manual	SessionStart hook with git sync
Project switching	N/A	Natural language ("switch to X")
Session isolation	N/A	Session-scoped (v1.4.1) - no conflicts

The Coordinator Pattern

Instead of planning files in your working directory, use a .planning/index.md coordinator:

~/scripts/                          # Your CWD
├── .planning/
│   ├── index.md                    # Coordinator (active project, registry)
│   └── projects/
│       ├── project-a/
│       │   ├── task_plan.md
│       │   ├── findings.md
│       │   └── progress.md
│       └── project-b/
│           └── ...

Or store planning files anywhere (Obsidian, Dropbox, etc.) with the coordinator pointing to them.

Coordinator Format

# Planning Coordinator

active: project-a
default_path: ~/Planning

## Projects

| Name      | Planning Path                 | Source Path      | Description  |
| --------- | ----------------------------- | ---------------- | ------------ |
| project-a | {default}/project-a           | ~/code/project-a | Main project |
| project-b | ~/Obsidian/Planning/project-b | ~/code/project-b | Side project |

Installation

Prerequisites

• Claude Code CLI installed
• Git configured with GitHub access

Per-Machine Installation (Required)

Install on each machine where you want to use multi-manus planning:

# Step 1: Add the marketplace
claude plugin marketplace add kmichels/multi-manus-planning

# Step 2: Install the plugin
claude plugin install multi-manus-planning@multi-manus-planning

# Step 3: Copy the command file (enables /multi-manus-planning slash command)
cp ~/.claude/plugins/cache/multi-manus-planning/multi-manus-planning/*/commands/multi-manus-planning.md ~/.claude/commands/

# Step 4: Restart your Claude session
# Exit and start a new session for the plugin to load

What gets installed:

• ✅ The multi-manus-planning skill (available via Skill tool)
• ✅ The /multi-manus-planning command (after Step 3)
• ❌ NO automatic hooks
• ❌ NO SessionStart configuration

Note: Plugins provide skills (invoked via Skill tool), not commands (invoked via /slash). Step 3 copies the command wrapper so you can use /multi-manus-planning.

Multi-machine setup: Repeat steps 1-4 on each machine. The plugin installs locally and does not sync between machines.

Optional: SessionStart Hook (Separate Setup)

To automatically sync planning files when starting a session:

Note: The hook walks up the directory tree to find .planning/, similar to how git finds .git/. This means it works from any subdirectory of your workspace.

1. Copy the hook:

   cp ~/.claude/skills/multi-manus-planning/scripts/planning-sync.sh ~/.claude/hooks/
   chmod +x ~/.claude/hooks/planning-sync.sh
   

2. Add to ~/.claude/settings.json:

   {
     "hooks": {
       "SessionStart": [
         {
           "hooks": [
             {
               "type": "command",
               "command": "~/.claude/hooks/planning-sync.sh"
             }
           ]
         }
       ]
     }
   }
   

Optional: SessionEnd Hook (Session Cleanup)

To automatically clean up session-local override files when ending a session:

1. Copy the hook:

   cp ~/.claude/skills/multi-manus-planning/scripts/planning-cleanup.sh ~/.claude/hooks/
   chmod +x ~/.claude/hooks/planning-cleanup.sh
   

2. Add to ~/.claude/settings.json:

   {
     "hooks": {
       "SessionEnd": [
         {
           "hooks": [
             {
               "type": "command",
               "command": "~/.claude/hooks/planning-cleanup.sh"
             }
           ]
         }
       ]
     }
   }