Back to Details

ceos-rocks

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

ceos-rocks

ceos-rocks

Manage quarterly Rocks — the 3-7 most important priorities for the next 90 days. Each Rock has one owner, a measurable outcome, and a due date at quarter end.
管理季度Rocks——即未来90天内3到7项最重要的优先级事项。每个Rock有唯一负责人、可衡量的成果，以及季度末的截止日期。

When to Use

适用场景

  • "Set rocks for this quarter" or "let's plan our quarterly priorities"
  • "Rock status" or "how are our rocks tracking?"
  • "Score rocks" or "end of quarter review"
  • "Create a rock" or "add a new rock for [person]"
  • "What rocks does [person] own?"
  • Any quarterly planning or review conversation
  • “设定本季度的Rocks”或“我们来规划季度优先级吧”
  • “Rock状态”或“我们的Rocks进度如何？”
  • “给Rocks评分”或“季度末复盘”
  • “创建一个Rock”或“给[某人]新增一个Rock”
  • “[某人]负责哪些Rocks？”
  • 任何季度规划或复盘对话

Context

上下文

Finding the CEOS Repository

查找CEOS仓库

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.
从当前目录向上搜索
.ceos
标记文件，该文件标记了CEOS仓库的根目录。
如果找不到
.ceos
，停止操作并告知用户：“不在CEOS仓库中。请克隆你的CEOS仓库并先运行setup.sh。”
使用前同步： 找到CEOS根目录后，运行
git -C <ceos_root> pull --ff-only --quiet 2>/dev/null
以获取团队成员的最新数据。如果运行失败（冲突或离线），静默使用本地数据继续操作。

Key Files

核心文件

FilePurpose
data/rocks/QUARTER/
Rock files for each quarter (e.g., 
data/rocks/2026-Q1/
)
data/vision.md
V/TO document (1-Year Plan for alignment checks)
templates/rock.md
Template for creating new Rock files
data/accountability.md
Accountability Chart (seat owners for Rock-owner alignment)
文件用途
data/rocks/QUARTER/
各季度的Rock文件（例如
data/rocks/2026-Q1/
）
data/vision.md
V/TO文档（用于对齐校验的1年规划）
templates/rock.md
创建新Rock文件的模板
data/accountability.md
责任分工表（用于Rock负责人对齐的岗位负责人表）

Rock File Format

Rock文件格式

Each Rock is a markdown file with YAML frontmatter:
yaml
id: rock-001
title: "Launch Beta Program"
owner: "brad"
quarter: "2026-Q1"
status: on_track       # on_track | off_track | complete | dropped
created: "2026-01-02"
due: "2026-03-31"
Status values:
  • on_track
    — progressing as expected
  • off_track
    — behind or at risk
  • complete
    — done (set during end-of-quarter scoring)
  • dropped
    — no longer a priority (set during end-of-quarter scoring)
File naming: 
rock-NNN-slug.md
where NNN is a zero-padded ID and slug is the title slugified (lowercase, hyphens, no special chars).
Milestones: Rocks support two milestone formats:
  • Structured (frontmatter): Array of milestone objects with 
    title
    , optional 
    due
    date, and 
    status
    (
    todo
    /
    in_progress
    /
    done
    ). Enables date-based progress tracking and overdue detection.
  • Markdown checklist (body): Traditional 
    - [ ]
    / 
    - [x]
    checklist items in the Milestones section. Simple and human-friendly.
Both are valid. Tracking mode prefers frontmatter milestones when present, falls back to markdown checklist parsing otherwise.
Attachments: Optional 
attachments
array in frontmatter references supporting documents. Each attachment has a 
path
(relative to CEOS root) and optional 
label
. The skill displays references but does not manage files.
每个Rock都是带有YAML前置元数据的markdown文件：
yaml
id: rock-001
title: "Launch Beta Program"
owner: "brad"
quarter: "2026-Q1"
status: on_track       # on_track | off_track | complete | dropped
created: "2026-01-02"
due: "2026-03-31"
状态值说明：
  • on_track
    — 进度符合预期
  • off_track
    — 进度落后或存在风险
  • complete
    — 已完成（季度末评分时设置）
  • dropped
    — 不再是优先级事项（季度末评分时设置）
