ceos-l10
Use when running or reviewing a Level 10 weekly leadership meeting
bradfeld · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add bradfeld/ceos --skill ceos-l10技能说明
name: ceos-l10 description: Use when running or reviewing a Level 10 weekly leadership meeting file-access: [data/meetings/l10/, templates/l10-meeting.md, data/scorecard/weeks/, data/rocks/, data/issues/open/, data/accountability.md] tools-used: [Read, Write, Glob]
ceos-l10
Facilitate the Level 10 (L10) Meeting — the weekly 90-minute leadership meeting that keeps the team aligned, accountable, and solving problems. The L10 follows a strict 7-section agenda with time boxes.
When to Use
- "Run L10" or "start our L10"
- "Level 10 meeting" or "weekly meeting"
- "Start our meeting" or "let's do our weekly"
- "Review last week's L10" or "what were our to-dos?"
- Any weekly leadership team meeting
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 |
|---|---|
data/meetings/l10/YYYY-MM-DD.md | L10 meeting notes |
data/scorecard/weeks/ | Latest scorecard (pulled during Scorecard section) |
data/rocks/[quarter]/ | Current Rocks (pulled during Rock Review) |
data/issues/open/ | Open issues (surfaced during IDS section) |
data/meetings/l10/ | Previous L10s (for To-Do review) |
templates/l10-meeting.md | Meeting template |
data/accountability.md | Accountability Chart (seat owners for To-Do assignment validation) |
Meeting Structure (90 minutes)
| # | Section | Time | Purpose |
|---|---|---|---|
| 1 | Segue | 5 min | Personal/professional good news |
| 2 | Scorecard | 5 min | Review weekly numbers |
| 3 | Rock Review | 5 min | Status of quarterly Rocks |
| 4 | Headlines | 5 min | Customer and employee news |
| 5 | To-Do Review | 5 min | Check last week's To-Dos |
| 6 | IDS | 60 min | Identify, Discuss, Solve top issues |
| 7 | Conclude | 5 min | New To-Dos, cascading messages, rating |
Process
Step 1: Set Up the Meeting
- Date: Use today's date, or ask if scheduling for a different day.
- Attendees: Ask who's attending. Default to the attendees from the most recent L10 if available.
- Create the meeting file from
templates/l10-meeting.mdatdata/meetings/l10/YYYY-MM-DD.md.
If an L10 already exists for today, ask: "There's already an L10 for today. Open it, or create a new one?"
Step 2: Segue (5 minutes)
Prompt each attendee to share one personal and one professional good news. This builds connection before diving into business.
Record responses in the Segue section.
"Let's start with a segue. [Name], share one personal and one professional good news."
Step 3: Scorecard Review (5 minutes)
- Read the most recent weekly scorecard from
data/scorecard/weeks/. - Display the metrics table with status.
- For each off-track metric, note it for the Issues list.
Scorecard — Week 07:
Weekly Revenue: $52K (goal: $50K) ✓
New Customers: 7 (goal: 10) ✗ → add to Issues?
NPS: 72 (goal: 70) ✓
Ask: "Any off-track items to add to today's Issues list?"
If no scorecard exists for this week: "No scorecard logged for this week yet. Skip, or enter numbers now?"
Step 4: Rock Review (5 minutes)
- Read all Rocks in
data/rocks/[current-quarter]/. - Display status for each Rock.
- Quick check — on track or off track? No discussion yet (save that for IDS).
Rock Review — Q1 2026:
Launch Beta (brad): on_track
Hire VP Sales (daniel): off_track → add to Issues?
Implement CRM (daniel): on_track
Ask: "Any off-track Rocks to add to today's Issues list?"
Step 5: Headlines (5 minutes)
Prompt for customer and employee headlines — good news, bad news, updates. Quick hits only. No discussion.
"What headlines do we need to share? Customer news, employee news, anything the team should know."
Record as bullet points.
Step 6: To-Do Review (5 minutes)
- Read the most recent previous L10 from
data/meetings/l10/. - Find the "New To-Dos" table from the Conclude section.
- For each To-Do, ask: "Done or not done?"
To-Do Review (from L10 2026-02-06):
☐ Send proposal to Acme (brad) — Done? [yes/no]
☐ Schedule interviews (daniel) — Done? [yes/no]
- Calculate completion rate. Target is 90%+.
- If below 90%, note it but don't dwell — it's data, not a guilt trip.
Step 7: IDS (60 minutes)
This is the core of the L10 — where the real work happens.
Step 7a: Build the Issues List
Collect issues from:
- Off-track Scorecard items (from Step 3)
- Off-track Rocks (from Step 4)
- Open issues from
data/issues/open/ - New issues raised by attendees
Ask: "What other issues should we add to today's list?"
Step 7b: Prioritize
List all issues and ask the team to pick the top 3 most important ones. These get solved today. The rest stay on the list for next week.
Step 7c: IDS Each Issue
For each of the top 3 issues, follow the IDS process:
- Identify — What is the real issue? Dig past symptoms. Use the 5 Whys if the root cause isn't obvious.
- Discuss — Each person shares their perspective. Stay focused — no tangents, no solving yet.
- Solve — What's the action? Create at least one To-Do with an owner and due date. Cross-reference
data/accountability.mdto validate that the To-Do owner matches the seat responsible for that area.
Record the IDS work in the meeting notes. If this creates a new issue file, use ceos-ids or write to data/issues/open/ directly.
Step 8: Conclude (5 minutes)
New To-Dos
Compile all To-Dos created during the meeting (from IDS and any other sections):
| To-Do | Owner | Due Date |
|---|