/ Free · Open Source · MIT

Build Your AI Chief of Staff

An opinionated framework for building your own AI operating partner using Claude Code. Drop the folder, start a conversation, and 30 minutes from now you'll have an AI that remembers who you are, what matters, and what you're building.

Get the Starter (Free) → See how it works
No credit card · No signup · Works with Claude Code Desktop
/ Context, not prompts

LLMs are only as good as the context you load.

Claude, ChatGPT, every model — they all need to know who you are, what matters, and how you work. This framework is the structure: identity, strategy, operations, memory. Drop the folder once, and Claude reads it at the start of every conversation.

/ Built for non-coders

You don't need to be technical.

No terminal. No code. You install Claude Code Desktop (a chat app), drop the folder in, and start talking. Claude fills in the markdown files for you based on your conversations. If you can text a colleague, you can run this.

The growth path — start at Layer 1, expand as you go. Click each layer to expand.
1
Foundation Start Here — Personal CoS, just for you
+

Your AI Chief of Staff knows who you are, your goals, your week, and the rituals that run your day. It reads your context at the start of every conversation and remembers what matters across sessions.

  • Identity layer (CLAUDE.md) — always loaded
  • Strategy layer (life plan, OKRs, Rocks, scorecard)
  • Memory that persists across all conversations
  • Six core slash commands (/day, /weekly-plan, /weekly-wrap-up, /debrief, /dashboard, /grow)
  • One MCP server connected (Notion or Calendar)
⏱ ~20 min to up & running 💰 Free · MIT licensed 🎯 For: anyone who wants an AI that actually knows them
2
Connected Up Next — All your services wired in
+

Your CoS becomes meaningfully more powerful with all your services connected. Slack posts daily summaries, Fireflies transcripts become tasks, Apollo enriches your network, the dashboard updates from real data.

  • 6–8 MCP servers (Notion, Slack, Calendar, Fireflies, Apollo, Drive, Gmail, etc.)
  • Custom slash commands tailored to your workflow
  • Daily Slack auto-posts with your morning dashboard
  • /debrief turns every call into action items
  • Visual dashboard.html with your real data
⏱ 1–2 weeks DIY 🎯 For: operators who want the full wedge
3
Team Future — Multi-seat with shared context
+