文件命名规则： 
rock-NNN-slug.md
，其中NNN是补零的ID，slug是标题的 slug 化格式（小写、连字符分隔、无特殊字符）。
里程碑： Rocks支持两种里程碑格式：
  • 结构化（前置元数据）： 里程碑对象数组，包含
    title
    、可选
    due
    日期和
    status
    （
    todo
    /
    in_progress
    /
    done
    ）。支持基于日期的进度跟踪和逾期检测。
  • Markdown checklist（正文）： 里程碑部分使用传统的
    - [ ]
    / 
    - [x]
    checklist项，简单易读。
两种格式均有效。跟踪模式优先使用前置元数据中的里程碑，不存在时则回退到解析markdown checklist。
附件： 前置元数据中可选的
attachments
数组用于引用支撑文档，每个附件包含
path
（相对于CEOS根目录）和可选
label
。本技能仅展示引用，不管理文件。

Quarter Format

季度格式

Quarters follow 
YYYY-QN
format: 
2026-Q1
, 
2026-Q2
, 
2026-Q3
, 
2026-Q4
.
To determine the current quarter from today's date:
  • Jan-Mar = Q1, Apr-Jun = Q2, Jul-Sep = Q3, Oct-Dec = Q4
季度遵循
YYYY-QN
格式：
2026-Q1
、
2026-Q2
、
2026-Q3
、
2026-Q4
。
从当前日期判断所属季度的规则：
  • 1-3月 = Q1，4-6月 = Q2，7-9月 = Q3，10-12月 = Q4

Process

流程

Mode: Setting Rocks

模式：设定Rocks

Use when creating new Rocks at the start of a quarter.
用于季度初创建新Rocks时使用。

Step 1: Determine the Quarter

步骤1：确定季度

Check if the user specified a quarter. If not, use the current quarter. If creating Rocks for a past quarter, warn: "That quarter has already started/ended. Continue anyway?"
Create the quarter directory if it doesn't exist: 
data/rocks/YYYY-QN/
检查用户是否指定了季度，未指定则使用当前季度。如果为过去的季度创建Rocks，发出警告：“该季度已经开始/结束，是否仍要继续？”
如果季度目录不存在则创建：
data/rocks/YYYY-QN/

Step 2: Review Context

步骤2：回顾上下文

Before creating Rocks, read and briefly summarize:
  • The 1-Year Plan from 
    data/vision.md
    (what are we trying to achieve this year?)
  • Any existing Rocks for this quarter (avoid duplicates)
创建Rocks前，阅读并简要总结以下内容：
  • data/vision.md
    中的1年规划（我们今年要达成什么目标？）
  • 本季度已有的Rocks（避免重复）

Step 3: Walk Through Each Rock

步骤3：逐个完善Rock信息

For each Rock, collect:
  1. Title — short, specific description (e.g., "Launch Beta Program")
  2. Owner — one person (Rocks are never shared)
  3. Measurable outcome — what does "done" look like?
  4. Milestones — 2-4 checkpoints toward completion
  5. Structured milestones (optional) — Ask: "Add due dates to milestones?"
    • If yes, collect for each milestone: title, due date (
      YYYY-MM-DD
      ), status (default: 
      todo
      )
    • Store as 
      milestones
      array in frontmatter
    • If no, use markdown checklist only (traditional format)
    • If more than 7 milestones, warn: "EOS recommends 3-5 milestones per Rock. Are all of these essential checkpoints?"
  6. Attachments (optional) — Ask: "Any supporting documents to reference?"
    • If yes, collect: path (relative to CEOS root) and optional label for each
    • Store as 
      attachments
      array in frontmatter
