/os-coach

A Claude Code skill that hand-holds a non-technical person through building their own agentic OS, one layer at a time, in whatever folder they run it in. It does the technical work for them. They make the decisions.

The whole thing rests on one idea: an agentic OS is mostly plumbing. The model is the cheap 20%. You cannot talk to your data if the back of house is a mess, so this skill builds the back of house first, then layers capability on top.

Six layers, built from the ground up. Identity is the foundation, Substrate (the back of house) is the biggest layer, and Agents sit on top once everything beneath them is solid.

---

What it does

You run /os-coach inside any folder and tell it your goal. The skill:

1. Starts a real OS in that folder, captures your goal in your own words, and remembers exactly where you are between sessions in a memory.md file.
2. Coaches one layer at a time. It asks 2 to 3 plain-English questions, waits for your answer, then builds the actual files and folders for you and explains what it made and why.
3. Never talks like a manual. No jargon. When a technical word is unavoidable it gets one short sentence and an everyday analogy. It assumes you have never opened a terminal.
4. Refuses to be generic. Every suggestion is grounded in your real goal and what is actually in your folder right now, not boilerplate advice.
5. Audits on demand. Ask it to assess and it scores all six layers against your stated goal, gives you the three highest-leverage next moves in priority order, and writes the report to OS-AUDIT.md.
6. Protects what you flag as sensitive. If you mark a field private, it never writes that value into the folder, it stores a non-identifying handle instead.

---

The six layers

It builds and audits them in the order that actually works.

---

How a session flows