Every team member gets their own CoS, with shared team context (Rocks, scorecard, people DB) visible across the team. Your CoS isn't personal productivity anymore — it's an intelligence layer across the company.

  • Multi-seat CoS instances
  • Shared team context (Rocks, scorecard, people)
  • Cross-CoS commands (team-pulse, cascade-check)
  • Role-based memory (CEO's CoS thinks like a CEO)
⏱ 2–6 weeks rollout 🎯 For: 3–15 person companies
4
Systemic Future — Company data flows into the CoS
+

Connect your company systems. Your CoS becomes a company OS — sees your CRM, finance data, support tickets, ops dashboards. Workflow automation kicks in across departments.

  • CRM integration (HubSpot, Salesforce, Pipedrive)
  • Finance data (QuickBooks, Stripe, banking)
  • Support tickets / ops dashboards
  • Custom data sources via API / n8n / Make
  • AI Client Brain — client-facing CoS extension
⏱ Ongoing — each integration 2–6 weeks 🎯 For: companies wanting an AI that sees everything
5
Engine Future — Your entire company running on AI
+

Your CoS stops being a system of intelligence and becomes a system of action. AI agents execute, not just inform — running outreach, managing pipeline, drafting client work, monitoring systems.

  • AI agents that act on your data
  • Multi-system automation across departments
  • Customer/client-facing AI workflows
  • Continuous learning across the company
  • Every Layer 1–4 capability integrated
⏱ 6+ months to reach meaningful depth 🎯 For: companies serious about an AI operating layer
/ Why this exists

A Chief of Staff isn't a chatbot.

Most people try to use ChatGPT or Claude as their assistant. It doesn't stick — because every conversation starts from zero. A real chief of staff remembers, anticipates, and pushes back.

Default Chatbot
  • Forgets every conversation
  • Asks "what do you want?" every time
  • Just one tool, no integrations
  • Pure conversation, no rituals
  • Generic answers, no point of view
  • You re-explain who you are every session
Your AI Chief of Staff
  • Persistent memory across conversations
  • Knows your role, business, week, priorities
  • Connected to your tools (Notion, Calendar, Slack, etc.)
  • Repeatable rituals (/day, /week, /debrief)
  • Coaches you — pushes back when you drift
  • Gets sharper over time
/ The mental model

Four layers that make it work.

Every working AI CoS has these four layers. The starter gives you all four out of the box.

LAYER 1

Identity

Who you are. How you work. What you care about. Loaded at the start of every conversation.

CLAUDE.md
LAYER 2

Strategy

What matters. Your life plan, annual OKRs, quarterly Rocks, business V/TOs.

context/life-plan.md, rocks.md, annual-plan.md
LAYER 3

Operations

How you run day-to-day. Weekly scorecard, slash commands, time blocks, rituals.

context/scorecard.md, .claude/commands/*
LAYER 4

Reflection

How you improve. Auto-managed memory + a durable history of every week.

memory/, history/
/ What you get

An entire CoS, in one folder.

Drop the folder into Claude Code Desktop, then talk. The whole framework loads in one read — Claude already knows what each file is for and walks you through filling them through conversation. 31 files, all open-source, all yours to edit.

31
Files
6
Slash Commands
5
Strategy Templates
1
Visual Dashboard
20 min
to up & running

You don't fill in forms. You have conversations.

Every template is built as instructions for Claude — what to ask, what good looks like, when to push back. Drop the folder, then talk to Claude the way you'd onboard a real chief of staff. Claude writes the files. Most operators have 3-5 setup conversations across their first week. None involve opening a markdown file.

"Hi! I'm setting up my AI Chief of Staff. Read the framework files in this project — they're set up but mostly empty. Then walk me through the first one."
/ Get started

Start free. Hop on a call if you get stuck.

Drop the starter on your machine and have your first conversation with Claude. If you hit a wall, I'll jump on a free 30-min call to help you get past it — operator to operator. No sales pressure.

The Starter

Free · MIT license

Drop the folder, start a conversation. Up & running in ~20 minutes.

  • Full open-source starter on GitHub
  • All 6 core slash commands
  • 5 strategy templates with embedded coaching
  • Visual dashboard
  • Setup runbook included
Get the Starter →

Get Unstuck

Free · 30 min with Brandon

Stuck somewhere? Want to see what's possible at deeper layers? Hop on a free 30-min call with me — Brandon, the guy who built this.

  • 30-min screen share, no sales pitch
  • I'll help unblock whatever's stuck
  • I'll show you what your CoS could become at Layers 2–5
  • If there's a deeper need, we can talk about that too
Book a Free Call →
Brandon Passley, Founder of Hyperedge AI

Hey, I'm Brandon.

I'm the founder of Hyperedge — we build AI operating systems for founder-led B2B agencies. I'm also co-founder of Outworks, an AI content operating system for B2B marketing teams.

I built this AI Chief of Staff for myself because running two companies, three clients, and a content engine was breaking the default tools. I've been running my own CoS daily for 6+ months — and I'm packaging the framework so other operators can run their own.

If you get stuck, book a free 30-min call with me. Operator to operator.

Hyperedge — AI operating systems for B2B agencies · Outworks — AI content operating systems · LinkedIn

Common Questions

Is this just ChatGPT with extra steps?

No, and this was built specifically for Claude Code, not ChatGPT. ChatGPT (and default Claude in the chat UI) is stateless — every conversation starts from zero. Claude Code is different: it reads the files in your project at the start of every conversation, persists memory across sessions, and connects to your tools through MCP. This framework gives Claude Code the structure to keep building context over time. It's the difference between a contractor you brief every time and a chief of staff who already knows everything about your business.

Do I need to be technical to use this?

No. You don't need to know how to code. You'll use Claude Code Desktop (a chat interface, not a terminal). You won't edit markdown files by hand — Claude does that for you based on the conversations you have. The setup is opinionated and works out of the box. If you hit a technical wall (like configuring a new tool), Claude walks you through it.

What does it cost to run?

The framework itself is free (MIT-licensed, open source). You'll pay for: a Claude subscription (or Anthropic API usage — typically $20-50/month at active use), and any third-party MCP integrations you add (most are free or have a free tier). Total monthly cost for a typical Layer 2 setup: ~$30-80.

Can my whole team use this?

Eventually, yes — that's Layer 3 of the growth path. Each team member gets their own CoS with shared team context (Rocks, scorecard, people DB visible across the team). For solo operators or founders, Layer 1-2 is the right starting point.

What if I want it built for me?

I'm happy to help. Hop on a free 30-min unstuck call with me and we'll talk through what that would look like. The starter gets you to Layer 1; if you want help reaching Layers 2–5 (full service integration, team rollout, custom data work), I can scope something tailored to your stack and goals.

How is my data handled?

Your data stays on your machine. Everything runs locally through Claude Code Desktop. The framework doesn't send your context anywhere except to Anthropic's API (which is required for Claude to work). No third party sees your information through this framework.

What if I get stuck or hate something?

Two paths: (1) Book a free 30-min Unstuck call with me — I'll help fix whatever's blocking you. (2) Just tell Claude Code to change it. "I don't like how /day works — make it shorter." "Add a section to CLAUDE.md for my coaching clients." Claude updates the files for you. Most operators reshape their CoS multiple times in the first month. That's the point.

/ The framework keeps evolving

New layers. New commands. New patterns.

An AI Chief of Staff isn't a one-time install — it's continuous context building. As I extend my own CoS (new MCP integrations, new slash commands, sharper coaching prompts, the Layer 2 → 5 drops), I send the updates out. Drop your email and you'll get them as they ship.

No spam · Unsubscribe anytime · Only when there's something worth sending

Ready to build yours?

Three steps. About 20 minutes. No code.

/ Step 01
Download the folder from GitHub.
/ Step 02
Point Claude Code Desktop at it.
/ Step 03
Start a conversation. Claude does the rest.
Get the Starter (Free) →