为每个Rock收集以下信息：
  1. 标题 — 简短明确的描述（例如“启动Beta测试项目”）
  2. 负责人 — 唯一责任人（Rocks永远不共享）
  3. 可衡量成果 — “完成”的标准是什么？
  4. 里程碑 — 通往完成的2-4个检查点
  5. 结构化里程碑（可选） — 询问：“需要给里程碑添加截止日期吗？”
    • 若是，为每个里程碑收集：标题、截止日期（
      YYYY-MM-DD
      ）、状态（默认：
      todo
      ）
    • 存储为前置元数据中的
      milestones
      数组
    • 若否，仅使用markdown checklist（传统格式）
    • 如果里程碑超过7个，发出警告：“EOS建议每个Rock设置3-5个里程碑，所有这些检查点都是必需的吗？”
  6. 附件（可选） — 询问：“需要引用任何支撑文档吗？”
    • 若是，为每个附件收集：路径（相对于CEOS根目录）和可选标签
    • 存储为前置元数据中的
      attachments
      数组

Step 4: Validate

步骤4：校验

  • 3-7 Rocks per person. If someone has fewer than 3, ask if they should own more. If more than 7, flag: "Too many Rocks for [person]. EOS recommends 3-7. Which ones are the real priorities?"
  • Alignment check. Does each Rock connect to a 1-Year Plan goal? Flag any that don't.
  • Due date. Set to the last day of the quarter.
  • Seat alignment. Cross-reference Rock owners against 
    data/accountability.md
    . Flag mismatches if a Rock's subject area doesn't match the owner's seat responsibilities, for example: "This Rock falls under the [Seat] responsibilities. Should [Seat Owner] own it instead?"
  • 每人负责3-7个Rock。 如果某人负责的Rock少于3个，询问是否需要增加更多；如果超过7个，标记提示：“[某人]的Rocks数量过多，EOS建议3-7个，哪些是真正的优先级事项？”
  • 对齐校验。 每个Rock是否和1年规划目标相关？标记所有不相关的Rock。
  • 截止日期。 设置为季度最后一天。
  • 岗位对齐。 将Rock负责人与
    data/accountability.md
    交叉校验，如果Rock的所属领域和负责人的岗位职责不匹配则标记提示，例如：“该Rock属于[岗位]的职责范围，是否应该由[岗位负责人]来负责？”

Step 5: Generate the ID

步骤5：生成ID

Read existing Rock files in the quarter directory. Find the highest 
rock-NNN
ID and increment. If no files exist, start at 
rock-001
.
读取季度目录下已有的Rock文件，找到最大的
rock-NNN
ID并递增。如果没有文件，从
rock-001
开始。

Step 6: Write the File

步骤6：写入文件

Use 
templates/rock.md
as the template. Substitute:
  • Frontmatter fields (id, title, owner, quarter, status=on_track, created=today, due=quarter-end)
  • Body sections (measurable outcome, milestones)
Write to 
data/rocks/YYYY-QN/rock-NNN-slug.md
.
Show the user the complete file before writing. Ask: "Create this Rock?"
使用
templates/rock.md
作为模板，替换以下内容：
  • 前置元数据字段（id、title、owner、quarter、status=on_track、created=当前日期、due=季度末日期）
  • 正文部分（可衡量成果、里程碑）
写入到
data/rocks/YYYY-QN/rock-NNN-slug.md
。
写入前向用户展示完整的文件内容，询问：“是否创建这个Rock？”

Step 7: Repeat or Finish

步骤7：重复或结束

Ask: "Create another Rock, or are we done for now?"
When finished, display a summary table of all Rocks for the quarter:
RockOwnerDue
Launch Beta Programbrad2026-03-31
Hire VP Salesdaniel2026-03-31
询问：“需要再创建一个Rock，还是目前就到这里？”
完成后，展示本季度所有Rocks的汇总表：
Rock负责人截止日期
Launch Beta Programbrad2026-03-31
Hire VP Salesdaniel2026-03-31

Mode: Tracking Rocks

模式：跟踪Rocks

Use for weekly or ad-hoc status checks.
用于每周或临时状态检查。

Step 1: Read All Rocks

步骤1：读取所有Rocks

Read all Rock files in 
data/rocks/[current-quarter]/
. Parse the frontmatter for status.
读取
data/rocks/[当前季度]/
下的所有Rock文件，解析前置元数据中的状态。

