fanout

Featured

Run independent subtasks in parallel — one git worktree and one implementation sub-agent per task, each opening its own PR — then cross-review every PR. polly never merges; the human does.

Code & Development 7,797 stars 1139 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# fanout — safe parallel execution Use ONLY for subtasks that are parallel-safe (no shared files, no ordering dependency). ## Procedure 1. Per task, create an isolated worktree: `sys_os_shell("git worktree add .worktrees/<task_id> -b polly/<task_id>")`. Record the worktree path + branch in the registry (`.polly/registry.json`). 2. Dispatch one implementation sub-agent per task, scoped to its worktree: `sys_session_send(agent="claude_code"|"codex"|"opencode"|"cursor"|"hermes", title="<task_slug>", args={purpose: "implement", input: "<task + acceptance contract + worktree path>"})`. Use a short task-based title such as `auth-refactor` or `fix-sse-error`, never the raw vendor name. State the scope and that it must work only inside `.worktrees/<task_id>`. The worker drives the task to green and opens its OWN PR for the branch. Every commit the worker authors must end with a blank line followed by the exact co-sign trailer as its final line — `Co-authored-by: omnigent <noreply@omnigent.ai>`. Record each handle's `conversation_id` in the registry. Emit the worktree + `sys_session_send` tool calls in THIS turn — never end a turn having only said you will dispatch; the dispatch calls and their announcement go in the same turn. Dispatch the whole parallel-safe set, THEN (and only then) END YOUR TURN. Do not poll. 3. Each sub-agent runs autonomously and notifies you through the inbox when it finishes. Collect its structured result wi...

Details

Author
omnigent-ai
Repository
omnigent-ai/omnigent
Created
1 months ago
Last Updated
today
Language
Python
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category