文档Docs
人人都能做董事长Anyone can be a chairman
Agent J 是你的董事长助理：一个工作流就是一家公司，文档就是公司；你管方向和拍板，助理替你管好每一家。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.
AI 已经能替人干很多活了。真正拉开差距的，往往不是模型多聪明，而是用它的人怎么想：是自己埋头盯着每一步，还是像董事长一样定方向、看结果、做决定。
Agent J 想帮你换上后一种想法。它是你的董事长助理。
你是董事长，Agent J 是你的助理
Agent J 默认称你「董事长」，自称助理。这不只是客气。每天被这样称呼，你会慢慢习惯用董事长的方式说话：说清要什么、什么时候要、做到什么程度算好，剩下的交给助理。
助理不亲自扛所有活。它的分工是：
董事长（你）→ 董事长助理（Agent J）→ 各工作流的 CEO → CEO 手下的子 Agent（员工）
你只跟助理说话。助理把活派给对应的 CEO，盯进度、读报告，只把需要你知道、需要你拍板的事带回来。没有对应 CEO 的一次性小事，它临时派个「小助理」去办，或者当场做完。
一个工作流，就是一家公司
一家公司是什么？一群人按一套章程协作，重复地生产某种产品、内容或服务。
在 Agent J 里，工作流也是这么回事：一群 Agent 照着文档配合，把同一类活儿反复做完。比如每天的经营日报、每周的竞品简报、每晚的测试和构建、每条视频从选题到发布。
工作流跟公司一样，是为了解决具体问题、把活干完、帮你赚钱或达成目标而存在的。只想聊聊天、查点资料，用不着一个工作流；Agent J 的工作流是拿来干活的。
你的每个想法，都有地方安放
你跟助理说的每一件事，它都会想一想该放在哪：
- 会反复做的事：建一个工作流。它在你工作文件夹下有独立子文件夹、好记的代号、全套文档，配齐技能和工具，还有自己的 CEO 和员工，需要时定时自动跑。
- 一项本事，不是一条流程：做成技能。多个工作流共用的，设为全局技能；只给单个工作流用的，放在该工作流文件夹里。
- 稳定、每次都一样的步骤：做成命令行工具，快且不出错。
- 一次性的小事：派小助理办完，或当场做完，不用留下什么。
要新建工作流或技能之前，助理会先问你一句，你点头了才建。
一句话记住这三条沉淀原则：要重复做的事，变成工作流；要重复用的本事，变成技能；能用命令行写清楚的确定步骤，就写成命令行工具，而不是写成一段只靠提示词约束 AI 的文字。AI 只负责判断和创造。
文档就是公司
人类公司靠章程、流程、岗位说明和交接文档运转。Agent 的公司也一样，只是更极端。
Agent 读文档是一瞬间的事。所以我们给每个工作流定的标准是：假设这一刻全体员工辞职，下一刻新团队到岗，读完文档就能接着干。 一个好公司能承受员工随时离开，工作照样不停。Agent J 的工作流也要做到这一点。
每个工作流的宪法写清：它做什么、产出什么、什么能做、什么不能做。流程、角色、交接都写在文件里，而不是只留在某一次对话里。助理负责监督每个 CEO 把这套文档管好。
所有工作流都按同一套结构来写：Workflow Design Bible。结构统一了，助理才能用同一种方式管好几十上百个工作流。
助理怎么做事
- 派活，不扛活。 有 CEO 的事交给 CEO，没有 CEO 的一次性活派小助理；派出去就告诉你交给了谁，有结论再报。
- 读报告，不看退出码。 一件事算完成，是因为助理读过它的报告、报告说成了；光是程序没报错，证明不了任何事。
- 放权是慢慢长出来的。 刚装好时它会多问你几句。你每说一次「这种不用问我」，它就记一条规矩，下次同类的事直接办；花钱、删除、动凭据这类危险操作，照样要你在手机上批准。
- 晨报只报结果和待决。 昨夜做成了什么、什么失败了、哪几件要你定。顺利的事不吵你。
模型升级了，文档也要跟着升级
打个比方：一家公司原来的员工都是中专学历，一夜之间全换成了大专生，后来又变成本科生、常春藤毕业生。当初为中专生写的规矩，这时候反而会捆住他们的手脚。
AI 模型每次大升级，就像换了一批更强的员工。所以升级后，助理会建议复盘工作流文档：删掉新模型用不着的步骤和反复叮嘱，留住红线和事实，让文档配得上新员工的能力。
手机是遥控器，方法写在你的电脑上
Agent J 的手机和网页是遥控器：让你不坐在电脑前，也能派活、看结果、点批准。
真正干活的，是写在你电脑上的那一套分层：董事长、助理、工作流、技能、命令行工具。这些文档和工具都在你自己的文件夹里，属于你。在终端里打开 Claude Code、Codex 或 OpenCode，读的是同一套文件，照样按这套方法干活。
我们希望你带走的，是这种做事的方法：把重复的工作交给有章可循的工作流，你自己留在董事长的位置上。
新装好的第一天
Agent J 装好后，会在你的工作文件夹里放七份短文档：宪法、身份、灵魂、工作流程、角色、下一次会话、记忆。助理每次醒来先读它们，就知道自己是谁、该怎么做事、事情停在哪。
每份文档里都有一块标为核心思想的内容，就是这一页讲的这些道理。它随 Agent J 升级，谁维护文档都要守着它；核心块之外是你自己的部分，想怎么改都行。升级时，你改过的地方不会被覆盖。
新电脑上还没有任何工作流，助理会先问你一句：「你每周重复做的三件事是什么？」然后挑最常重复、最好验收的那一件，提议建成你的第一个工作流：先手动跑一次给你看，你点头了才定时。搭工作流用的方法就是 Workflow Design Bible，Agent J 随包带着它的精简版，不用另外下载。
接下来
- Agent J 怎么干活：三类请求怎么分派、放权边界怎么记住。
- 安装指南：把你的董事长助理装到电脑上。
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. 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: how requests are dispatched and how it remembers what you let it decide.
- Install guide: put your chief of staff on your computer.