القائمة
Use when assessing organizational health across the Six Key Components with the EOS Organizational Checkup
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints
Use when running or reviewing a Level 10 weekly leadership meeting
Use when analyzing EOS health trends over time - Rock completion rates, scorecard consistency, checkup progression, and issue resolution patterns
Use when setting, tracking, or scoring quarterly Rocks
Use when defining metrics, logging weekly scorecard numbers, or analyzing trends
Use when taking a Clarity Break — stepping back from day-to-day work for strategic thinking time
استنادا إلى تصنيف SOC المهني
| name | ceos-checkup |
| description | Use when assessing organizational health across the Six Key Components with the EOS Organizational Checkup |
| file-access | ["data/checkups/","templates/checkup.md","data/vision.md","data/accountability.md","data/rocks/","data/scorecard/","data/people/","data/issues/"] |
| tools-used | ["Read","Write","Glob"] |
Measure organizational health using the standard EOS Organizational Checkup — a 20-question assessment across the Six Key Components (Vision, People, Data, Issues, Process, Traction). Each leadership team member rates the organization 1-5 on each question, and scores are calculated per component and overall. Use quarterly or semi-annually to track progress and surface alignment gaps.
Not for: Individual team member evaluation (use ceos-people), V/TO refresh (use ceos-annual), or quarterly Rock setting (use ceos-quarterly-planning).
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.
| File | Purpose |
|---|---|
data/checkups/ | Checkup result files (one per session, dated) |
templates/checkup.md | Template for new checkup files |
data/vision.md | V/TO — Core Values, Core Focus, targets (read-only) |
data/accountability.md | Accountability Chart — team structure and seats (read-only) |
data/rocks/ | Quarterly Rocks for Traction context (read-only) |
data/scorecard/ | Weekly metrics for Data context (read-only) |
data/people/ | People evaluations for People context (read-only) |
data/issues/ | Open/resolved issues for Issues context (read-only) |
Each checkup is stored at data/checkups/YYYY-MM-DD.md with YAML frontmatter:
date: "2026-02-15"
participants:
- name: "Brad Feld"
ratings: [5, 4, 5, 4, 3, 4, 3, 4, 5, 4, 5, 4, 4, 5, 4, 3, 4, 5, 4, 3]
- name: "Sarah Chen"
ratings: [4, 5, 4, 5, 4, 3, 4, 5, 4, 5, 4, 5, 5, 4, 5, 4, 3, 4, 5, 4]
status: complete # in_progress | complete
overall_score: 4.2
component_scores:
vision: 4.3
people: 4.1
data: 4.0
issues: 4.5
process: 3.5
traction: 4.3
Ratings array: 20 integers (1-5), indexed by question number (index 0 = Question 1, index 19 = Question 20). Use null for unanswered questions.
The EOS Organizational Checkup uses these 20 canonical questions, grouped by the Six Key Components:
| # | Question |
|---|---|
| 1 | We have a clear vision in writing that has been properly communicated and is shared by everyone in the company. |
| 2 | Our core values are clear, and we are hiring, reviewing, rewarding, and firing around them. |
| 3 | Our Core Focus (core business) is clear, and we keep our people, systems and processes aligned and focused on it. |
| 4 | Our 10-Year Target (big, long-range business goal) is clear, communicated regularly, and is shared by all. |
| 5 | Our target market (definition of our ideal customer) is clear, and all of our marketing and sales efforts are focused on it. |
| 6 | Our 3 Uniques (differentiators) are clear, and all of our marketing and sales efforts communicate them. |
| # | Question |
|---|---|
| 7 | We have a proven process for doing business with our customers. It has been named and visually illustrated, and all of our salespeople use it. |
| 8 | All of the people in our organization are the "right people" (they fit our culture and share our core values). |
| 9 | Our Accountability Chart (organizational chart that includes roles/responsibilities) is clear, complete, and constantly updated. |
| 10 | Everyone is in the "right seat" (they "get it, want it, and have the capacity to do their jobs well"). |
| # | Question |
|---|---|
| 11 | Our leadership team is open and honest, and demonstrates a high level of trust. |
| 12 | All teams clearly identify, discuss, and solve issues for the long-term greater good of the company. |
| # | Question |
|---|---|
| 13 | Everyone has Rocks (1 to 7 priorities per quarter) and is focused on them. |
| 14 | Everyone is engaged in a regular Meeting Pulse (weekly, quarterly, annually). |
| 15 | All meetings are on the same day and at the same time, have the same agenda, start on time, and end on time. |
| # | Question |
|---|---|
| 16 | Our Core Processes are documented, simplified, and followed by all to consistently produce the results we want. |
| # | Question |
|---|---|
| 17 | We have systems for receiving regular feedback from customers and employees, so we always know their level of satisfaction. |
| 18 | A Scorecard for tracking weekly metrics/measurables is in place. |
| 19 | Everyone in the organization has at least one number they are accountable for keeping on track each week. |
| 20 | We have a budget and are monitoring it regularly (e.g., monthly or quarterly). |
| Rating | Meaning |
|---|---|
| 5 | Strongly agree — this is firmly in place |
| 4 | Agree — mostly in place, minor gaps |
| 3 | Neutral — partially in place, needs work |
| 2 | Disagree — significant gaps exist |
| 1 | Strongly disagree — not in place at all |
Each component score is the average of its questions across all participants:
| Component | Questions | Count |
|---|---|---|
| Vision | 1-6 | 6 |
| People | 7-10 | 4 |
| Issues | 11-12 | 2 |
| Traction | 13-15 | 3 |
| Process | 16 | 1 |
| Data | 17-20 | 4 |
Overall score = average of all 20 questions across all participants.
Interpretation:
| Score | Rating | Action |
|---|---|---|
| 4.0-5.0 | Strong | Maintain — this component is working |
| 3.0-3.9 | Needs attention | Discuss at L10 — identify specific gaps |
| < 3.0 | Weak | IDS priority — create issues for action plans |
Use when conducting a new Organizational Checkup session with the leadership team.
Ask for:
YYYY-MM-DD).data/accountability.md to suggest team members. Ask: "Who is participating? (Default: everyone on the Accountability Chart)"If data/accountability.md doesn't exist or is empty, ask the user to list participants manually.
Check if data/checkups/YYYY-MM-DD.md already exists for today's date.
status: complete: "A checkup already exists for [date]. Open it to review, or create a new session?"status: in_progress: "An incomplete checkup exists for [date]. Resume where you left off, or start fresh?"Before starting questions, briefly review available CEOS data for context:
data/vision.md for Core Values and 1-Year Plan (Vision context)data/rocks/ for current quarter's Rocks (Traction context)data/scorecard/metrics.md for active metrics (Data context)data/issues/open/ for open issues count (Issues context)Display a brief context summary:
Context for Today's Checkup
━━━━━━━━━━━━━━━━━━━━━━━━━━
Core Values: [list from vision.md]
Current Rocks: [count] for [quarter]
Active Metrics: [count] on Scorecard
Open Issues: [count]
If any data source is missing, note it and continue. The checkup doesn't require these — they provide context.
Present the 20 questions organized by component. For each component:
Collection approach: Present all questions for one component at a time. For each question, collect ratings from all participants before moving to the next question.
Example interaction:
VISION — Question 1 of 6
"We have a clear vision in writing that has been properly communicated
and is shared by everyone in the company."
Rate 1-5 (1=strongly disagree, 5=strongly agree):
Brad: [rating]
Sarah: [rating]
After each component, display the component subtotal:
Vision Complete — Component Average: 4.2
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Brad avg: 4.3
Sarah avg: 4.0
Progress tracking: Show progress after each component:
Progress: 2/6 components [████████░░░░░░░░░░░░] 33%
Vision: 4.2 | People: 3.8 | Data: — | Issues: — | Process: — | Traction: —
After all 20 questions are rated:
If overall score < 2.5: Display warning: "Overall score below 2.5/5. Consider a focused IDS session to identify root causes across multiple components."
For each component scoring below 3.5, ask: "Any specific action items for [Component]?"
Suggest relevant CEOS skills for low-scoring components:
| Component | Score < 3.0 | Suggested Skill |
|---|---|---|
| Vision | Low | "Consider running ceos-vto to refresh the Vision/Traction Organizer" |
| People | Low | "Consider running ceos-people to evaluate right people, right seats" |
| Data | Low | "Consider reviewing ceos-scorecard to strengthen weekly metrics" |
| Issues | Low | "Consider running ceos-ids to process the open issues list" |
| Process | Low | "Consider running ceos-process to document core processes" |
| Traction | Low | "Consider reviewing ceos-rocks for Rock focus and ceos-l10 for meeting discipline" |
Build the file from templates/checkup.md:
{{date}} with the session date{{participants}} with participant namesstatus: completeShow the complete file before writing. Ask: "Save this checkup?"
Write to data/checkups/YYYY-MM-DD.md.
Use when reviewing historical checkup results and tracking trends over time.
Read all files from data/checkups/. Parse YAML frontmatter for each.
If no files exist: "No checkups found. Run your first Organizational Checkup to establish a baseline."
Sort by date (most recent first).
Organizational Checkup History
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| Date | Participants | Overall | Vision | People | Data | Issues | Process | Traction | Status |
|------------|-------------|---------|--------|--------|------|--------|---------|----------|--------|
| 2026-02-15 | 3 | 4.2 | 4.3 | 4.1 | 4.0 | 4.5 | 3.5 | 4.3 | ✓ |
| 2025-11-10 | 3 | 3.8 | 4.0 | 3.5 | 3.2 | 4.0 | 3.0 | 3.8 | ✓ |
| 2025-08-01 | 2 | 3.2 | 3.5 | 3.0 | 2.8 | 3.5 | 2.5 | 3.2 | ✓ |
For each component, show direction vs. the previous checkup:
Trend Analysis (Latest vs Previous)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
| Component | Previous | Current | Change | Trend |
|-----------|----------|---------|--------|-------|
| Vision | 4.0 | 4.3 | +0.3 | ↑ |
| People | 3.5 | 4.1 | +0.6 | ↑↑ |
| Data | 3.2 | 4.0 | +0.8 | ↑↑ |
| Issues | 4.0 | 4.5 | +0.5 | ↑ |
| Process | 3.0 | 3.5 | +0.5 | ↑ |
| Traction | 3.8 | 4.3 | +0.5 | ↑ |
| OVERALL | 3.8 | 4.2 | +0.4 | ↑ |
Trend indicators:
↑↑ = improved by 0.5+↑ = improved by 0.1-0.4→ = unchanged (within 0.1)↓ = declined by 0.1-0.4↓↓ = declined by 0.5+Calculate days since the most recent checkup. If > 120 days:
📅 Last checkup was [N] days ago (recommended: quarterly / every 90 days).
Consider running a new checkup to track progress.
Ask: "Want to drill into a specific checkup or component?"
If the user selects a checkup, display the full file with all participant ratings and action items.
If the user selects a component, show that component's score history across all checkups as a progression.
Use when analyzing alignment gaps between team members' ratings on a specific checkup.
Default to the most recent checkup. If multiple exist, ask: "Which checkup? (Default: most recent — [date])"
Load the selected checkup file and parse participant ratings.
If the checkup has only one participant: "Alignment analysis requires 2+ participants. This checkup has only one. Run a new checkup with multiple team members, or select a different checkup."
For each of the 20 questions, calculate across all participants:
Flag questions where the team diverges significantly:
Sort by range (highest first) to surface the biggest gaps.
Alignment Analysis — [Date] Checkup
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Participants: Brad, Sarah, Mike
HIGH VARIANCE (Range >= 3) — Discuss These
| # | Question (abbreviated) | Brad | Sarah | Mike | Avg | Range | Flag |
|---|------------------------------|------|-------|------|-----|-------|------|
| 7 | Proven customer process | 5 | 2 | 3 | 3.3 | 3 | 🔴 |
| 16| Core Processes documented | 4 | 1 | 3 | 2.7 | 3 | 🔴 |
MODERATE VARIANCE (Range = 2)
| # | Question (abbreviated) | Brad | Sarah | Mike | Avg | Range | Flag |
|---|------------------------------|------|-------|------|-----|-------|------|
| 3 | Core Focus clear | 5 | 3 | 4 | 4.0 | 2 | ⚠️ |
ALIGNED (Range <= 1)
| # | Question (abbreviated) | Brad | Sarah | Mike | Avg | Range |
|---|------------------------------|------|-------|------|-----|-------|
| 1 | Clear vision in writing | 5 | 5 | 4 | 4.7 | 1 |
| 11| Leadership team trust | 5 | 4 | 5 | 4.7 | 1 |
| ... (remaining aligned questions)
Alignment Summary
━━━━━━━━━━━━━━━━
High variance (Range >= 3): 2 questions — need team discussion
Moderate variance (Range 2): 1 question — worth reviewing
Aligned (Range <= 1): 17 questions — team consensus
Top Discussion Topics:
1. Q7: "Proven customer process" — Range 3 (Brad: 5, Sarah: 2)
→ Team sees this very differently. Discuss what "proven process" means.
2. Q16: "Core Processes documented" — Range 3 (Sarah: 1, Brad: 4)
→ Consider running ceos-process to document core processes.
Ask: "Want to discuss any specific question or create issues from these gaps?"
If the user wants to create issues, suggest using ceos-ids with the specific gap as the issue topic.
null and note it. Don't silently omit questions.data/vision.md — Core Values, Core Focus, 10-Year Target, 1-Year Plandata/accountability.md — seats and ownersdata/rocks/ — current quarter's Rocksdata/scorecard/ — metrics and weekly entriesdata/people/ — person evaluationsdata/issues/open/ and data/issues/resolved/ceos-ids.data/annual/ — annual planning recordsceos-checkup can be referenced during annual planning to track year-over-year progress.data/quarterly/ — quarterly planning recordsOnly ceos-checkup writes to data/checkups/. Other skills (particularly ceos-annual and ceos-quarterly-planning) may read checkup data for trend analysis and planning context, but they do not create or modify checkup files.