Control primitivesv0.1.0

fan-out-work

Runs the same bounded pipeline over independent items in parallel without hiding failures or dropped coverage.

WORKFLOW / 05/fan-out-work <the work — e.g. 'add tests to every untested module' or a path to a work-list>
  1. 01

    Scout and freeze the complete work list before delegation.

  2. 02

    Define the identical per-item pipeline and terminal outcomes.

  3. 03

    Set concurrency, retries, isolation, budget, and an explicit drop policy.

  4. 04

    Run items concurrently while the coordinator retains stop/continue judgment.

  5. 05

    Reduce results and account for every covered, failed, blocked, and dropped item.

operating envelope

Use it deliberately.

The shortest useful definition of where this skill helps—and where it should stay out of the way.

Use when

  • A large, cheaply discoverable list of independent items needs the same treatment.
  • Per-file review, tests, migration, or auditing would waste wall-clock when run serially.
  • The result can be faithfully reduced after every item reaches a terminal state.

Do not use when

  • The list contains only a handful of items.
  • Items depend on one another and therefore require a DAG.
  • Parallel items share write scope without worktree isolation.

output contract

What must be true when it stops.

Produces

  • Frozen item inventory and independence basis
  • Per-item pipeline, isolation, retry, and drop policy
  • Covered, failed, blocked, and dropped-item ledger
  • Optional reduced or merged result

Guarantees

  • The coordinator proves independence before parallel execution.
  • Failed or null items remain visible in the result.
  • Any top-N, sample, or overflow cap lists exactly what it omitted.
  • Parallel writers use isolation or are sequenced.
  • The final accounting includes every discovered item.

Honest failure states

  • failed_item — an agent returned an error or null result
  • blocked_item — the item cannot complete inside the declared pipeline
  • dropped_item — a named sampling or cap rule excluded the item
  • not_independent — cross-item dependencies require a DAG instead

enforcement

Know which claims are executable.

Scripts are linked when this skill owns deterministic machinery. The remaining rules are explicit operating contracts and must not be marketed as hooks.

install and invoke

One skill, three honest surfaces.

skills.sh

Available

Universal skill installation, including Claude Code and Codex.

npx skills add https://github.com/ulpi-io/skills-autonomous-engineering --skill fan-out-work

Claude Code plugin

Available

Install the full plugin, then invoke /fan-out-work or let routing select it from context.

Claude installation →

Codex plugin

Work in progress

A work in progress on the codex-native-plugin branch — build it, start a new session, then invoke $autonomous-engineering:fan-out-work.

Codex installation →