A few months ago I was juggling 3 features across different branches, stashing changes constantly, and every time I switched context my agent had no idea what was going on.
The problem I had: I'd start a feature, spend 2 hours with Claude working through requirements and architecture. Great session. Next day, different feature. Come back to the first one a week later — all those decisions exist only in a chat transcript I'll never reread. Meanwhile my PM is asking about status in Slack and my QA engineer doesn't know what to test until I write a doc nobody wants to write.
What I do now:
- Create a workspace → gets its own git worktree, VS Code, terminals. Completely isolated from my other work.
- As I work with my agent, we write artifacts — requirements, design, spec, test plan — as structured YAML that lives in
.tracigo/in the repo. The key part: these have changelogs that capture why decisions were made, not just what. - Every agent session auto-loads these artifacts. I don't configure anything — the tool writes instruction files in each agent's native format (
.claude/rules/,.cursor/rules/,Agentsmd, etc.) - My PM edits requirements directly. My QA writes test cases against the spec. When requirements change, the changelog flags which downstream artifacts need updating — before I write code that'll be thrown out.
The tool is called Tracigo if anyone wants to check it out. Happy to answer questions about the workflow or share the YAML artifact structure.
Anyone else running multiple agents in parallel? Curious to know what you do..