Sandbox
@Workflowsio/company-os-starter-kit

Claude Code company OS starter kit

This repo helps you build a markdown-based Company OS for Claude Code. `CLAUDE.md` acts as the hub, `blueprint/` holds your company context and playbooks, `gtm-skills/` adds reusable skill files, and `plugin/` adds workflow commands. The hook scripts add safety checks, logging, and notifications around agent actions.

84 stars16 forksShellUpdated 5mo ago
Who it's for

Builders who want to package their business context, skills, and guardrails for Claude Code.

What it delivers

You can give Claude Code persistent company knowledge instead of re-explaining your business every session.

What it does

CLAUDE.md master template

A central file that Claude reads on load and uses as the entry point to the rest of your company context.

Blueprint folder structure

A ready-made `blueprint/` layout for company docs, wiki pages, skills, archive files, raw inputs, and hooks.

Five GTM starter skills

Reusable skill files for outbound copywriting, LinkedIn posts, ICP modeling, GTM strategy, and discovery prep.

Workflows plugin commands

A bundled `plugin/` directory with commands for planning, working, reviewing, brainstorming, compound knowledge, and swarm execution.

Safety and logging hooks

Shell hooks for blocking dangerous tool calls, logging session events, and sending desktop notifications.

Setup and customization guides

Guide files that explain how to install the kit, extend the skills, and adapt the structure to your business.

How to get it

  1. 1Open your project in Claude Code and say
    Read the CLAUDE.md and all the files in this repo.
    Interview me about my business and help me
    fill everything in. Go section by section.

README

Claude Code Ready 5 Skills 6 Plugin Commands 3 Hooks MIT License

Company OS Starter Kit

Build your own Company OS with Claude Code.

We're building an AI-native GTM services company. We scaled to 20 people in under 9 months. Bootstrapped. Claude Code has become a huge part of how we operate.

This is the starter kit for building the same kind of system. The folder structure, the skills, the safety hooks, and the setup guide we wish we had when we started.

Built by Dan Rosenthal at workflows.io. Full setup guide on Notion.


What is a Company OS?

A Company OS is a set of files (primarily markdown) that gives your AI persistent knowledge about your business. Your tools, your processes, your rules, your voice, your team. Instead of re-explaining your business every conversation, Claude starts every session already knowing who you are.

At the center is CLAUDE.md, the one file Claude reads on load. It points to everything else: company context, skills, tool connections, safety rules. Not a prompt you paste. An operating system that compounds the more you use it.


What's in the Kit

Root

FileWhat it does
CLAUDE.mdThe master template. Your AI's operating system. Fill this in first.
PLUGIN-GUIDE.mdHow to install the Workflows Engineering Plugin (bundled in plugin/, not an external marketplace install)
LICENSEMIT
.gitignoreIgnores session logs, credentials, OS files, editor files

blueprint/ - Your Company OS folder structure

Copy this into your project and fill it in. Claude will interview you.

FileWhat it does
blueprint/INDEX.mdContent catalog template. Maps every file in your OS.
blueprint/company/overview.mdWhat you sell, ICP, positioning, metrics
blueprint/company/team.mdRoster, org structure, communication norms
blueprint/company/accounts.mdKey accounts + CRM connection guide
blueprint/company/gtm-stack.mdYour tools, data flow, what's working and broken
blueprint/company/voice.mdBrand voice, tone, word swaps, writing rules
blueprint/company/design-system.mdColors, typography, visual style
blueprint/wiki/outbound-playbook.mdOutbound strategy, channels, campaign types
blueprint/wiki/onboarding.mdNew hire ramp plan and resources
blueprint/wiki/processes.mdRecurring SOPs and workflows
blueprint/hooks/safety-guard.shBlocks dangerous tool calls (PreToolUse)
blueprint/hooks/session-logger.shLogs every event to per-session JSONL files
blueprint/hooks/notify.shmacOS/Linux desktop notifications
blueprint/hooks/settings.jsonWires all hooks to lifecycle events
blueprint/hooks/setup-guide.mdFull hook documentation, customization guide
blueprint/skills/guide.mdHow to add and structure skill files
blueprint/archive/guide.mdWhat goes in the archive folder
blueprint/raw/guide.mdHow to dump and process raw inputs

gtm-skills/ - 5 starter skills

FileWhat it does
gtm-skills/outbound-copywriter.mdCold email sequences using the SPARK framework
gtm-skills/linkedin-post-writer.mdLinkedIn posts in your voice with scoring rubric
gtm-skills/icp-modeller.mdTiered ICP matrix with firmographic/psychographic/behavioral scoring
gtm-skills/gtm-strategist.mdGTM motion design, stack planning, budget allocation
gtm-skills/discovery-prep.mdPre-call research briefs and conversation prep
gtm-skills/guide.mdHow to add, customize, and create new skills

plugin/ - Workflows Engineering Plugin

Bundled locally in this repo (not an external install). Copy to your project to get structured workflow commands.

FileWhat it does
plugin/.claude-plugin/plugin.jsonPlugin manifest
plugin/commands/workflows/plan.mdStructured implementation planning
plugin/commands/workflows/work.mdStep-by-step plan execution with QA
plugin/commands/workflows/review.mdMulti-agent code and work review
plugin/commands/workflows/swarm.mdFull pipeline with parallel agents
plugin/commands/workflows/brainstorm.mdRequirement exploration before planning
plugin/commands/workflows/compound.mdDocument solved problems for team knowledge

Quick Start

Option A: Terminal

# 1. Clone
git clone https://github.com/Workflowsio/company-os-starter-kit.git
cd company-os-starter-kit

