agent-os

🧭

Plan, shape, batch, deliver

A coherent mission gets the planning depth it needs, a bounded branch becomes implementation-ready delivery units, and the developer chooses individual delivery or an explicit integrated batch.

🧾

Evidence before claims

The verify-before-done discipline turns "it works" into a command, an exit status and a result. A check that ran proves only what that check exercised — and unverified claims get named as unverified.

🚧

Authority follows the request

An implementation request authorizes in-scope repository work. The agent asks only for unresolved product decisions and stops delivery at the requested boundary.

🔍

Control the contract

Skills lock outcomes, boundaries and ground truth while leaving local tactics to the implementer. Material delivery gets independent review; a fully qualified small fix may skip it.

🤝

Two platforms, one source

Every skill ships once and loads in both Claude Code and Codex. Manual skills are opted into explicitly on both; automatic skills trigger themselves from the situation.

📐

Policy you can edit

A single policy.md is installed as a managed block in your global instruction files, and every repo grows its own living project policy through an interview instead of a template.

What it looks like

One planning entry adapts to the work — a vague desire can be clarified, a known feature can be covered against the repository, and evidence lands before any completion claim:

text

User:
/plan-work Reports feel useless for our big customers and I
don't know what to do about it.

Agent:
Is the pain seeing the data, or taking it with them? I will first
resolve what the repository already tells us.

User:
Taking it with them. They paste screenshots into slides today.

Agent:
The goal is now clear. I will inspect authorization, result limits,
and the existing report flow. If independent choices remain, I will
open a decision map; otherwise the plan can go straight to shaping.

    ...later, after shaping and delivery...

Command: npm test -- report-export
Exit: 0
Result: API, authorization, and CSV encoding cases pass.

Delivered to the requested boundary: one verified pull request.
Merge stays with you.

Read the whole journey in The work loop.

agent-osExplicit workflows, automatic disciplines