Skip to content
cccskills
FreePublished on GitHub

company-os

Meta-framework for how a company runs. Operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse, issue resolution, and 90-day rocks.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3 stars(GitHub 3 + cccskills 0)

Run score Not tested

See how to install

Files included (4)

  • SKILL.md3.1 KB
  • references/implementation-guide.md9.8 KB
  • references/os-comparison.md10.7 KB
  • references/six-components.md5.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Company Operating System

The operating system is the collection of tools, rhythms, and agreements that determine how the company functions. Making it explicit makes it improvable.

Why This Matters

Most operational dysfunction isn't a people problem — it's a system problem. When the same issues recur every week, meetings feel pointless, nobody knows who owns what, or quarterly goals slip — fix the system.

The Six Core Components

Every effective operating system has these six. See references/six-components.md for detailed implementation guidance on each.

  1. Accountability Chart — Who owns each outcome. One person per function, no shared ownership.
  2. Scorecard — 5-15 weekly metrics with owners and targets. Only red metrics get discussion time.
  3. Meeting Pulse — Daily standup → Weekly L10 → Monthly review → Quarterly planning → Annual planning.
  4. Issue Resolution (IDS) — Identify, Discuss, Solve. Maximum 15 minutes per issue.
  5. Rocks (90-Day Priorities) — 3-7 per person, binary (done/not done), reviewed weekly.
  6. Communication Cadence — Who gets what information, when, and how.

Operating System Selection

See references/os-comparison.md for full comparison. Quick guide:

If you are...Consider...
10-250 person company, founder-led, operational chaosEOS / Traction
Ambitious growth, need rigorous strategy cascadeScaling Up
Tech company, engineering culture, hypothesis-drivenOKR-native
Decentralized, flat, high autonomyHolacracy

Implementation Roadmap

Quick start (first 30 days):

  1. Build the accountability chart (1 workshop, 2 hours)
  2. Define 5-10 weekly scorecard metrics (1 hour)
  3. Start the weekly L10 meeting (no prep — just start)

These three alone will improve coordination more than most companies achieve in a year.

Common Failure Modes

  • Partial implementation: Half an operating system is worse than none — it creates theater.
  • Meeting fatigue: Replace meetings, don't add them.
  • Metric overload: Start with 5. Add when the cadence is established.
  • Rock inflation: Hard limit: 7 per person. When everything is a priority, nothing is.
  • Leader non-compliance: If leaders don't take it seriously, nobody will.

Key Questions

  • "If I asked five team leads our top 3 priorities, would they give the same answers?"
  • "Name a metric that tells us by Friday whether this week was good. Do we track it?"
  • "Who owns customer churn? Can you name that person without hesitation?"

Resources

  • references/os-comparison.md — EOS vs Scaling Up vs OKRs vs Holacracy vs hybrid
  • references/implementation-guide.md — 90-day implementation plan
  • references/six-components.md — detailed implementation for accountability, scorecard, pulse, IDS, rocks, communication

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

See all skills by SebastianLuser

Report a problem with this skill