/ceos-kickoff

name: ceos-kickoff
description: Use when conducting Focus Day, Vision Building Day 1, or Vision Building Day 2 — the EOS implementation kickoff sequence
file-access: [data/meetings/kickoff/, templates/focus-day.md, templates/vb-day-1.md, templates/vb-day-2.md, data/vision.md, data/rocks/, data/scorecard/, data/issues/, data/accountability.md]
tools-used: [Read, Write, Glob]

ceos-kickoff

Facilitate the EOS implementation kickoff sequence — the three foundational sessions where a leadership team first implements EOS. Focus Day introduces the tools and establishes the foundation. Vision Building Day 1 defines the Vision component (Core Values, Core Focus, 10-Year Target, Marketing Strategy). Vision Building Day 2 completes the V/TO (3-Year Picture, 1-Year Plan, Rocks, Issues List). These are one-time sessions, distinct from the recurring L10 or quarterly/annual planning cycles.

When to Use

• "Focus Day" or "run our Focus Day"
• "Vision Building Day" or "VB Day 1" or "VB Day 2"
• "Start EOS" or "implement EOS" or "kick off EOS"
• "First EOS session" or "EOS implementation"
• "We're starting EOS — what's first?"
• Any reference to the initial EOS implementation sequence

Context

Finding the CEOS Repository

Search upward from the current directory for the `.ceos` marker file. This file marks the root of the CEOS repository.

If `.ceos` is not found, stop and tell the user: "Not in a CEOS repository. Clone your CEOS repo and run setup.sh first."

**Sync before use:** Once you find the CEOS root, run `git -C <ceos_root> pull --ff-only --quiet 2>/dev/null` to get the latest data from teammates. If it fails (conflict or offline), continue silently with local data.

Key Files

| File | Purpose | |------|---------| | `templates/focus-day.md` | Focus Day session template | | `templates/vb-day-1.md` | Vision Building Day 1 template | | `templates/vb-day-2.md` | Vision Building Day 2 template | | `data/meetings/kickoff/` | Saved kickoff session files | | `data/vision.md` | Current V/TO (read-only — use `ceos-vto` to modify) | | `data/accountability.md` | Accountability Chart (read-only — use `ceos-accountability` to modify) | | `data/rocks/` | Rock files (read-only — use `ceos-rocks` to create) | | `data/scorecard/` | Scorecard data (read-only — use `ceos-scorecard` to update) | | `data/issues/open/` | Open issues (read-only — use `ceos-ids` to manage) |

Kickoff Sequence

The EOS implementation follows a specific cadence:

1. **Focus Day** — Day 1. Introduces all EOS tools, creates initial drafts. Typically a full-day session. 2. **Vision Building Day 1** — ~30 days later. Deep dive into the Vision component. Half to full day. 3. **Vision Building Day 2** — ~30 days after VB Day 1. Completes the V/TO, sets first formal Rocks. Half to full day.

After all three sessions, the company transitions into the regular EOS rhythm: weekly L10s, quarterly planning, annual planning.

File Naming

• `focus-day-YYYY-MM-DD.md` — Focus Day session
• `vb-day-1-YYYY-MM-DD.md` — Vision Building Day 1
• `vb-day-2-YYYY-MM-DD.md` — Vision Building Day 2

All files are saved in `data/meetings/kickoff/`.

Process

This skill has three modes. Ask which session the user wants to run.

---

Mode 1: Focus Day

*The first full-day session when starting EOS.*

1. Setup

1. Ask for the date (default: today) and attendees. 2. Check for existing Focus Day files: `glob data/meetings/kickoff/focus-day-*.md`.

• If found, ask: "A Focus Day session already exists ([date]). Open to review, append notes, or start fresh?"

3. Check for existing V/TO: `read data/vision.md`.

• If populated, note: "V/TO already has content. Focus Day typically runs when first starting EOS. Continue anyway?"

4. Read the template: `read templates/focus-day.md`. 5. Replace placeholders (date, attendees) and start the session.

2. Welcome & EOS Overview

Walk through the Six Key Components of EOS:

• **Vision** — Get everyone on the same page
• **People** — Right people, right seats
• **Data** — Manage by a Scorecard, not feelings
• **Issues** — IDS (Identify, Discuss, Solve)
• **Process** — Document the core processes
• **Traction** — Rocks + Meeting Pulse

Capture team expectations and commitment notes.

3. V/TO Introduction

This is a first pass — capture initial thoughts, not final decisions:

• Core Values brainstorm (3-7 candidates)
• Core Focus first draft (Purpose + Niche)
• 10-Year Target initial idea

Note: "These will be refined and finalized in Vision Building Days 1 and 2."

4. Accountability Chart Draft

Guide the team through building the initial org structure: 1. Define major functions (seats) — focus on the structure, not the people 2. Assign 5 key roles per seat 3. Place people into seats — mark where "Right Person, Right Seat" evaluation is needed

If `data/accountability.md` already exists, read it and build on it.

5. Initial Rocks Brainstorm

Brainstorm priorities for the current quarter: 1. Ask: "What quarter are we in?" (set the {{quarter}} placeholder) 2. Brainstorm 10-20 Rock candidates 3. Narrow to company's top 3-7 4. Assign owners

Note: "These Rocks are preliminary. They'll be formalized in VB Day 2 after the full vision is set."

6. Scorecard Discussion

Introduce the weekly Scorecard concept: 1. Explain: "5-15 numbers that tell the health of your business at a glance" 2. Brainstorm initial metrics 3. Assign owners and set weekly goals

7. L10 Preview

Introduce the Level 10 Meeting format: 1. Walk through the 7-section L10 agenda (5-5-5-5-5-60-5 minutes) 2. Schedule the first L10 meeting (day, time, location)

8. Conclude & Save

1. Summarize key outcomes from each section. 2. Set dates for Vision Building Day 1 (~30 days) and Vision Building Day 2 (~60 days). 3. Capture immediate action items. 4. Show the complete file and get approval. 5. Save to `data/meetings/kickoff/focus-day-YYYY-MM-DD.md`.

Suggest: "Use `ceos-accountability` to formalize t