Streamline Workflow with CEOS: Claude Meets EOS – Cyber Tech

I’ve been conscious of EOS (Entrepreneurial Working System) for over a decade. A lot of firms I’m on the board of use some aspect, or all of it. A number of mates, together with Bart Lorang, are EOS Implementers.

Final night time, whereas watching Olympic highlights and the primary few episodes of Steal, I created a v0.1 of CEOS — an open-source mission that brings the core EOS toolkit to any Claude Code session. I went from an empty GitHub repo to a public-ready mission in about 90 minutes. Please be happy to make enjoyable of Amy and me about how we spend our Friday nights.

EOS has nice instruments — V/TO, Rocks, Scorecard, L10 Conferences, IDS. However most firms implement them in a patchwork of Google Docs and spreadsheets. Or Notion pages. Or possibly they use one of many EOS-related SaaS merchandise. The info finally ends up scattered throughout platforms, locked in proprietary codecs, and disconnected from the precise conversations the place selections occur.

Since I’m dwelling inside Claude Code (and integrating increasingly of my workflow to it), I assumed I’d see if I may make a set of expertise that implement EOS. I’m engaged on one other mission (non-public at this level, however possibly I’ll open supply it) referred to as CompanyOS, which, whereas centered on a really early-stage firm (just like the 5,000+ which have gone via Techstars), probably may scale.

CEOS is constructed on three concepts:

1. Every little thing is a file. Each Rock, each Scorecard entry, and each L10 assembly is a Markdown file with YAML entrance matter. Human-readable on GitHub, parseable by any instrument, and diffable in git. No database. No SaaS subscription. Git historical past is your audit path.

2. Expertise, not software program. CEOS isn’t an software — it’s a set of Claude Code expertise. Every ability teaches Claude find out how to facilitate a selected EOS workflow. You say “let’s set our quarterly rocks” and the ceos-rocks ability walks you thru the method: reviewing the V/TO for alignment, amassing titles and homeowners, validating the 3-7 rule, producing the information. You say “run our L10” and ceos-l10 pulls your scorecard knowledge, critiques your Rocks, checks final week’s precise to-dos, and facilitates IDS in your prime 3 points.

3. Fork and personal it. The upstream repo (bradfeld/ceos) has expertise, templates, and docs — no firm knowledge. You fork it, run ./setup.sh init, reply 4 questions (firm identify, quarter, staff members, L10 day), and your EOS knowledge lives in your fork’s knowledge/ listing. Pull upstream for ability updates; your knowledge stays untouched.

Right here’s the timeline of the work I did with Claude Code. It carried out every little thing – I simply supplied the steerage. And sure, Claude got here up with the timeline beneath. Should you aren’t technical and don’t care, skip the following 10 paragraphs – they’ll be boring. However, if you’re technical, it’s sort of fascinating what Claude determined, totally by itself, to do.

9:38 PM — gh repo create bradfeld/ceos --public --add-readme --license mit --clone. One command created the GitHub repo, initialized it with LICENSE and README, and cloned it regionally.

9:42 PM — Repo scaffolding. README with mission overview and structure diagram. CONTRIBUTING.md addressing two audiences (EOS practitioners and builders — intentionally totally different ability units). .ceos marker file for ability repo-root detection. .gitignore that retains knowledge/ out of the upstream repo. Listing construction for expertise, templates, and docs.

9:50 PM — Seven EOS template information. This was the primary actual design choice: which information get YAML frontmatter (structured knowledge that expertise parse programmatically) vs. that are pure markdown (reference paperwork people learn). The reply: frontmatter for objects with lifecycle state — Rocks have standing: on_track, Points have ids_stage: recognized, L10 conferences have ranking. Pure markdown for reference paperwork just like the V/TO and Accountability Chart.

10:04 PM — The setup script. Pure bash, zero dependencies. Three modes: ./setup.sh (symlink expertise), ./setup.sh init (guided setup), ./setup.sh --uninstall (clear removing). Two portability selections that matter: utilizing | because the sed delimiter as an alternative of / so file paths in values don’t break substitution, and avoiding sed -i totally (macOS and GNU Linux deal with it in another way) by utilizing temp information as an alternative.

10:23 PM — 5 EOS expertise. This was the meat of the mission. Every ability is a SKILL.md file — basically a immediate engineering doc in structured kind. The important thing stress in writing expertise is comprehensiveness vs. followability. An excessive amount of element and Claude skims; too little and it improvises. The sample that labored: tables for quick-reference knowledge (standing enums, file paths, modes) and prose for workflow logic.

