Executable units, not vague tickets
skaftorAI decomposes a blueprint into Work Orders. Each one names its scope, its target repository and service, its acceptance criteria, and its dependencies — a self-contained brief that a person or a coding agent can pick up and run without a round of clarifying questions.
- Clear scope, acceptance criteria, and dependencies per unit
- Bound to a repository, branch, and service up front
- Assignable to a teammate or a coding agent
Grounded before it starts
Every Work Order carries an execution context — the repo, the branch, the relevant files, and the memory of how similar work shipped before. That context travels with the unit, so whoever executes it starts inside the right workspace, not from a blank page.
- An execution manifest that points at the real workspace
- Prior implementations surfaced as reference
- Impact analysis so the blast radius is known before work begins
Tracked from open to shipped
Work Orders carry their own history — who executed them, on which branch, with which model and IDE, and what it cost. That record feeds back into memory, so the next plan is grounded in how the last one actually ran.