Step 2: Display Status

步骤2：展示状态

Show a status table:
RockOwnerStatusMilestonesNotes
Launch Beta Programbradon_track2/3 completeOn schedule
Hire VP Salesdanieloff_track0/4 complete (1 overdue)No candidates yet
Milestone progress computation:
  • If frontmatter has 
    milestones
    array    : Count entries with 
    status: done
    vs total. Display: "N/M complete". If any milestone has 
    due
    in the past and 
    status
    is not 
    done
    , append "(X overdue)".
  • Else: Parse markdown checklist in body (count 
    [x]
    vs total 
    [ ]
    and 
    [x]
    ). Display: "N/M done".
Attachment display: If frontmatter has 
attachments
array, show after the status table:
Attachments:
  • Beta spec (data/rocks/2026-Q1/rock-001-beta-spec.pdf)
  • Requirements doc (data/rocks/2026-Q1/requirements.pdf)
展示状态表：
Rock负责人状态里程碑备注
Launch Beta Programbradon_track2/3 完成进度符合预期
Hire VP Salesdanieloff_track0/4 完成（1个逾期）暂未收到候选人简历
里程碑进度计算规则：
  • 如果前置元数据有
    milestones
    数组    ：统计
    status: done
    的条目数和总条目数，展示：“N/M 完成”。如果有任何里程碑的
    due
    日期已过且
    status
    不是
    done
    ，追加“(X个逾期)”。
  • 否则：解析正文中的markdown checklist（统计
    [x]
    的数量和
    [ ]
    +
    [x]
    的总数量），展示：“N/M 完成”。
附件展示： 如果前置元数据有
attachments
数组，在状态表后展示：
附件:
  • Beta测试规范 (data/rocks/2026-Q1/rock-001-beta-spec.pdf)
  • 需求文档 (data/rocks/2026-Q1/requirements.pdf)

Step 3: Update Status

步骤3：更新状态

If a Rock's status needs to change:
  1. Show the current status
  2. Ask what the new status should be (on_track or off_track)
  3. Show the diff in the frontmatter
  4. Ask for approval before writing
  5. Add a dated note to the Notes section
如果某个Rock的状态需要变更：
  1. 展示当前状态
  2. 询问新的状态是什么（on_track或off_track）
  3. 展示前置元数据的变更diff
  4. 写入前请求用户确认
  5. 在备注部分添加带日期的说明

Mode: Scoring Rocks (End of Quarter)

模式：评分Rocks（季度末）

Use at the end of a quarter for the completion review.
用于季度末的完成情况复盘。

Step 1: Load All Rocks

步骤1：加载所有Rocks

Read all Rock files in 
data/rocks/[quarter]/
.
读取
data/rocks/[对应季度]/
下的所有Rock文件。

Step 2: Score Each Rock

步骤2：为每个Rock评分

For each Rock, ask: "Complete or incomplete?"
  • EOS scoring is binary. No partial credit. The measurable outcome was either achieved or it wasn't.
  • Update status to 
    complete
    or 
    dropped
    (if the Rock was abandoned or deprioritized)
  • A Rock that was worked on but not finished gets 
    dropped
    — it can become a new Rock next quarter
针对每个Rock询问：“已完成还是未完成？”
  • EOS评分是二元的，没有部分得分，可衡量成果要么达成要么未达成。
  • 将状态更新为
    complete
    或
    dropped
    （如果Rock被放弃或降低优先级）
  • 已开展但未完成的Rock标记为
    dropped
    ——可以在下个季度作为新Rock重新设置

Step 3: Show the diff for each status change, ask for approval.

步骤3：展示每个状态变更的diff，请求用户确认。

Step 4: Summary

步骤4：汇总

Display the quarter scorecard:
Q1 2026 Rock Scorecard
━━━━━━━━━━━━━━━━━━━━━━
Complete: 4/6 (67%)
Target: 80%+

