Campaigns over a goal

The idea

A campaign is a root item and all work under it, with limits, one-click hold and resume, one instruction sent to all open work, and a report of runs, pull requests, cost and follow-ups.

The problem
Large delegated efforts were hard to stop, steer or measure as one unit.
Why it matters
An owner controls and reports on a whole effort at once.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Command Center and drill-down

    A live console shows totals, a runtime map, a control desk and telemetry from stored records, and every page opens a stacked drill-down down to the step, with a why-trace and question threads.

  • Delegation down the chain with fan-out

    A manager splits work into parts, creates every child in one transaction with dependencies, and waits once for all of them.

  • CEO front door over a worker hierarchy

    The operator talks to one CEO worker; department heads and workers sit below it, and each level's budget and tool limits bind its whole subtree.

  • Parallel work in one repository by footprint

    Each plan predicts the files and functions it touches; overlapping work goes to the same worker or waits, and disjoint work runs side by side without worktrees.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.