Personal Corp OS

Manager uses your local Manager Config for repositories and boards; the distributed skill contains no personal workspace logs.

Personal Corp is a way to run a one-person company through AI agents: tasks out of your head, departments instead of one person's memory, a weekly retro instead of "I'll sort it out someday".

This repo holds everything you need for that: the story of how the system works, templates for the HQ and a department, and the open skills for Claude Code and Codex.

By Ris — AI development & vibecoding.

Русская версия: README.ru.md.

The problem: you are the bottleneck

Not because you work too little. Because strategy, memory, coordination, execution, and acceptance all sit in one pile — inside your head. While that is true, your department's throughput equals yours.

Hiring does not fix it: a new person takes the work but not the context, so you keep explaining. AI alone does not fix it either: an agent without context is the same new hire, except it does not remember yesterday.

The issue is not model strength. The issue is that context never leaves your head.

What agent rules actually are

Agent rules are a plain text file sitting in a folder. No magic: text you read with your eyes and edit by hand.

Such a file lives in every folder, and its content differs.

Opening a folder, the agent learns three things from that file.

Those three answers replace a long prompt. The agent gets them from the folder instead of your message, so you stop explaining the same thing every time.

The core idea: the folder defines the view

Start the agent from the HQ and it reads the HQ rules and sees the map of the whole system. Start it from a department and it reads the department rules and sees that domain, its tasks, and its skills. Same model, different view, set by the folder rather than by a long prompt.

Everything else follows from that: for this to work, context has to leave your head into files, and those files have to sit in folders that carry rules.

What a department is

A department is a folder that owns one domain and accumulates experience about it. Inside it has its own rules, its own tasks, and its own skills.

Which departments people start with

I run about thirty. These are the usual first ones:

Department	What it accumulates	Time to create it
Content	Voice, topics, finished texts, notes on what landed	You write regularly and re-explain your style every time
Research	Questions, found facts, sources, conclusions tied to decisions	You are looking up the same thing a second time
Sales	People, agreements, correspondence, deal status	You keep track of who was promised what in your head
Media	Briefs, prompts, finished assets, acceptance criteria	You generate images and video and the briefs get lost
Legal	Contracts, templates, wording you already agreed to	Every new contract is assembled from scratch
Finance	Expenses, subscriptions, recurring payments	You cannot recall what is charged every month

A department exists for repetition. Work that happened once is fine living in the HQ.

What a skill is

A skill is a written-down way of working that can be repeated. You walk the work by hand once, write the steps down, and from then on the agent runs them.

Four layers and who lives where

Layer	Who acts	What lives here
Management	The human	Goal, priorities, limits, the right to say "good enough"
Truth	The human writes, the agent reads	Rules, memory, indexes, source of truth
Operations	The agent executes, the human accepts	Tasks, queue, statuses, runs, departments
Observation	The agent collects, the human looks	Dashboards, metrics, blockers

A subagent lives only in the operations layer: it does not write truth about the system and does not accept results.

One test for any file: is this truth about the system, or is it the result of work? Truth sits in the folder from day one. Results are created by skills once there is something to record. That is why the templates ship no empty files for future reports, decisions, or glossaries.

The route: how experience becomes capital

graph LR
    A["Taskowner + criteria"] --> B["Executionhuman or agent"]
    B --> C["Acceptancegood enough or not"]
    C --> D["Patternwhat worked"]
    D --> E["Department memoryrules and decisions"]
    E --> F["Prioritynext week"]
    F --> A
    style A fill:#8b5cf6,color:#fff
    style C fill:#f59e0b,color:#fff
    style E fill:#10b981,color:#fff

1. Writing the task down. A thought becomes a task once it has an owner, done criteria, and a place to live. Before that it lives in you. After that both a human and an agent can pick it up.

2. Experience accumulating in departments. Artifacts and decisions settle in a department — a separate folder for its own domain. Next time the agent reads the department instead of reading you.

3. Retro with the agent. Once a week you look at what worked and promote it into rules. Whatever you corrected twice becomes a written rule and stops needing you.

The weekly rhythm

Three links on their own are a feature list. The rhythm turns them into a system.

graph LR
    R["retrowhat worked"] --> P["planningpriorities of the week"]
    P --> D["dailyliving full-week view"]
    D --> T["tasksinto departments"]
    T --> E["executionthe trace goes back into the task"]
    E --> R
    style R fill:#f59e0b,color:#fff
    style P fill:#3b82f6,color:#fff
    style D fill:#64748b,color:#fff
    style T fill:#8b5cf6,color:#fff
    style E fill:#10b981,color:#fff

The rhythm answers the question that usually stays unanswered: when exactly does experience turn into a rule. Answer: at the retro, once a week, not "someday".

The same word gives a different result dep