Turning a job posting into an AI Employee spec

A posting for a role that is mostly process already describes a system. The method sorts its lines into known-process work and judgement work, and turns the process lines into specified, gated workflows.

A posting for a process role already describes a system, written as a list of duties

Today

A duty list that hides the judgement lines

  • You have a posting drafted for a role that is mostly process, and you are about to hire against a document that already describes a system.
  • The posting lists workflows in the language of duties, which hides which lines are process and which are judgement.
  • Hiring a person for the process lines buys ramp time and turnover for work that follows known rules, and leaves the judgement lines buried in the same list.
With agents

Each duty line sorted, checked, gated and signed

  • The posting becomes a spec instead of a wish list.
  • The judgement lines stay with a person on purpose.
  • The role is buildable one workflow at a time.

How an agent runs it

The posting is the raw material. What the agent does with it is a sort, a check and a draft, and the result is a document a person signs.

01

Reads the posting and splits it into the workflows it actually lists

Every duty line becomes a candidate workflow with a name, so a line like "manage vendor onboarding" becomes the workflows it contains.
02

Sorts each line into known-process work and judgement work

Known-process work is work where the rules can be written, the inputs are named and the outputs are defined. Judgement work is work where the decision lives with a person; the entry on work that should stay human owns that boundary.
03

Runs each process line against readiness and marks what preparation it needs

The readiness checklist is the test. A line that fails a check becomes a scoped preparation task rather than a rejected workflow.
04

Drafts the spec for each process workflow

The inputs it reads, the decision rules it applies, the outputs it produces, the systems it touches, and where its consequential step sits.
05

Places one gate per workflow on its consequential step, naming the owner who holds it

The approval gates entry defines the gate and what it costs; the spec records where each one sits and whose name is on it.
06

Human gate

Routes the assembled spec, with the judgement lines marked as staying with a person, to the hiring owner for sign-off before anything is built. The spec is the artifact a person signs, and How It Works describes the gates it will run under.
07

Assembles the signed spec into the role's operating record

Each workflow has its owner, its gate and its readiness status from the day the first one starts running.

Results

What changes when the posting becomes a spec

The role described as a system

Each duty line is sorted and written down with its inputs, rules, outputs and gate, so the role is described as a system.

Judgement stays with a person

The sort marks them and the spec records who holds them, so no decision is delegated by accident.

Buildable one workflow at a time

Each process line is a scoped workflow with its own readiness status and gate, so the first one can run before the last one is specified.

Where this fits

AI Employee

This is the AI Employee tier, reached through the AI Employee door: a full role's worth of known-process work, delegated as a set of specified workflows rather than as one task. One workflow proves the pattern on the rung below, and a department of several roles under one management layer is the rung above; the spec is what makes the step between them a document. How It Works describes the gates every workflow in the spec runs under.

Tier 2 / Scale
How It Works

Questions, answered

Then it is a hire, and the spec says so. The process lines that remain may still be worth running as a single workflow, which is the rung below this one, rather than as a role.

AI Opportunity Audit

Sort the posting before you publish it

Send the posting instead of publishing it, and sort it together.