mirror of
https://github.com/OthmanAdi/planning-with-files.git
synced 2026-04-26 00:16:01 +03:00
[GH-ISSUE #13] Fork with multi-project support - potential upstream interest? #9
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/planning-with-files#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kmichels on GitHub (Jan 9, 2026).
Original GitHub issue: https://github.com/OthmanAdi/planning-with-files/issues/13
Hey! I built a fork called multi-manus-planning that adds:
.planning/index.mdcoordinatorWanted to let you know and say thanks for the original - it is a great foundation. Happy to discuss if any of these features would fit upstream.
@OthmanAdi commented on GitHub (Jan 9, 2026):
Hey @kmichels! Thanks for sharing this — really cool to see where you took it.
The multi-project coordinator is clever. I've been using this primarily for single-project workflows, but I can see how juggling multiple repos with separate planning locations would be useful, especially the Obsidian setup.
A few questions to understand your use case better:
Which feature has been most valuable in practice? The multi-project switching, the separate paths, or the SessionStart sync?
The SessionStart hook for git sync — this one feels like it could be broadly useful even for single-project users. How's it working for you across machines?
The
.planning/index.mdcoordinator — does Claude pick this up automatically, or do you have to prompt it to check the coordinator first?I'll add a link to your fork in the README under a "Community Forks" section so others with similar needs can find it.
Thanks again for building on this and for the kind words. Let's keep the conversation going — always interested in how people are adapting the pattern.
@kmichels commented on GitHub (Jan 9, 2026):
Thanks for the thoughtful questions - happy to share what's working.
Most valuable feature: Honestly, the separate planning/source paths. I keep my planning files in an Obsidian vault (iCloud-synced across machines) while the actual code lives in various repos in local storage (still git synced though). This means I can browse and edit task plans in Obsidian's UI when I'm not in a Claude session, and they're still there when I come back. The multi-project switching is convenient but I'm still early in using it heavily.
SessionStart git sync: Works well for pulling the latest planning state when I switch machines. One thing I discovered today though: I originally had ~/.claude itself symlinked to iCloud for cross-machine sync, and that caused real-time sync conflicts. Moved to a cleaner approach: local ~/.claude per machine (install plugins independently on each), and only sync the planning files via git. The hook handles the planning file sync, and the rest is machine-local.
Coordinator pickup: Not automatic: you invoke the skill (either via slash command or Skill tool), and the first thing it does is check for .planning/index.md. If found, it reads the active: field and resolves the project's planning path. The SessionStart hook displays "Planning context: [project-name]" so you know where you are, but Claude doesn't automatically load the planning files until you invoke the skill or start working on something.
One thing worth noting: I discovered today that Claude Code plugins provide skills (invoked via the Skill tool), not commands (invoked via /slash). So I had to add a command wrapper file that users copy to ~/.claude/commands/ to enable the /multi-manus-planning slash command. Might be worth documenting for others building plugins.
Appreciate you linking the fork: let me know if any of this sparks ideas for the original. The coordinator pattern could potentially be upstreamed as an optional feature.