A simple, open format for organizational operating systems.
Like AGENTS.md tells coding agents how to work on your codebase, ORG.md tells operational agents how to work within your organization.
Every AI conversation about your work starts from scratch. The agent doesn't know:
- Your methodology (EOS? OKRs? Custom?)
- Your vocabulary ("rock" means 90-day priority, not geology)
- Where things live (file structure, naming conventions)
- When you work (deep work hours, meeting days)
- What format you expect (your templates, not generic output)
One file. Seven sections. Machine-readable context for organizational AI.
ORG.md
├── Operator # Who's running this OS
├── Framework # Your methodology and vocabulary
├── File System # Where artifacts live
├── Scheduler # Time blocks and task routing
├── State # Progress tracking and persistence
├── Templates # Artifact structures
└── Commands # Defined operations
-
Clone the repository:
git clone https://github.com/richardblythman/org.md.git cd org.md -
Run Claude Code in the directory:
claude
-
Initialize your organizational OS:
/init_org_os
This will create an ORG.md file at your workspace root configured for your organization.
- Read the full specification
- See a complete example
| Without ORG.md | With ORG.md |
|---|---|
| "Create a quarterly goal doc" | /new-rock "Launch mobile app" |
| Generic template output | Your format, your fields |
| "Where should I save this?" | Predictable file locations |
| Context lost between sessions | State persistence and restoration |
| Same explanations every time | Methodology encoded once |
See SPEC.md for the complete specification.
- EOS Product Team - Full example for a product team using modified EOS
- Lean Startup - Strategy validation through structured experimentation
ORG.md is an open specification. Contributions, feedback, and real-world examples welcome.
CC BY 4.0