dense-multi-agent-worktree-delivery
Installation
SKILL.md
Dense Multi-Agent Worktree Delivery
Core Rule
Use this workflow when the user wants substantial project advancement through many coordinated agents, isolated worktrees, scoreable lanes, stacked PRs, fast validation feedback, and external status sinks.
Preserve this as a standalone operating model. Generic delivery skills may support it, but must not collapse it into a project router, a three-agent fallback, or a vague "parallel work" note. Dense means controlled throughput with evidence, not uncontrolled WIP.
Mode Selector
Choose exactly one mode before acting:
- Batch mode — default for new dense product progress. Use adaptive workgroups, scoreable lanes, stacked PRs, and status sinks.
- Single-slice mode — use when the user names one issue, PR, bug, CI failure, or hotfix. Do not add swarm overhead unless adjacent low-overlap work can safely continue.
- Closeout/audit mode — use when PRs, CI, dirty worktrees, controller state, Slack/Linear state, or sibling branch rebases are already in flight.
Closeout/audit debt must be owned before new implementation, but it is not a global stop sign. Hermes may keep low-overlap development moving when live PR/CI/review capacity exists and each lane has an explicit closeout owner and next action.