✓ Launch Beta Program (brad)
✓ Hire VP Sales (daniel)
✓ Implement CRM (daniel)
✗ Redesign Onboarding (brad) — dropped
✓ ISO Certification (sarah)
✗ Partner Program (brad) — dropped
If completion rate is below 80%, flag it: "Below the 80% target. Consider: Were Rocks too ambitious, or were there execution issues? This is a good topic for the next L10."
展示季度评分卡：
2026年Q1 Rock评分卡
━━━━━━━━━━━━━━━━━━━━━━
完成率: 4/6 (67%)
目标: 80%+

✓ 启动Beta测试项目 (brad)
✓ 招聘销售副总裁 (daniel)
✓ 上线CRM系统 (daniel)
✗ 重设计新用户入职流程 (brad) — 已放弃
✓ 通过ISO认证 (sarah)
✗ 合作伙伴项目 (brad) — 已放弃
如果完成率低于80%，标记提示：“低于80%的目标值，可以考虑：Rocks设定得过于激进，还是执行层面存在问题？这是下一次L10会议的好议题。”

Output Format

输出格式

Setting: Show each Rock file before writing. End with a summary table. Tracking: Status table with milestone progress (from frontmatter milestones if present, else markdown checklist). Overdue milestones flagged. Attachments listed if present. Scoring: Quarter scorecard with completion rate.
设定模式： 写入前展示每个Rock文件，最后输出汇总表。 跟踪模式： 带里程碑进度的状态表（优先使用前置元数据中的里程碑，否则使用markdown checklist），标记逾期里程碑，如有附件则列出。 评分模式： 带完成率的季度评分卡。

Guardrails

