Kmichels Multi Manus Planning
kmichels-multi-manus-planning is a Claude Code plugin for the Build phase that coordinates Manus-style planning across multiple projects and paths.
by kmichels · github.com/kmichels/multi-manus-planning
Run Manus-style coordinated planning across several projects and machines so Claude Code keeps separate plans and paths without mixing context.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install kmichels-multi-manus-planning@kmichels/multi-manus-planningBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:kmichels/multi-manus-planning") and the paste-ready config with skillselion.get_install_config("plugin:kmichels/multi-manus-planning").
What it does
kmichels-multi-manus-planning is a Claude Code plugin that implements multi-project, Manus-style planning using a coordinator pattern. Solo builders 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.
Highlights
- 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
Why builders use it
Juggling several projects in Claude Code mixes plans and paths so you cannot trust which roadmap the agent is following.
After install, you get separated multi-project plans with coordinator-style switching so each codebase keeps its own planning thread.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 23 stars, 0 votes.
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.
Comments
Share how you use kmichels-multi-manus-planning, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.