Give coding agents the project context they keep asking for

Agents and new contributors read the code. KOS gives them the reasons behind it.

The problem

Coding agents rediscover the same constraints from the code, or miss them. Implementation decisions live in PR threads and chat logs.

Each agent session starts with a long re-briefing, or without one.

Synthetic example

A refactor that resumes cleanly

An agent was halfway through a refactor when the session ended. The next agent, in a different tool, needs to continue without undoing anything.

The next agent starts from the handoff and the decision, not from a guess.

payments-service
architectureService boundaries and why refunds are separate
decisionKeep the legacy webhook format until clients migrate
handoffRefactor stopped at payments/refunds; tests pending

What KOS gives you here

Repository context

Architecture notes and constraints kept next to the work they describe.

Agent handoffs

A consistent record of where an agent stopped and what is next.

Preserved decisions

Implementation decisions that survive the end of a session.

Your first useful outcome

  1. 01

    Describe the architecture

    A short note on boundaries and constraints.

  2. 02

    Record open decisions

    Especially the ones agents keep questioning.

  3. 03

    Require a handoff

    Ask each agent session to finish with one.

Start with one project

The Starter Kit is free and open source. One project is enough to see the difference in your next session.

Get KOSRead the guide