规则限制

  • Always show diff before writing. Never modify a Rock file without showing the change and getting approval.
  • One owner per Rock. If the user tries to assign a Rock to multiple people, explain that EOS Rocks have one owner. Suggest splitting into separate Rocks.
  • 3-7 per person. Warn (don't block) if someone is outside this range.
  • Binary scoring only. Don't allow "partial" or percentage-based scoring. Complete or dropped.
  • Milestone status values. Only accept 
    todo
    , 
    in_progress
    , 
    done
    for structured milestones. If the user provides another value during creation, show the allowed values.
  • Respect quarter boundaries. Rocks in 
    data/rocks/2026-Q1/
    belong to Q1. Don't move them between quarters — create new Rocks in the next quarter instead.
  • Cross-reference V/TO. When setting Rocks, check alignment with the 1-Year Plan from 
    data/vision.md
    . Use 
    ceos-vto
    if deeper vision review is needed.
  • ID uniqueness. Always check existing files before assigning an ID to avoid collisions.
  • Don't auto-invoke other skills. Mention 
    ceos-vto
    , 
    ceos-l10
    , and 
    ceos-annual
    when relevant, but let the user decide when to switch workflows.
  • Sensitive data warning. On first use, remind the user: "Rocks may contain sensitive business priorities. Use a private repo."
  • 写入前必须展示diff。 未展示变更并获得用户确认前，永远不要修改Rock文件。
  • 每个Rock仅一个负责人。 如果用户尝试为一个Rock分配多个负责人，说明EOS Rocks要求唯一负责人，建议拆分为多个独立的Rock。
  • 每人3-7个Rock。 如果某人的Rock数量超出范围，发出警告（不阻断操作）。
  • 仅支持二元评分。 不允许“部分完成”或百分比评分，只能是已完成或已放弃。
  • 里程碑状态值限制。 结构化里程碑仅接受
    todo
    、
    in_progress
    、
    done
    三个值，创建时如果用户提供其他值，展示允许的取值范围。
  • 遵守季度边界。 
    data/rocks/2026-Q1/
    下的Rocks属于Q1，不要在季度之间移动Rocks——可以在下个季度创建新的Rock。
  • 交叉校验V/TO。 设定Rocks时，检查和
    data/vision.md
    中1年规划的对齐性，如果需要更深入的愿景回顾可以使用
    ceos-vto
    。
  • ID唯一性。 分配ID前始终检查已有文件，避免ID冲突。
  • 不要自动调用其他技能。 相关场景可以提及
    ceos-vto
    、
    ceos-l10
    和
    ceos-annual
    ，但让用户自行决定何时切换工作流。
  • 敏感数据提醒。 首次使用时提醒用户：“Rocks可能包含敏感的业务优先级，请使用私有仓库存储。”

Integration Notes

集成说明

V/TO (ceos-vto)

V/TO (ceos-vto)

  • Read: 
    ceos-rocks
    reads 
    data/vision.md
    to check the 1-Year Plan when setting Rocks. Each Rock should connect to a 1-Year Plan goal.
  • Suggested flow: If Rocks don't align with the 1-Year Plan, suggest: "Review the V/TO with 
    ceos-vto
    to ensure strategic alignment."
  • 读取： 设定Rocks时
    ceos-rocks
    会读取
    data/vision.md
    检查1年规划，每个Rock都应该和1年规划目标关联。
  • 建议流程： 如果Rocks和1年规划不对齐，建议：“使用
    ceos-vto
    回顾V/TO，确保战略对齐。”

L10 Meetings (ceos-l10)

L10会议 (ceos-l10)

  • Read: 
    ceos-l10
    reads Rock files during Section 4 (Rock Review) of the L10 meeting. Each Rock owner reports on_track or off_track status.
  • Suggested flow: Off-track Rocks should be discussed further in the IDS section of the L10.
  • 读取： 
    ceos-l10
    在L10会议的第4部分（Rock回顾）会读取Rock文件，每个Rock负责人汇报on_track或off_track状态。
  • 建议流程： 进度落后的Rocks应该在L10的IDS部分进一步讨论。

Quarterly Conversations (ceos-quarterly)

季度沟通 (ceos-quarterly)

  • Read: 
    ceos-quarterly
    references Rock progress during quarterly conversations. Rock ownership and status provide context for individual performance discussions.
  • 读取： 
    ceos-quarterly
    在季度沟通中会引用Rock进度，Rock的归属和状态为个人绩效沟通提供上下文。

Annual Planning (ceos-annual)

年度规划 (ceos-annual)

  • Read/Write: During annual planning, the team scores the outgoing quarter's Rocks and sets Q1 Rocks for the new year. 
    ceos-annual
    orchestrates this; 
    ceos-rocks
    handles the actual Rock creation and scoring.
  • 读/写： 年度规划期间，团队为即将结束的季度的Rocks评分，并为新的一年设定Q1的Rocks。
    ceos-annual
    负责编排流程，
    ceos-rocks
    负责实际的Rock创建和评分。

To-Dos (ceos-todos)

待办事项 (ceos-todos)

  • Related: Rock milestones may generate To-Dos during L10 meetings. These To-Dos are tracked in 
    data/todos/
    via 
    ceos-todos
    with 
    source: l10
    .
  • 关联： Rock里程碑可能在L10会议中生成待办事项，这些待办事项通过
    ceos-todos
    跟踪在
    data/todos/
    中，
    source
    标记为
    l10
    。

Accountability Chart (ceos-accountability)

责任分工表 (ceos-accountability)

  • Read: 
    ceos-rocks
    reads 
    data/accountability.md
    when setting Rocks to validate that Rock owners match seat responsibilities. A Rock about sales pipeline should belong to whoever owns the Sales & Marketing seat.
  • Suggested flow: If a Rock doesn't align with the owner's seat, suggest: "This Rock falls under the [Seat] responsibilities. Should [Seat Owner] own it instead?"
  • 读取： 设定Rocks时
    ceos-rocks
    会读取
    data/accountability.md
    ，校验Rock负责人是否和岗位职责匹配，和销售管道相关的Rock应该归属于销售&营销岗位的负责人。
  • 建议流程： 如果Rock和负责人的岗位不对齐，建议：“该Rock属于[岗位]的职责范围，是否应该由[岗位负责人]来负责？”

Read-Only Principle

只读原则

Other skills read 
data/rocks/
for reference. Only 
ceos-rocks
writes to Rock files. This preserves a single source of truth for quarterly priorities.
其他技能仅读取
data/rocks/
作为参考，仅
ceos-rocks
可以写入Rock文件，保证季度优先级的唯一数据源。