--- title: Anyone can be a chairman nav: Philosophy summary: Agent J is your chief of staff. A workflow is a company and its documents are the company; you set direction and decide, and your chief of staff runs the rest. order: 34 --- # Anyone can be a chairman AI can already do a great deal of work. What separates people now is less how clever the model is and more how its user thinks: hovering over every step, or setting direction, reading results and making the calls the way a chairman does. Agent J is built to move you toward the second habit. It is your **chief of staff**. ## You are the Chairman; Agent J works for you Agent J calls you "Chairman" and itself your chief of staff. That is not flattery. Hear it every day and you start talking like one: say what you want, by when, and what good looks like — then let your chief of staff handle the rest. A chief of staff does not do all the work personally. The structure looks like this: Chairman (you) → chief of staff (Agent J) → each workflow's CEO → the sub-Agents (staff) under that CEO You talk to your chief of staff. It hands work to the right CEO, follows progress, reads the reports, and brings back only what you need to know or decide. A one-off with no CEO goes to a "junior assistant" it sends on the spot, or it simply does the small thing itself. ## A workflow is a company What is a company? People who work together under a charter, producing the same kind of product, content or service again and again. A workflow in Agent J is the same thing with Agents for staff and a set of documents for a charter: a daily sales report, a weekly competitor brief, a nightly test-and-build run, a video channel from topic to publish. And like a company, a workflow exists to get something done — to solve a concrete problem, finish real work, and help you earn or reach a goal. If all you want is a chat or a quick lookup, you don't need a workflow. Agent J's workflows are for work. ## Every intention has a home Whatever you tell your chief of staff, it asks where that should live: - **Work that repeats** becomes a workflow: its own folder inside your working folder, a memorable code name, a full set of documents, the skills and tools it needs, its own CEO and staff, and a schedule if it should run by itself. - **A capability rather than a process** becomes a skill. If several workflows will use it, it is a global skill; if only one will, it lives inside that workflow's folder. - **Steps that are stable and identical every time** become a command-line tool: faster, and the same every run. - **A one-off** goes to a junior assistant or gets done on the spot, and nothing needs to be kept. Before creating a new workflow or skill, your chief of staff asks you once and builds it only after you say yes. The three settling rules in one breath: work you repeat becomes a workflow; a capability you reuse becomes a skill; a step that can be written as a command-line function becomes a command-line tool, not a paragraph of instructions that only a prompt holds the AI to. The AI is there to judge and create. ## The documents are the company Human companies run on charters, processes, job descriptions and handover notes. An Agent company does too, only more so. An Agent reads its documents in an instant, so we hold every workflow to one standard: **assume the entire staff resigns this minute and a new team walks in the next — they read the documents and carry on.** A good company survives people leaving at any time without the work stopping. An Agent J workflow should too. Each workflow's constitution states what it does, what it produces, and what it may and may not do. Process, roles and handover are written into files, not left inside one conversation. Your chief of staff makes sure every CEO keeps those documents in shape. All workflows share one structure, the [Workflow Design Bible](https://github.com/preangelleo/workflow-design-bible). One structure is what lets a single chief of staff run dozens or hundreds of them the same way. ## How your chief of staff works - **It dispatches; it doesn't carry.** Work with a CEO goes to that CEO; a one-off with no CEO goes to a junior assistant. Once it is handed out, you are told who has it and that a report will follow. - **It reads the report, not the exit code.** Work counts as done because the report was read and says so. A run without errors proves nothing on its own. - **Delegation grows over time.** Fresh out of the box it asks you more. Each time you tell it not to ask about a kind of thing, it writes down a rule and decides the next one itself. Spending, deleting and touching credentials still need your approval on the phone. - **The morning brief is results and pending decisions.** What got done overnight, what failed, what you need to decide. Things that went well don't make noise. ## When the model gets smarter, the documents should too Picture a company whose staff all left school at sixteen. Overnight they are replaced by college graduates, later by university graduates, then by Ivy League hires. The rules written for the first group now hold the new people back. Every major model upgrade is a staff change like that. After each one, your chief of staff proposes that every workflow review its documents: drop the steps and repeated reminders the new model no longer needs, keep the red lines and the facts, and let the documents rise to the new staff's ability. ## Your phone is the remote; the method lives on your computer Agent J's phone and web app are a remote control. They let you hand out work, check results and approve things without sitting at your desk. The part that does the work is the set of layers written down on your computer: Chairman, chief of staff, workflow, skill, command-line tool. Those documents and tools sit in your own folder and belong to you. Open Claude Code, Codex or OpenCode in a terminal and they read the same files and work the same way. What we hope you keep is the method: give repeated work to workflows with clear rules, and keep your own seat at the head of the table. ## Your first day Once installed, Agent J puts seven short documents in your working folder: constitution, identity, soul, workflow, roles, next session and memory. Your chief of staff reads them every time it wakes up, so it knows who it is, how to work and where things stopped. Each document has a block marked as the core ideas — the ideas on this page. It is upgraded with Agent J, and whoever maintains the documents keeps it; everything outside the block is yours to change as you like. Upgrades never overwrite what you changed. On a new computer there are no workflows yet, so your chief of staff starts with one question: *what are three things you do again and again every week?* It picks the one that repeats most and is easiest to check, and proposes it as your first workflow: run once by hand for you to see, scheduled only after you say yes. Workflows are built with the Workflow Design Bible method; Agent J ships a cut-down version of it, so there is nothing extra to download. ## Next - [How Agent J works](/docs/how-agentj-works/): how requests are dispatched and how it remembers what you let it decide. - [Install guide](/docs/install/): put your chief of staff on your computer.