rugged-gemini: Skill for Gemini CLI

Parallel Dispatch: Dependency Graph

Build a DAG from scope cards. Topological sort into levels. Dispatch all nodes at the same level in parallel.

When to Invoke

• After scope cards are produced by parallel-dispatch-decomposition
• Before dispatching any agents within a primitive
• When re-planning after a sub-task failure

Graph Construction

Nodes

Each scope card becomes a node in the DAG:

• ID: @<agent-type>[<scope>]
• Type: write (modifies files) or read (read-only analysis)
• Phase: The primitive this node belongs to (SCOUT, DESIGN, BUILD, REVIEW, etc.)

Edges

Each "Blocked By" or "Hard Dependencies" entry in a scope card becomes a directed edge:

• Edge direction: dependency → dependent (producer → consumer)
• Only hard dependencies create edges. Soft dependencies are advisory.

Construction Algorithm

1. Create a node for each scope card
2. For each node, read its "Hard Dependencies" and "Blocked By" fields
3. Create an edge from each dependency to this node
4. Validate: every referenced dependency exists as a node (no dangling references)

Topological Sort

Group nodes into levels based on their depth in the dependency graph:

• Level 0: Nodes with zero incoming edges (no dependencies). These execute first.
• Level N: Nodes whose dependencies are all in levels 0 through N-1.

All nodes at the same level are independent of each other and can be dispatched in parallel.

Sort Algorithm

1. Initialize in-degree count for each node
2. Enqueue all nodes with in-degree = 0 → Level 0
3. For each node in current level:
   a. Remove its outgoing edges (decrement in-degree of dependents)
   b. If any dependent's in-degree reaches 0 → add to next level
4. Repeat until all nodes assigned
5. If unassigned nodes remain → cycle detected → ABORT

DAG Output Format

Present the execution plan as a leveled dispatch table:

## Execution DAG

### Level 0 (no dependencies — dispatch in parallel)
| Node | Agent | Scope | Type | Deliverables |
|------|-------|-------|------|-------------|
| 1 | @scout | [auth] | read | Auth pattern research |
| 2 | @scout | [tasks] | read | Task engine research |
| 3 | @scout | [infra] | read | Infrastructure research |

### Level 1 (depends on Level 0 — dispatch after Level 0 completes)
| Node | Agent | Scope | Type | Blocked By | Deliverables |
|------|-------|-------|------|-----------|-------------|
| 4 | @architect | [api-contracts] | write | 1, 2 | API contract definitions |
| 5 | @architect | [data-model] | write | 1, 2, 3 | Data model design |

### Level 2 (depends on Level 1 — dispatch after Level 1 completes)
| Node | Agent | Scope | Type | Blocked By | Deliverables |
|------|-------|-------|------|-----------|-------------|
| 6 | @backend-engineer | [auth] | write | 4 | Auth feature implementation |
| 7 | @backend-engineer | [tasks] | write | 4, 5 | Task feature implementation |
| 8 | @frontend-engineer | [auth-ui] | write | 4 | Auth UI components |
| 9 | @frontend-engineer | [task-ui] | write | 4, 5 | Task UI components |

### Level 3 (depends on Level 2 — dispatch after Level 2 completes + merges)
| Node | Agent | Scope | Type | Blocked By | Deliverables |
|------|-------|-------|------|-----------|-------------|
| 10 | @backend-engineer | [integration] | write | 6, 7 | Router wiring, app entry |
| 11 | @frontend-engineer | [integration] | write | 8, 9 | Route registration, app shell |