ceos-rocks

Define and manage quarterly Rocks with owners, outcomes, and due dates.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/kevhsunami/EOS --skill ceos-rocks-kevhsunami
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ceos-rocks
Source: https://github.com/kevhsunami/EOS/tree/main/skills/ceos-rocks
Command: npx skills add https://github.com/kevhsunami/EOS --skill ceos-rocks-kevhsunami

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing quarterly Rocks can be complex: teams must assign each Rock to a single owner, define a measurable outcome, and set a due date for quarter-end.

Core Features & Use Cases

  • Set, own, and track 3-7 quarterly Rocks with clear outcomes and due dates.
  • Use structured milestones (frontmatter) or Markdown checklists to capture progress and detect overdue items.
  • Align Rocks to the 1-Year Plan and Accountability Chart to maintain strategic focus and seat ownership.

Quick Start

Create your first Rock for this quarter by using the rock template in templates/rock.md and placing it under data/rocks/.

Frequently Asked Questions about ceos-rocks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan and track quarterly Rocks with a single owner and clear outcomes?

To plan quarterly Rocks, you define each Rock with a single owner, a measurable outcome, and a quarter-end due date. You place the created rock file into the data/rocks/ directory to begin tracking accountability and progress.

What is the best way to align quarterly Rocks with a 1-Year Plan and accountability chart?

Aligning quarterly Rocks requires owner-validated checks against your accountability chart and 1-Year Plan. This ensures every Rock maintains strategic focus and confirms the assigned seat owner is responsible for the specific quarterly outcome.

Can I use structured milestones to detect overdue items in quarterly Rocks?

Yes, you can capture progress and detect overdue items in quarterly Rocks by using structured milestones in YAML frontmatter. Alternatively, Markdown checklists can be used to track milestone completion and monitor timeline delays.

How do I create a quarterly Rock using a standard template?

You create a quarterly Rock by using the standard template located in templates/rock.md. Each Rock requires YAML frontmatter for metadata, optional structured milestones, and must be saved under the data/rocks/ directory.

How many quarterly Rocks should I set and own for each quarter?

You should set, own, and track between 3 to 7 quarterly Rocks per quarter. Each Rock must have clear outcomes, a defined due date for quarter-end, and a single owner to ensure strict accountability.

Do I need YAML frontmatter for every quarterly Rock I define?

Yes, YAML frontmatter is required for every quarterly Rock to define its metadata, owner, and due dates. Structured milestones within the frontmatter are optional but recommended for tracking progress and detecting overdue items.