/ceos-accountability

name: ceos-accountability
description: Use when viewing, updating, or auditing the Accountability Chart — seats, owners, and roles
file-access: [data/accountability.md, templates/accountability.md, data/people/]
tools-used: [Read, Write, Glob, Edit]

ceos-accountability

Manage the Accountability Chart — the organizational structure that defines who owns what seat, what each seat's 5 key responsibilities are, and the reporting hierarchy. Every function of the business has one clear owner. A person can own multiple seats, but every seat needs exactly one owner.

When to Use

• "Show the accountability chart" or "who owns what?"
• "Update the org chart" or "change seat ownership"
• "Add a new seat" or "we need a VP of Product"
• "Remove a seat" or "consolidate these roles"
• "Audit the accountability chart" or "check for gaps"
• "Who reports to whom?" or "show the structure"
• "How many seats does [person] own?"
• "Are there any empty seats?" or "what roles are unfilled?"
• "Update roles for [seat]" or "change responsibilities"
• Any discussion about organizational structure, seat ownership, or role definition

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/accountability.md` | The Accountability Chart (source of truth) | | `templates/accountability.md` | Template for new charts (used by `setup.sh init`) | | `data/people/` | Person evaluation files (cross-reference for Audit) |

Accountability Chart Structure

The chart is a single markdown file (`data/accountability.md`) with this structure:

• **Company heading:** `## CompanyName` at the top with a `*Last updated: YYYY-MM-DD*` line
• **How to Use section:** Instructions block (preserved during edits)
• **Seats:** Each seat is a `## SeatName` heading followed by:
• `**Owner:** PersonName` (or `[Name]` if unfilled)
• A roles table with exactly 5 numbered rows

**Example seat:**

## VP of Sales

**Owner:** Mike Torres

| # | Role |
|---|------|
| 1 | Revenue — hit quarterly sales targets |
| 2 | Pipeline — maintain 3x pipeline coverage |
| 3 | Team — recruit, coach, and retain sales reps |
| 4 | Process — define and enforce the sales playbook |
| 5 | Reporting — weekly forecast and funnel metrics |

**Hierarchy** is implicit from the order of seats in the file. The Visionary and Integrator appear first (top of org), followed by functional seats (Sales, Ops, Finance, etc.).

**Template placeholders:** `[Name]` for empty owner, `[Key responsibility]` for undefined roles.

Process

Mode: View

When the user asks to see the accountability chart or check seat ownership.

Step 1: Read the Chart

Read `data/accountability.md`. If the file doesn't exist: "No accountability chart found. Run `./setup.sh init` to create one from the template, or create `data/accountability.md` manually."

Step 2: Parse Seats

Walk through the file and extract each seat:

• **Title:** The `## SeatName` heading text
• **Owner:** The name after `**Owner:**` (or "empty" if `[Name]`)
• **Roles:** The numbered entries in the roles table
• **Role count:** How many non-placeholder roles are defined

Step 3: Display the Chart

Show the chart in a clear hierarchical format:

Accountability Chart — Acme Corp
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Last updated: 2026-02-01

  Visionary                Brad Feld         5/5 roles
  Integrator               Sarah Chen        5/5 roles
  ├── VP of Sales          Mike Torres       5/5 roles
  ├── VP of Operations     Daniel Kim        5/5 roles
  └── VP of Finance        (empty)           0/5 roles

If the user asks for detail, show each seat with its full role table.

Step 4: Summary Stats

Summary: 5 seats | 4 filled | 1 empty | avg 4.0 roles per seat

---

Mode: Update

When the user wants to modify the accountability chart — add, change, or remove seats.

Sub-mode: Add Seat

Step 1: Collect Seat Information

Ask for:

1. **Title** — "What's the seat title?" (e.g., "VP of Product") 2. **Owner** — "Who owns this seat?" (one person, or leave empty for a gap to fill) 3. **Five roles** — "What are the 5 key responsibilities for this seat?" 4. **Position** — "Where in the hierarchy? Under which seat, or at the leadership level?"

Step 2: Validate

• **Title required.** If empty, ask again.
• **5 roles recommended.** If fewer than 5, warn: "EOS recommends exactly 5 roles per seat. You have [N]. Want to add more, or save as-is?"
• **Check for duplicate title.** If a seat with the same title already exists: "A seat called '[Title]' already exists. Did you mean to modify it instead?"

Step 3: Show the Addition

Display the new seat in the correct format:

## VP of Product

**Owner:** [Collected name or [Name]]

| # | Role |
|---|------|
| 1 | [Role 1] |
| 2 | [Role 2] |
| 3 | [Role 3] |
| 4 | [Role 4] |
| 5 | [Role 5] |

Ask: "Add this seat to the accountability chart?"

Step 4: Write

Insert the new seat at the correct position in `data/accountability.md`. Add a `---` separator before the new seat. Update the `*Last updated:*` date to today.

Sub-mode: Modify Seat

Step 1: Select the Seat

Show the current chart (list seats with owners). Ask: "Which seat do you want to modify?"

Accept by title or owner name.

Step 2: Show Current State

Display the seat's current title, owner, and all 5 roles.

Step 3: Collect Changes

Ask what to change:

• **Owner** — "Change the owner?"
• **Roles** —