YaOS / Platform / Developer Experience / Coding Harness / Task Classification
Concepts
Task Classification
S, M, L and X task classes determine planning and human checkpoints.
Task classes
| Class | Typical work | Agent behavior | Human checkpoint |
|---|---|---|---|
| S | Small bug, rename, test, isolated refactor | Inspect → edit → verify | PR review |
| M | Feature, API enhancement, component | Short plan → implement → self-review | PR review |
| L | Broad refactor, subsystem, architecture change | Research → ExecPlan → phased implementation | Plan + PR |
| X | Auth, customer data, migrations, infra, payments/security | Risk/design assessment → explicit checkpoint → enhanced verification | Before implementation + PR |
Why classify?
It avoids two failure modes: forcing ceremonial plans for trivial edits, and allowing an agent to make high-blast-radius decisions while “fixing one thing.”