Parallel Sessions #2621
Replies: 1 comment 1 reply
|
@CarlosChiari — GSD already has pieces that overlap with what you described: The auto-merge part ("append the new version to the original") is risky as a default — STATE.md conflicts often signal real divergence (different active milestones, different progress, different decisions) and silently concatenating can double-count progress or revive rejected plans. The safer primitive is conflict-aware reconciliation with explicit precedence rules, not append-both. If you want to push this further, open an Enhancement issue with: (1) the specific workflow that fails today, (2) what files conflict in practice and how, (3) proposed reconciliation rules per file type (STATE.md, ROADMAP.md, phase files), (4) alternatives considered (e.g., workstreams as-is, manual rebase with |
Uh oh!
There was an error while loading. Please reload this page.
I wrote a Skill that makes Claude plan waves with multiple sessions to work many phases at the same time, in parallel, verifying overlaps and possible conflicts. When the sessions end, and we fetch origin and rebase, STATES.md and maybe other files have conflicts. I ask Claude to just append the new version to the original version and the conflict ends. Could be nice if GSD includes the skill to prepare parallel sessions and add a command to fetch and rebase them in order or whatever.
All reactions