rlaope/oh-my-hermes / skills/ulw-work
ulw-work
Verified[omh] Accepted plan awaiting implementation: split it into disjoint parallel lanes with per-lane acceptance criteria, verification commands, and owners; prevents two lanes editing the same file. Aliases: ulw. Use when the user says: ultrawork, parallel work, parallel implementation, parallel then integrate, high throughput, coding team, coordinated workers, finish until done.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 26.5 KB |
| references/campaign-orchestrator.md | markdown | 10.1 KB |
| references/dependency-topology.md | markdown | 4.8 KB |
| references/execution-rulings.md | markdown | 8.5 KB |
| references/file-ownership-manifest.md | markdown | 5.0 KB |
| references/kanban-lane.md | markdown | 13.2 KB |
| references/native-delegation.md | markdown | 5.3 KB |
| references/tdd-red-green.md | markdown | 7.0 KB |
| references/team-lane.md | markdown | 5.7 KB |
references/team-lane.md
View on GitHub# Checked Team Lane
Load this reference when an accepted `ultrawork` plan splits into in-session `delegate_task` lanes and each lane must count as done only when its own check passes. `omh_team` holds the team: it hands back `delegate_task` entries, learns from the host when each helper starts and returns, runs each lane's check command itself in this session's workspace, and sends a failing lane back for a fix. A helper's summary is never how a lane is accepted.
## Before `team_start`
- Every lane has one `verification_command`, written in the lane's `omh_todo` item as ``check: `<command>` `` before the plan is accepted. Only that field binds, and only to the exact text between the backticks: a command mentioned in prose or a prefix of one is refused as `command_not_in_accepted_plan`.
- The plan is this session's own `omh_todo` plan with `plan_stage=accepted`. Call `team_start` once without `plan_ref`: it is refused as `plan_ref_mismatch`, starts nothing, asks the person nothing, and carries the accepted plan's reference. Repeat the same call with that `plan_ref`.
- A check is one plain test command such as `python -m pytest`, `npm test` or `make test`. Refused anywhere in argv: a shell or `env`, inline program text (`python -c`, `node -e`), git options or verbs that change the checkout or a remote, a forge CLI, privilege elevation, network tools, package install or publish, and `rm`/`mv`/`chmod`. Hermes' own command floor and the person's `approvals.deny` rules also apply; Hermes' dangerous-pattern check does not, and the person's approval of the exact list stands in for it.
- `team_start` asks the person to approve the exact command list. Where nobody can answer, and in a scheduled run, it is refused; report that instead of retrying. Under `--yolo` or `approvals.mode: off` Hermes approves without asking, so say which commands were frozen.
## The Loop
1. `team_start` with `team_id`, `plan_ref`, and one unit per lane (`unit_id`, `title`, `depends_on`, `verification_command`). `max_repair_attempts` defaults to 2 and is capped at 3.
2. Dispatch the returned `delegate_task` entries unchanged in one call. Each `goal` ends with the attempt key OMH reserved; you may add to `context`, never edit `goal`.
3. When the helpers return, call `team_reconcile`. While any team helper is still out it checks nothing and says so (`delegations_in_flight`). While a returned helper's work is on a branch this workspace has not merged, it is refused as `helper_branch_unmerged`, checks nothing, and names each such branch in `unmerged`. It runs at most two checks per call; `checks_pending` means call it again.
4. Relay the result's `say` line. Dispatch any new entries it returns: fix-ups for lanes whose check failed, and lanes whose parents have all passed.
5. Repeat from 3 until `team_state` is `done` or `blocked`. The one other stop is a `helper_branch_unmerged` you cannot clear, because a branch does not merge or its work must not land: report that part as blocked with its branch named, and stop.
`team_status` reports each lane's state, tries used against the maximum, its last check (`command`, `exit_code`, `observed_at`), and this conversation's cost including helpers.
## What Counts
- A lane is accepted only on an exit code OMH observed. An accepted lane carries `evidence: {kind: team_check, ref: <team_id>/<unit_id>/attempt-<n>/check}`; cite that when closing the matching `omh_todo` item.
- A check that could not run cleanly (timeout, command not found, killed by a signal, workspace missing or not a git checkout, files changed while it ran, git could not read the helper's branch) spends no try; three in a row block the lane.
- After Hermes restarts, `team_reconcile` is refused until `team_start` is called again with the same parts and the person approves again; every earlier pass is then checked once more.
- A failing check with tries left returns a fix-up entry carrying only `{command, exit_code}`; the helper reruns the command itself to see the output.
- Out of tries, the lane is `blocked` with `repair_budget_exhausted` and its last check. Report that lane and stop; do not start a new team to route around it.
## Limits to State
- Helpers share one workspace by default. A check is attributed to its lane, but another lane's edits are in the same tree; checks wait until every team helper is back to narrow this, not remove it.
- With Hermes' `delegation.worktree_isolation` on, a helper works in a git worktree of its own and its edits land on its own branch, not in this workspace. A check run here then tests a tree without that lane's work, and a pass would accept a lane nobody checked. Once every helper is back, commit what each left uncommitted in its worktree, then merge each returned helper's branch into this workspace before `team_reconcile`; `references/native-delegation.md` says how to find the branches. OMH never merges: until then `team_reconcile` is refused as `helper_branch_unmerged` with the branch named, `state: commits_not_merged` or `state: uncommitted_changes`. The helper's worktree (`.worktrees/subagent-<id>`) is found by its path even when the helper left its branch, and a helper counts as merged once the branch's last commit and the worktree's HEAD are both in this workspace's history, so after a squash or rebase merge remove the worktree and delete the branch; once both are gone nothing is looked for. Untracked files left in a merged helper's worktree also refuse: remove them, or the worktree.
- A check runs code the helpers wrote, as the person's own user account with the real home folder.
- Parallel helpers in one call share one model route; a lane that needs a different model is dispatched in its own call after `omh_delegate_route`.
- Board lanes (`references/kanban-lane.md`) are not checked by `omh_team` yet; they still follow the prepare and readback recipe there.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |