Kmichels Multi Manus Planning
- 28 repo stars
- Updated January 11, 2026
- kmichels/multi-manus-planning
kmichels-multi-manus-planning is a Claude Code plugin that coordinates Manus-style planning across multiple projects and paths.
About
kmichels-multi-manus-planning is a Claude Code plugin that implements multi-project, Manus-style planning using a coordinator pattern. developers who run several repos, client projects, or parallel experiments often lose thread when one Claude session bleeds plans together; this plugin is meant to keep planning artifacts and paths scoped per project while still letting you switch context deliberately. Use it when you are scoping what to build next, breaking work into coordinated phases, or maintaining parallel roadmaps across machines. It is a process-oriented planning layer rather than a code generator, so journey scope is multi-phase: the same coordinator helps during validate when you narrow scope, during build when you sequence tasks, and early in idea when you compare project options. The repository lists one plugin and modest community traction; read the plugin’s SKILL.md for exact invoke triggers and coordinator commands before relying on it for production PM.
- Manus-style multi-project planning with a coordinator pattern for Claude Code
- Supports separate project paths and switching without cross-contaminating plans
- Cross-machine planning source keywords indicate distributed or multi-repo workflows
- Single-plugin bundle focused purely on planning orchestration
- Fits indie builders juggling more than one codebase or client repo
Kmichels Multi Manus Planning by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install kmichels-multi-manus-planning@kmichels/multi-manus-planningAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 28 |
|---|---|
| Last updated | January 11, 2026 |
| Repository | kmichels/multi-manus-planning ↗ |
What it does
Run Manus-style coordinated planning across several projects and machines so Claude Code keeps separate plans and paths without mixing context.
Who is it for?
Best when you're running multiple Claude Code projects and want Manus-like planning discipline and explicit project switching.
Skip if: Single-repo developers who only need a one-off task list inside one session.
What you get
After install, you get separated multi-project plans with coordinator-style switching so each codebase keeps its own planning thread.
- Per-project planning threads managed by a coordinator pattern
- Cleaner context when switching between repos or machines
- Structured plan artifacts aligned to each project path
By the numbers
- 1 plugin in bundle
- Repository: kmichels/multi-manus-planning
- Community listing: 23 GitHub stars (ingested metadata)
Recommended Plugins
0oastro Kawai Girl Output StyleTransform Claude's responses into kawaii anime girl style\!3
0xbigboss Claude CodeComprehensive configuration system for Claude Code51
2lab Ai Oh My ClaudeClaude Code plugin for AI-powered iterative development loops.37
45ck Claude Sdlc PluginClaude Code plugin for SDLC workflow automation with Storybook planning hub1
70 10 Claude Code Plugins70-10's Claude Code plugins
Aaronbassett Agent FoundryMy personal plugin marketplace for Claude Code4How it compares
Multi-project planning coordinator, not a deployment MCP or code-review skill.
FAQ
Who is Kmichels Multi Manus Planning for?
It is for Claude Code users managing multiple projects or machines who want coordinated, Manus-style planning without blending contexts.
When should I use Kmichels Multi Manus Planning?
Use it when you scope or sequence work across more than one project, especially before implementation sprints or when switching between client repos.
How do I add Kmichels Multi Manus Planning to my agent?
Add the kmichels/multi-manus-planning plugin to Claude Code from the marketplace or repo, then invoke it per SKILL.md when starting or switching project plans.