antigravity-brain-bridge: Skill for Claude Code

Parallel Task Delegation

When working on complex tasks that involve multiple independent parts, you can dramatically speed up execution by delegating independent sub-tasks to child conversations using the Brain Bridge MCP tools.

When to Delegate

✅ DELEGATE when:

• The current task has 2+ independent sub-tasks that don't depend on each other's output
• A sub-task is self-contained (has clear input, clear expected output)
• A sub-task would take many steps to complete (e.g., writing tests, refactoring a module, code analysis)
• You're working on multiple files/modules that don't share state

❌ DON'T DELEGATE when:

• Sub-tasks are tightly coupled (Task B needs Task A's output)
• The task is simple enough to complete in a few steps
• The task requires extensive back-and-forth with the user
• The task modifies the same files (would cause merge conflicts)

Workflow: Recursive Decompose + Result Merge

Phase 1 — Analyze & Decompose

Before starting work, analyze the task and identify parallelizable parts:

User: "Add authentication to the API, write tests, and update the docs"

Think:
  - Task A: Implement auth middleware → depends on nothing
  - Task B: Write auth tests → depends on Task A's interface, but can stub it
  - Task C: Update docs → independent
  
  → Task A: do myself (core work, needs user interaction)
  → Task B: delegate (self-contained, clear spec)
  → Task C: delegate (independent)

Phase 2 — Delegate Sub-Tasks

Use the delegate_task MCP tool with clear, specific instructions:

delegate_task(
  task: "Write comprehensive tests for the auth middleware in /src/auth/. 
         Test files should go in /src/auth/__tests__/. 
         Cover: login, logout, token refresh, invalid tokens, expired tokens.
         Use the existing test framework (jest) and patterns from /src/users/__tests__/.",
  cwd: "/path/to/project"
)

Tips for good delegation:

• Be specific about what to do and where
• Mention the tech stack and existing patterns to follow
• Specify the output location (where to write files)
• Include context the child conversation needs (the child starts with zero context)