YaOS / Platform / Developer Experience / Coding Harness / Getting Started
Getting Started
Getting Started
Onboard a repository and start using the harness with minimal setup.
New repository
- Add
.harness/project.yaml. - Select only the profiles that describe the stack.
- Define canonical setup, test, lint, typecheck and eval commands.
- Add a concise architecture/project context document.
- Run harness sync to generate the tool-specific adapters.
- Run harness doctor / validation before committing.
Starting work
| Task | Execution |
|---|---|
| S — Small | Inspect → edit → targeted verification → finish |
| M — Normal | Inspect → short plan → implement → verify → self-review |
| L — Significant | Investigate → ExecPlan → implement in phases → independent review |
| X — High risk | Investigate → explicit risk/design review → human checkpoint → enhanced verification |
Rule of thumb: the developer should not have to learn a different engineering process for Claude, Codex and Antigravity. The adapter changes; the YaOS engineering contract does not.
Existing repository
- Inventory the current stack and CI.
- Create
.harness/project.yamlwith the detected commands and constraints. - Select profiles conservatively; do not add technologies the repo does not use.
- Populate architecture, contracts and known gotchas.
- Generate adapters in a migration PR.
- Run a small fixed eval set before making the harness the default.