The 5 expertise:

• ceos-vto — Evaluate and replace the Imaginative and prescient/Traction Organizer. Exhibits diffs earlier than writing. Runs alignment checks between sections.
• ceos-rocks — Three modes: setting (with V/TO alignment checks, 3-7 validation, ID era), monitoring (milestone progress, standing updates), and scoring (binary full/dropped, quarter scorecard with 80% goal).
• ceos-scorecard — Outline metrics with targets and thresholds, log weekly values, 13-week pattern evaluation with automated escalation to the Points record.
• ceos-l10 — The total Degree 10 Assembly. Seven sections with time containers. Pulls actual knowledge from scorecard and rocks information. Opinions precise to-dos from final week’s assembly. Facilitates IDS on the highest 3 points. Captures assembly ranking.
• ceos-ids — Structured subject decision with 5 Whys for root trigger identification, dialogue seize, and to-do era.

A essential design selection: expertise reference one another however by no means auto-invoke. The L10 ability mentions that ceos-ids can create subject information, however helps you to resolve when to change. Free coupling via mentions, not tight coupling via auto-invocation.

10:39 PM — 5 documentation information focusing on totally different audiences. The EOS primer interprets enterprise ideas into developer vocabulary. The info format spec interprets the identical content material right into a parsing contract. The skill-authoring information sits on the intersection—it’s immediate engineering documentation in disguise as a contributor information. A ability reference offers customers with a fast overview of all 5 expertise, together with set off phrases and examples.

10:52 PM — GitHub configuration. CODEOWNERS, three subject templates (EOS Course of Request, Bug Report, Talent Enchancment), a PR template with earlier than/after sections, and customized labels. The problem templates are intentionally totally different — one for EOS practitioners (“I believe the Rock scoring course of ought to work in another way”), one for builders (“setup.sh fails on Ubuntu”), one for ability enhancements (“ceos-l10 ought to deal with recurring agenda gadgets”).

11:08 PM — Closing cleanup. Eliminated companyos-integration.md which contained inside particulars about how CEOS would combine with our non-public CompanyOS system. Archived the content material to a Linear remark earlier than deleting — git historical past preserves it, however a Linear remark makes it findable with out git archaeology.

Throughout this, my Claude occasion realized a couple of issues which were integrated into our native studying (a dynamic file I preserve and use to replace expertise throughout periodic sweeps).

Writing expertise are immediate engineering in doc kind. The most important lure is the description area. Should you write “manages Rocks in three modes with binary scoring,” Claude will comply with that abstract and skip the detailed course of sections. The outline ought to say when to make use of it (“use when setting, monitoring, or scoring quarterly Rocks”), not what it does. The physique has the what.

Templates want lifecycle consciousness. The excellence between frontmatter and pure markdown isn’t about complexity — it’s about whether or not the file has state that adjustments over time. A Rock strikes from on_track to off_track to full. A V/TO doc is edited however doesn’t have lifecycle states. That distinction determines whether or not a ability can programmatically question and handle the info.

Documentation for AI expertise packages wants three layers. Person-facing (what can I do?), contributor-facing (how do I add?), and machine-facing (what’s the contract?). Most tasks get the primary two. The third — the info format spec that makes YAML frontmatter an actual, transportable, parseable contract — is what makes the ecosystem extensible.

The .ceos marker sample is underrated. Borrowed from .git and .npmrc, a zero-byte marker file on the repo root provides each ability a dependable approach to discover the CEOS repository no matter the place the person’s working listing is. No atmosphere variables, no configuration, no hardcoded paths. Simply search upward for .ceos.

CEOS is reside at github.com/bradfeld/ceos. MIT license. Do no matter you need with it. If you’re into EOS, come play. I’ll take note of any PRs and points. Following are the following few issues I’m going to create.

• Course of Documentation ability — The sixth EOS element. Doc core processes as checklists with followability metrics.
• Folks Analyzer ability — Proper individuals, proper seats. The GWC (Get it, Need it, Capability to do it) analysis instrument.
• Quarterly Dialog ability — The formal quarterly check-in between managers and direct reviews.
• Annual Planning ability — Yr-end V/TO refresh and next-year Rock setting.

And, whereas I used to be making an attempt to provide you with a reputation for this, with Claude, it instructed me I would like to incorporate the next footer.

CEOS is an impartial open-source mission. It isn’t affiliated with or endorsed by EOS Worldwide.