Using OpenGSD in teams, shared plans vs worktrees

[PaulSainsbury]

Hey,

We have a small team using GSD. We don’t pre-plan a lot of our work so we struggle to find a way to manage the roadmap and planning files. Things move fairly fluidly so coordinating a combined roadmap that doesn’t overlap or get changed as we go is quite hard.

We were given guidance to keep our plans out of git, so we ignore .planning, but include .planning/codebase

Our hassle is that we then run into a problem where worktree sub-agents don’t always get the latest plan update if they work in parallel because plan changes aren’t stored in git.

Has anyone had experience in working in teams with GSD and what to keep shared vs separate?

[ericknyoto]

​We are a development team of 6 people. Our workflow is as follows: we commit to the repository's codebase, graph, intel, and config.json folders. The reason for this is so that everyone can use the codebase files immediately without each person having to execute the code map base. The lead developer is the one who decides when the codebase should be updated. The config.json is committed to ensure that all developers use the same configuration (e.g., balanced profile, no commit, research true, etc.). All files inside the .planning folder resulting from a new project, discuss plan, execute, and milestone must not be committed. Instead, they are uploaded manually to Google Drive for documentation purposes.