Work orders
The anatomy of a Skaftor work order — the agent-executable unit of software work — and the execution manifest that lets an agent run it without re-gathering context.
A work order is the interface between planning and execution: a self-contained, agent-executable task compiled from intent, carrying its acceptance criteria, execution context, and links back to the requirements and architecture it serves.
Anatomy
- Scope — what to build and the boundary it must respect.
- Acceptance criteria — how 'done' is defined.
- Execution manifest — the full context payload an agent consumes: intent, constraints, relevant files, prior decisions, and blast radius.
- Links — to parent requirements/blueprint and, once built, to the code that fulfills it.
Execution from the terminal
skaftor wo show AUTH-02 # full spec + acceptance criteria
skaftor wo plan AUTH-02 # repo, files, reuse, impact
skaftor wo manifest AUTH-02 # the full execution manifest as JSON
skaftor wo start AUTH-02 --branch feature/auth-2Because each work order links to its intent and its code, work orders are the atoms of the Intent-to-Production Thread.