ceos-clarity

Coordinate and document Clarity Break sessions for EOS teams.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarity Breaks are essential for strategic thinking, but teams often struggle to consistently capture insights, themes, and action items. This skill provides a structured yet flexible workflow to guide reflection, preserve context from V/TO, Rocks, Scorecard, and Issues, and prepare items for the next L10.

Core Features & Use Cases

  • Context-aware Start mode reads the latest repository data (vision, rocks, scorecard, issues) to surface a strategic snapshot.
  • Guided reflection prompts capture what’s working, what’s not, what’s missing, and what needs to change.
  • Outputs are organized into frontmatter fields (themes, issues_identified) and a new data/clarity/YYYY-MM-DD.md file for archival.
  • Supports retrospective logging (Mode: Log) and historical review (Mode: History) to surface recurring themes and insights.

Quick Start

Open Claude Code and begin a new Clarity Break session using the ceos-clarity workflow.

Frequently Asked Questions about ceos-clarity

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

FAQPage Schema
How do I document EOS Clarity Breaks to capture strategic themes and issues?

Document EOS Clarity Breaks by running a guided workflow that reads V/TO, Rocks, Scorecard, and open Issues to capture reflections. It writes structured markdown files with frontmatter fields like themes and issues_identified for archival.

What is the best way to prepare for an L10 meeting using Clarity Break reflections?

Prepare for an L10 meeting by using Clarity Break reflections to surface actionable themes and open Issues. The workflow reads your latest repository data to provide a strategic snapshot, organizing outputs into structured frontmatter fields for team review.

How do I log retrospective Clarity Break sessions and review historical insights?

Log retrospective sessions using Log mode to capture past reflections, and use History mode to review them. History mode surfaces recurring themes and insights from previously archived markdown files stored in the clarity data directory.

Can I use this workflow if my team only tracks Rocks and Scorecard data without a full V/TO?

Yes, you can use this workflow with partial data. Start mode reads available repository data from Rocks and Scorecard directories to surface a strategic snapshot, adapting the reflection prompts to the context provided.

What data formats and file structures does the Clarity Break workflow require?

The workflow requires markdown files in specific directories: vision.md, rocks/, scorecard/weeks/, and issues/open/. It outputs new markdown files to data/clarity/ with YAML frontmatter fields including date, person, and duration.