dispatching-parallel-agents
Dispatching Parallel Agents
Adapted from obra/superpowers — MIT. Adapted for the NodeJS-Starter-V1 monorepo (frontend/backend/database component separation).
Overview
When you have multiple unrelated failures across different components or files, investigating them sequentially wastes time. Each independent investigation can happen in parallel.
Core principle: Dispatch one agent per independent problem domain. Let them work concurrently. Integrate results after all complete.
When to Use
Use when:
- 3+ test files failing with different root causes
- Multiple independent subsystems broken (e.g., React component + FastAPI endpoint + DB model)
- Each problem can be understood without context from the others
- No shared state between investigations (agents won't edit the same files)
More from cleanexpo/unite-hub
tdd
Use when implementing any feature or bug fix. Hard gate — no production code without a failing test first. Applies to vitest (apps/web/) and pytest (apps/backend/). Triggers on "implement", "add feature", "fix bug", "new component", "new endpoint", or any code-writing task.
1idea-to-production
Plain-English pipeline from idea to production — routes user requests to the right phase and agent
1oauth-flow
OAuth 2.0 and OIDC integration with PKCE, Supabase Auth providers, and redirect URI validation
1health-check
>-
1csv-processor
>-
1vector-search
>-
1