← ClaudeAtlas

delegationlisted

How to split a substantial task across agents: the three-layer model, the architecture matrix, effort and model-tier calibration, brief rules, and the never-delegated floor. Use when sizing a feature build, refactor, migration, audit, or multi-file fix; when the work arrived as a goal ("clean this up", "get it published") rather than as a list of slices; when crews, teams, managers, subagents, or waves come up; when token cost on a big job is a worry; or when a session has been editing files itself for a long stretch without delegating.
hsb3/dotfiles-agents · ★ 0 · AI & Automation · score 70
Install: claude install-skill hsb3/dotfiles-agents
# Delegation <!-- harness:claude-code --> In Codex, first read [Codex distribution](references/dispatch-knobs.md#codex-distribution) for installed role setup, native dispatch, isolation prerequisites, and completion routing. That section supplies the Codex procedures wherever this workflow names Claude Code tools. <!-- /harness --> Delegated work runs on three layers: **strategy**, **management**, **execution**. Each has work that is irreducibly its own, a context it must carry and a context it must never be handed, and things it must never do. Three layers is the default for anything non-trivial. Collapsing one is an exception that has to be justified against the conditions below, not a tiebreak. Premium session tokens buy decomposition, judgment, and verification. They do not buy file-reading or bounded edits. Self-contained: usable without any other skill; `rubric-panel`, `layer-cycle`, and `handoff` extend it where named below. **Provenance tags.** `[lab]` was measured in the inventory lab (three controlled experiments × three languages, anchored-rubric panels). `[cost]` comes from measured delegation-cost and context-economics findings. `[field]` was observed in practice by the repo owner but has not been reproduced under measurement. `[untested]` is reasoning that has never been measured. Change `[untested]` first when evidence arrives, and never defend any tag as if it were a finding it is not. The map from rule to measurement is `references/provenance.md`. ## Th