Delegate Feature Branches
UTILITY SKILL. INVOKES: multi-agent workers, implement-in-logical-commits, draft-pr-until-green.
USE FOR:
Use $delegate-feature-branches ...- Assigning each planned worktree to a sub-agent.
- Parallel implementation across already planned branches.
- Existing plan includes branch, worktree, goal, and validation.
DO NOT USE FOR:
- Planning or splitting branches; use
plan-feature-branches.
- Creating worktrees; use
setup-feature-worktrees.
- Single-branch work; use
implement-in-logical-commits.
- Monitoring only; use
monitor, monitor-ci, or draft-pr-until-green.
Workflow
- Keep one branch with the main agent unless told otherwise; assign one worker per extra branch.
- Give each worker: worktree, branch, goal, scope, validation, and completion contract.
- Tell workers not to revert others' work and to adapt to concurrent changes.
- Spawn workers in parallel, then keep the local branch moving.
- Collect PR links, CI state, commits, validation, and blockers.
Examples
You own branch <branch> in <worktree>.
Goal: <goal>
Scope: <files>
Validation: <commands>
Use $implement-in-logical-commits, then $draft-pr-until-green. Return PR link, CI state, commits, validation, blockers.
Troubleshooting
- Push/auth/PR failure: capture the exact blocker; do not publish that branch.
- Branch conflict: stop the affected worker; report files and branches.
- Not independently reviewable: do not publish; report reason and regrouping.
Output
Return short Markdown with branch-owner map, worktrees, PR/CI state, validation, commits, and blockers.
1---2name: delegate-feature-branches3description: Assign planned feature branches with existing worktrees to Codex sub-agents for parallel implementation and draft PR publication. Use when a branch plan and worktree map already exist and the user asks for delegation, workers, sub-agents, or parallel Codex execution. Do not use for planning, worktree setup, single-branch work, or monitoring-only requests.4---56# Delegate Feature Branches78**UTILITY SKILL. INVOKES:** multi-agent workers, `implement-in-logical-commits`, `draft-pr-until-green`.910## USE FOR:1112- `Use $delegate-feature-branches ...`13- Assigning each planned worktree to a sub-agent.14- Parallel implementation across already planned branches.15- Existing plan includes branch, worktree, goal, and validation.1617## DO NOT USE FOR:1819- Planning or splitting branches; use `plan-feature-branches`.20- Creating worktrees; use `setup-feature-worktrees`.21- Single-branch work; use `implement-in-logical-commits`.22- Monitoring only; use `monitor`, `monitor-ci`, or `draft-pr-until-green`.2324## Workflow25261. Keep one branch with the main agent unless told otherwise; assign one worker per extra branch.272. Give each worker: worktree, branch, goal, scope, validation, and completion contract.283. Tell workers not to revert others' work and to adapt to concurrent changes.294. Spawn workers in parallel, then keep the local branch moving.305. Collect PR links, CI state, commits, validation, and blockers.3132## Examples3334```text35You own branch <branch> in <worktree>.36Goal: <goal>37Scope: <files>38Validation: <commands>39Use $implement-in-logical-commits, then $draft-pr-until-green. Return PR link, CI state, commits, validation, blockers.40```4142## Troubleshooting4344- Push/auth/PR failure: capture the exact blocker; do not publish that branch.45- Branch conflict: stop the affected worker; report files and branches.46- Not independently reviewable: do not publish; report reason and regrouping.4748## Output4950Return short Markdown with branch-owner map, worktrees, PR/CI state, validation, commits, and blockers.
willakins