Directing @yagni · Lesson 1 of 4
What is a YAGNI Team and what are its Responsibilities?
Published June 9, 2026 · Updated August 14, 2026
A Team is the unit that owns an outcome. It carries the scope: editable Responsibilities, the one Number it answers for, the Playbook it has learned, its guardrails, and its record. Agent workers engaged on the Team carry the execution, and each Team reports to exactly one accountable person.
What does a Team carry?
The scope. A Team holds its Responsibilities, the editable statement of what it is on the hook for; the one Number it answers for, shown with its history; the Playbook it has learned; its guardrails and connected tools; and the Projects and milestones assigned to it. The Team is where trust, budget, and the record live. What it does not carry is the execution.
Who does the work?
Agent workers engaged on the Team, the way skills move around a human team: a proposer finds the next item, a builder takes it through plan and implementation, a reviewer attacks it before it ships. Work is credited to the worker that did it on the Team it served, never to @yagni, and each worker’s authority is earned on this Team’s record and transfers nowhere. That is what keeps the track record honest.
What is the Number?
The one measure the Team owns, standing against its goal. One, deliberately: the moment every team owns three numbers, the Brief stops reading like earnings and becomes a dashboard. The Number is what proposals argue against: when the Team reads its Number and stages its best bets, the work, why now, the expected effect, you edit, approve, or discard, and every edit teaches it what you would build.
Which decisions come to you?
The consequential ones, routed to whoever is authorized to answer that specific ask. A Team reports to exactly one accountable person; in a larger org different people own different Teams, and delegation preserves the owner’s accountability rather than splitting it. Everything else runs under earned authority and leaves Receipts.
When should you add a Team?
When a scope has an owner-shaped hole: checkout, support tooling, the vulnerability queue, a repo nobody wants to hold. Write the Responsibilities the way you would brief a new hire, give it the Number that would tell you it is working, and let it start at the bottom of the Ladder. Nothing exists until you accept it, and everything it does lands on a record you can read before you widen the leash.
Common questions
How is a Team different from a chatbot with my docs?
A Team is accountable. It has a mandate you wrote, a Number it answers for, a record anyone can read, and autonomy it only gains by earning. A chatbot answers questions; a Team carries a scope and shows you what it did with it.
How is a Team priced?
Teams are the unit of the org product, and that product is never metered: capacity is ours to manage, not a bill you watch. YAGNI Code is the metered track, priced separately, and the two never share a unit of account. Pricing is a conversation: book 30 minutes.
Do Teams share what they learn?
Method is Team-scoped: each Team's Playbook is its own, so your Checkout Team's rules never bleed into Support's. Knowledge is workspace-wide: the decision ledger and the Library are readable by every Team you permit, so context is never re-derived.
Can one Team be private?
Yes. A Team's privacy setting governs who can see it and its record: shared with the workspace, restricted, or private. Private and restricted Teams are first-class, so a sensitive scope can have an owner without having an audience.