CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-05-02 03:35:09 +02:00
Code Issues Packages Projects Releases Wiki Activity

chore: add worktree parallel debug agents to TODOS.md (P2)

Browse Source 
When /qa hits multiple stubborn bugs, parallel debug agents in
isolated git worktrees could investigate simultaneously. Deferred
from the sequential debug escalation PR as a follow-up.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-03-18 11:13:23 -07:00
parent 5044c664c6
commit caea5058d9
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TODOS.md
+14
View File
@@ -422,6 +422,20 @@
**Priority:** P2
**Depends on:** `garrytan/team-supabase-store` branch landing on main
## Debug
### Worktree-based parallel debug sub-agents
**What:** When /qa hits multiple stubborn bugs, spawn parallel debug agents each in their own git worktree (`isolation: "worktree"` on the Agent call). They investigate simultaneously while /qa continues other work. Results cherry-picked back.
**Why:** Sequential debug investigations add ~2-5 min per bug. With 3-4 hard bugs, that's 10-20 min of sequential waiting. Parallel worktree agents could investigate all simultaneously, with zero working-tree conflicts.
**Context:** v1 ships sequential (debug-subagent-escalation PR). The Agent tool supports `isolation: "worktree"` which creates a temporary git worktree — each agent gets its own copy of the repo. Especially powerful in plan mode where /qa might find multiple hard bugs across different subsystems.
**Effort:** M (human: ~1 week / CC: ~30min)
**Priority:** P2
**Depends on:** Sequential debug escalation (debug-subagent-escalation PR)
## Design Review
### /plan-design-review + /qa-design-review + /design-consultation — SHIPPED