How to Run Long, Multi-Issue Workstreams with Claude Code /goal and Git Worktrees

Member-only story

and Git Worktrees

Keep Claude Code focused across multiple issues and PRs — without scope drift, duplicate abstractions, or constant prompting. #

Our problem was not a lack of planning.

The requirements were clear, the issues were ready, and the acceptance criteria were mostly in place. We wanted to place separate workstreams in Git worktrees and let several Claude Code sessions move forward in parallel.

The difficulty appeared after the work started.

Real engineering tasks rarely look like this:

One issue → one pull request → done

A more realistic structure looks like this:

One workstream  └── several issues       └── several pull requests per issue

Consider a simple example: adding a notification center to an application.

Issue A: Build the notification data layer  ├── PR 1: Data model and migration  └── PR 2: Read and update APIsIssue B: Build the notification interface  ├── PR 3: Notification list  └── PR 4: Unread state and mark-as-read behaviorIssue C: Add notification preferences  ├── PR 5: Preferences API  └── PR 6: Settings screen

Completing this workstream requires more than generating code.