# 2. Copy blueprint to your project
cp -r blueprint/ /path/to/your-project/
cp CLAUDE.md /path/to/your-project/CLAUDE.md

# 3. Copy skills
cp -r gtm-skills/ /path/to/your-project/gtm-skills/

# 4. Copy plugin (optional - adds /workflows commands)
cp -r plugin/ /path/to/your-project/.claude/plugins/company-os/

# 5. Install hooks
mkdir -p /path/to/your-project/.claude/hooks
cp blueprint/hooks/*.sh /path/to/your-project/.claude/hooks/
cp blueprint/hooks/settings.json /path/to/your-project/.claude/settings.json
chmod +x /path/to/your-project/.claude/hooks/*.sh

# 6. Open your project in Claude Code and go

Option B: Just ask Claude

Open your project in Claude Code and say:

Read the CLAUDE.md and all the files in this repo.
Interview me about my business and help me
fill everything in. Go section by section.

Claude will:

  • Walk through each section of CLAUDE.md
  • Ask about your company, tools, team, and processes
  • Fill in every {{placeholder}} based on your answers
  • Adapt the structure to your business type
  • Suggest your first custom skill when done

No manual markdown editing required.


The 5 Skills

Skills are reusable instruction sets that tell Claude HOW to do specific tasks. Each includes frameworks, step-by-step instructions, anti-patterns, and quality checks.

SkillWhat it doesExample prompt
Outbound CopywriterCold email sequences using the SPARK framework, 7 power patterns, 6 archetypesWrite a 3-step sequence for VP Sales at mid-market SaaS
LinkedIn Post WriterLinkedIn posts in your voice with hook formulas, formatting rules, scoring rubricWrite a LinkedIn post about why most outbound fails
ICP ModellerTiered ICP matrix with firmographic, psychographic, and behavioral scoringBuild an ICP for our new product targeting fintech
GTM StrategistGTM motion design, tool selection, channel strategy, budget allocationDesign a GTM motion for our Series A launch
Discovery PrepPre-call research briefs with pain hypotheses, talking points, objection handlingPrep me for a call with the VP Marketing at Acme Corp

These five are GTM-focused starters. The skill format works for any domain. Create skills for engineering, support, finance, HR, product - whatever your team does.


The Blueprint

The blueprint/ folder is the recommended structure for your Company OS. Copy it to your project and fill it in.

FolderPurpose
company/Core context that rarely changes. Identity, team, brand, stack. Start here.
wiki/Reference docs, playbooks, SOPs. Things your team looks up. Grows over time.
hooks/Safety guard, session logger, notifications. Set up once, forget about it.
skills/Skill file templates. Copy starter skills from gtm-skills/ and add your own.
archive/Completed projects, old docs. Kept for reference but not loaded by default.
raw/Unprocessed inputs. Call transcripts, data exports, articles. Let Claude organize them into wiki/ pages.

Start with CLAUDE.md + company/overview.md. Add more as you go. A Company OS with 5 solid files beats one with 50 scattered files.


Philosophy

Why GitHub? Version control. Branching. Diffs. Pull requests. Your AI context should be managed with the same rigor as your code. When something breaks, you can revert. When someone joins, they clone and go.

Why markdown? It is the universal format. Every AI tool reads it. Every developer knows it. No vendor lock-in. No proprietary format. Move it to any system at any time.

Why this structure? CLAUDE.md is the hub. Brain files are the spokes. Skills are the playbooks. Hooks are the guardrails. Each piece has one job. Add what you need, skip what you don't.

AI-agnostic. The architecture works with Claude Code today. The files are plain markdown. If you switch tools tomorrow, the context transfers. The skills transfer. Only the hooks are Claude Code-specific.

Multiplayer. Share the repo with your team. Everyone gets the same context. Skills compound across sessions. Brain files stay current through commits. This is how AI context scales past one person.


Credits

Built by Dan Rosenthal at workflows.io.

The Workflows Engineering Plugin is built on top of Compound Engineering by EveryInc. The core workflow commands (plan, work, review, swarm, brainstorm) come from their excellent open-source foundation.


Follow me on LinkedIn for more on building with AI, GTM systems, and context engineering. I post about what we're building at workflows.io and share the frameworks behind it.

Star this repo if you found it useful.

Files in the repo

Repository payload8 top-level entries
  • blueprint
  • gtm-skills
  • plugin
  • .gitignore
  • CLAUDE.md
  • LICENSE
  • PLUGIN-GUIDE.md
  • README.md

Discussion (0)

Ask about usage, or say what you built with it

Sign in to join the discussion.

No comments yet. Be the first to say what this is good for.

More templates

CopilotKit/
OpenBot

Open-source AI coworkers that each get a computer of their own: a browser, files and tools, with every action decided before it happens and recorded after. Bring any AG-UI agent.

4.6k
Donchitos/
Claude-Code-Game-Studios

Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.

25k

A self-organizing Obsidian vault that gives AI coding agents persistent memory. Claude Code, Codex CLI, Gemini CLI.

4.6k
idavidov13/
agentic-playwright

Production-grade Playwright + TypeScript Scaffold for Agentic Testing. Harness for all major AI coding agents baked in.

163
gavishap/
omnia-vault

Omnia Vault - the all-in-one project brain: an Obsidian LLM wiki, Graphify code graphs, a living plan that triages new videos against itself, and a Claude Code ⇄ Codex relay. Everything your project knows, in one clonable vault.

60

🎬 Tạo video "so sánh kiến thức" ngắn tự động — HyperFrames + AI voice, 1 template nhiều chủ đề.

169