Delegation-grade, or a spec an agent runs cold

There is a spec you write to organize your own thinking, and there is a spec you write to hand off. The second is a higher bar, and it is the one that unlocks the Orchestrator mode later, because you cannot route work to multiple agents if your specs only make sense inside your own head. The bar has a name in your practice: delegation-grade. A spec is delegation-grade when something that has never seen the problem could execute it correctly and could not execute it incorrectly.

That phrasing is doing real work. It is not enough that a capable agent could get it right if it read your mind. The spec has to carry its own context, so the right build is the obvious one and the wrong build is ruled out by what you wrote. If an agent could plausibly produce something that passes your words but misses your intent, the spec has a hole, and the hole is yours, not the agent's. Writing to this bar forces you to surface the assumptions you were about to leave implicit, which is exactly where handoffs break.

Why this is the skill that scales you

Because a solo operator's ceiling is set by how much they can safely hand off. A spec only you can execute keeps everything routed through you, and you become the bottleneck in your own system. A delegation-grade spec can go to Claude Code, to a subagent, to a teammate, to a future you who has forgotten everything, and come back right. That is what lets one person run parallel work instead of doing it all in series. The spec stops being a note to self and becomes a unit of delegation.

The Field Manual's spec track has the delegation-grade drills. In the operating system, this is the spec that makes orchestration possible.

The takeaway: A delegation-grade spec is one something that never saw the problem could execute right and couldn't execute wrong. Writing to that bar surfaces your hidden assumptions and is what lets you hand work off instead of being the bottleneck.